The bug is still reproducible in 0.2-5.
I have been running this script for two days:
while true; do xprintidle; sleep 10; done

After about 24 hours of not touching the PC it got stuck with an output
looking like this:
$ xprintidle
16200004
$ xprintidle
16200003

basiclaly resetting to 16200000 and not 0.
I think after a certain amount of time xprintidle gets stuck
(the number 16200000 suggests about half an hour, so i guess its more than
that).

I think you should run the small line above on a machine and not touch it
for a day, that should reproduce the bug
Then you can test possible fixes on the "broken" machine.

Guy

Reply via email to