Your message dated Mon, 10 Aug 2020 16:39:20 +0200 with message-id <[email protected]> and subject line Re: Bug#664222: still reproducible on 0.2-5 has caused the Debian Bug report #664222, regarding [xprintidle] reporting impossible idle times. to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 664222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664222 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: xprintidle Version: 0.2-4 Severity: normal --- Please enter the report below this line. --- some of the environment info is wrong. Running i386 squeeze in a ltsp nfs mounted environment that can not send email. Working on a script to shut down ltsp terminal after a given idle time. This script is called by cron ever 10 minutes: #!/bin/bash #install xprintidle cron #add cron entry to lts.conf export DISPLAY=:7 export XAUTHORITY=`ps -ef|grep xinit |grep -v grep|cut -d" " -f 26` #`grep XAUTHORITY /var/log/ldm.log` # time is in miliseconds #90 minutes 90*60*1000 5400000 idletime=`/usr/bin/xprintidle` /bin/date +%T >> /tmp/idletime echo $idletime >> /tmp/idletime if (( $idletime > 5400000 )) ; then /sbin/shutdown -h now; fi ........................................................ Some of the debugging tmp file: 13:30:01 74472 13:40:02 125794 13:50:01 2525087 14:00:01 21486 14:10:01 2421775 14:20:01 12377 14:30:01 573954 14:40:01 25396 14:50:02 296359 15:00:01 2695648 If we look at 14:40:01 to 14:50:02 2695648 - 296359 = 2,399,289 ms This converts to 39.988 minutes of additional idle time in a 10 minute period. Simple tests look OK. root@ws-1-74:~# xprintidle ;sleep 10; xprintidle 2019311 2029552 let me know any additional info is needed. John McMonagle --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-0.bpo.1-amd64 Debian Release: 6.0.4 500 testing fondy.advocap.org 500 stable-updates ftp.debian.org 500 stable www.debian-multimedia.org 500 stable security.debian.org 500 stable ftp.us.debian.org 500 stable dl.google.com 200 squeeze-backports backports.debian.org --- Package information. --- Depends (Version) | Installed =======================-+-=========== libc6 (>= 2.2.5) | 2.11.3-3 libx11-6 (>= 0) | 2:1.3.3-4 libxext6 (>= 0) | 2:1.1.2-1 libxss1 | 1:1.2.0-2 Package's Recommends field is empty. Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---Version: 0.2-10 There are reports of a similar problem no longer affecting gnome in 2018, so I take the chance to close this bug as fixed. As previously noted, I suspect the bug really was in the X server, but do not see the point of trying to track down any more details. -- Happy hacking Petter Reinholdtsen
--- End Message ---
