Bug 350911

Summary: Akregator stealing focus when minimized in tray with frequency equal to fetch interval
Product: [Applications] akregator Reporter: baschie <bastiaan.huisman>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: grave CC: gronslet
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Mint (Ubuntu based)   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description baschie 2015-08-03 09:30:37 UTC 
Akregator steals my focus at the same interval as the fetching interval. I have focus-follows-mouse, and the mouse cursor for instance in a terminal window. Then every time Akregator fetches feeds, the focus disappears and nothing I'm typing ends up in the terminal. 
This also manifests itself in full screen applications like Citrix receiver, where the kde taskbars appear over the full screen application and focus is stolen from the Citrix receiver.

Reproducible: Always

Steps to Reproduce:
1. Start up a clean install of Akregator.
2. Add a single feed, updating every minute.
3. Minimize Akregator
2. Start typing in a terminal
3. Watch focus get stolen every minute

Actual Results:  
Focus gets stolen with the same interval as the fetching interval

Expected Results:  
Focus stays in program I'm currently using and that my mouse is currently hovering over

I'm running Linux Mint with KDE 4.14.2. Since a few weeks my focus is stolen quite frequently (perhaps once every few minutes). 
I realized after a while that this is due to Akregator, since the problem disappears when I close that program. It happens when Akregator is running in the background.
I've uninstalled Akregator, removed .kde/share/apps/Akregator, reinstalled Akregator and added a single feed that I set a separate fetching interval for. The focus stealing seems to be dependent on this interval. Happening every minute if I set it to 1 minute, every three minutes if I set it to 3 minutes.
I have 2 screens, and use the "mouse follows focus" feature.
I don't know how to create more debug information for you, but I'd be more than willing to perform some tasks if that would help you determine where the problem lies.
The problem is somewhere between grave (if you set it to update every minute), and acceptable (if you set it to fetch every half hour).

Separately I have a crash each time I close (exit)  Akregator, with a similar track trace as reported in 336417, comment 4.
Comment 1 MartinG 2015-10-31 18:51:25 UTC 
baschie  Thank you for nailing this down to Akregator! This bug has been causing me quite some frustration at work the last few weeks. I am almost sure it is related to Akregator as you suggest.

I run Akregator from inside Kontact.
If I mark all my feeds as read, then mark a single post unread, use key navigation to go to the next post, then back to the now last unread post there is: Press right, then left, I immediately lose fokuse, when Akregator marks the post as "read".

Really big annoyance when this also happens every time Akregator updates feeds, and it is really hard to find out what causes the lost focus.

I hereby confirm the bug, and suggest to raise status a bit. I also guess this can be fixed quite fast. I can provide more debug info if required.

I'm using Linux Mint 17.2 (bug also was in 17.1):
akregator                                   4:4.14.2-0ubuntu1~ubuntu14.04~ppa1
Comment 2 Denis Kurz 2017-06-23 20:18:40 UTC 
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Denis Kurz 2018-02-01 09:50:51 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.