Timer stops immediately after start with "You been idle!" on OS 10.7

[GoogleCodeExporter]

What steps will reproduce the problem?
1. upgrade to 10.7
2. start a timer

What is the expected output? What do you see instead?
I expect the timer to run.  Instead, as soon as one second passes, you get a 
message stating "You been idle!"  clicking yes causes the prompt again in 1 
second.  Clicking no causes an entry in the time log with no end time. 

What version of the product are you using? On what operating system?  Intel
or PPC computer?
Later 2010 MBP i7, OS 10.7

Please provide any additional information below.
Current workaround is ignore the popup.  When you are ready to end a timer, 
click yes, then very quickly click the timer stop button.

Original issue reported on code.google.com by delphyne on 21 Jul 2011 at 2:52

[GoogleCodeExporter]

I have now upgraded my machine to 10.7 (clean install) and I don't see this 
issue on my machine. Please check your settings what your idle timeout is.

Original comment by [email protected] on 22 Jul 2011 at 5:30

• Changed state: Reviewed

[GoogleCodeExporter]

Ok, so interestingly, I started the app, started a timer, and it failed as 
described before.

I opened the prefs to check the timeout value (900), and hit ok.  

once i hit ok, the app started working again.  it seems like during the 
upgrade, the prefs got hosed, causing the app to fail in the unexpected way 
described above.  perhaps there should be a check to make sure the preferences 
are sane on startup.

Original comment by delphyne on 23 Jul 2011 at 2:15

[GoogleCodeExporter]

the problem is occurring again, attached is the log output from Console.app

Let me know if i can provide any more data that may help

Original comment by delphyne on 26 Jul 2011 at 5:29

Attachments:

• time_tracker_log.txt

[GoogleCodeExporter]

hey, it would be awesome if you could copy your 2 data files 
(com.slooz.timetracker.plist and data.plist, see the FAQ for the exact 
locations). That might help me to replicate it. I would need the state of those 
files when actually being able to produce the problem. So when you encounter 
it, do nothing, just exit the app, copy the files, restart the app and make 
sure that it still reproduce it. Then either mail me the files (if you don't 
want them up here) or attach them please.
thanks so much.

Original comment by [email protected] on 27 Jul 2011 at 5:24

[GoogleCodeExporter]

No problem.  This morning it worked fine when I started the timer at 8:04AM, 
and failed at 8:27AM.  These plists are from 8:27AM.

Original comment by delphyne on 27 Jul 2011 at 1:36

Attachments:

• issue-121.tgz

[GoogleCodeExporter]

System: 15" MBP Late 2008
OS: Lion 64bit

I get the same error but only when clicking or hitting spacebar when 
controlling my mac using Synergy (http://synergy-foss.org/). It works fine when 
I start a task when controlling the mac directly. I'm currently using Synergy 
1.3.5 as version 1.4.5 has some issues (clipboard & right-click).

Summary:
Issues occurs when: I click or hit spacebar when controlling the mac using 
Synergy
Issue does not occur when: I click or hit spacebar when controlling the mac 
directly

FWIW, no other apps are causing issues when controlled through Synergy.

Original comment by [email protected] on 9 Dec 2011 at 4:27

[GoogleCodeExporter]

FWIW, my HD was upgraded to a Crucial M4 256GB SSD. 

Original comment by [email protected] on 12 Dec 2011 at 8:27

[GoogleCodeExporter]

This is also happening on a Mid 2009 MacBook Pro, 15"

Original comment by [email protected] on 20 Jan 2012 at 6:52

[GoogleCodeExporter]

@jcvalero, I am not sure what the hitting of your spacebar does. Can you please 
provide a more thorough report. 

1. start from when you start the app and describe all the steps that you do 
until you see the issue
2. attach a console log.

Original comment by [email protected] on 21 Jan 2012 at 10:13

[GoogleCodeExporter]

It looks like the latest beta version of Synergy resolved the issue (1.4.7)

Original comment by [email protected] on 10 Feb 2012 at 6:14

[GoogleCodeExporter]

Never mind, the message is still continuously popping up when clicking yes to 
include the idle time. This might be a synergy issue since it works fine if I 
click yes directly from the mac instead.

Original comment by [email protected] on 10 Feb 2012 at 7:38

[GoogleCodeExporter]

Hey. I am expecting that synergy injects events in a way that Mac Os does not 
recognize as events that would reset the idle time. Therefore the idle timer 
will probably fire since you were not really physically moving the mouse. Not 
sure if there is anything I can do on the app side. 

Original comment by [email protected] on 10 Feb 2012 at 8:58

[GoogleCodeExporter]

The problem also happens with Teleport.  The problem does not manifest as 
eventually timing out, it times out instantly.  The problem is new as of Lion.  
Snow Leopard does not exhibit the behavior.

Sometimes it happens immediately.  Sometimes it happens after a few minutes, 
other after an hour.  It appears that the earlier in the morning (and odd 
distinction, i know), the less likely the error occurs.  

Original comment by [email protected] on 10 Feb 2012 at 9:03

[GoogleCodeExporter]

Agreed, this is new in Lion.

Hopefully removing some deprecated SDK calls will do the trick for Synergy. 
http://synergy-foss.org/tracker/issues/706 . If this is the case, perhaps the 
developer of Teleport can do the same? I did see there is a Lion-compatible 
version of Teleport (v1.1.1).

Original comment by [email protected] on 14 Feb 2012 at 7:13