Bug 84510

Summary: Idle detection dialog pops up on karm's virtual desktop even if that one is not active
Product: [Applications] ktimetracker Reporter: Marc Haber <mh+kde-bugs>
Component: generalAssignee: Mark Bucciarelli <mark>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: dev, l.lunak
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Marc Haber 2004-07-05 13:20:57 UTC 
Version:           1.3.1 (using KDE 3.2.3,  (testing/unstable))
Compiler:          gcc version 3.3.3 (Debian 20040422)
OS:                Linux (i686) release 2.4.26-vash

When the machine is left idle, the idle detection dialog pops up on the desktop that karm is running on, which might not be the one active at the moment. Hence, the dialog is not noticed when the user returns and might work without time detection active.

I would want karm to pop up the idle dialog on whatever desktop is active at the moment to make sure the user notices.

Greetings
Marc
Comment 1 Mark Bucciarelli 2004-07-05 15:20:36 UTC 
Thanks for your report!

What version of KDE are you running?
Comment 2 Marc Haber 2004-07-05 15:40:05 UTC 
kde 3.2.2-2 from Debian unstable.
Comment 3 Hal 2007-09-21 09:56:49 UTC 
Are you sure you would want that behavior?  If I am using AutoTracking, then I only want to have the choice when I return to THAT desktop, where all of my work for that Task is.

At best, maybe this should be an option, but not the default behavior.  Just my 2c.
Comment 4 Hal 2007-09-21 09:57:32 UTC 
Are you sure you would want that behavior?  If I am using AutoTracking, then I only want to have the choice when I return to THAT desktop, where all of my work for that Task is.

At best, maybe this should be an option, but not the default behavior.  Just my 2c.
Comment 5 Thorsten Staerk 2007-12-12 23:20:44 UTC 
It is fixed in the meantime, or I cannot reproduce.
Comment 6 Thorsten Staerk 2008-12-23 12:34:02 UTC 
why did I close this? I have no idea. It is fixed now.

*** This bug has been marked as a duplicate of bug 174301 ***