Thanks for testing. If I compute correctly, 16200000 ms is exactly 4.5 hours, not half an hour. Well, the exactness of the value is still suspicious.
Please note that xprintidle doesn't do much more than reading and printing the idle value returned from XScreenSaverQueryInfo. The only possible problem I can see is allocation of XScreenSaverInfo structure without proper initialization. I've fixed it in 0.2-6. If it doesn't help then I don't know what to do more. Perhaps XScreenSaverQueryInfo returns invalid values under some circumstances. I'm not going to debug it, I'm sorry. Any help is appreciated. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
