Re: something triggering my screensaver timeout (login dialog) - sid, xfce
On Mon, Jan 06, 2014 at 12:17:37AM +1100, Zenaan Harkness wrote: OK, time for some cannons: I wrote a brief wrapper script for xscreensaver and xscreensaver-command, and redirected the /usr/bin/ versions to my versions which output two lines to a log file. Heres some output: /home/justa/bin/xscreensaver-command -version Monday 6 January 00:11:15 EST 2014 /home/justa/bin/xscreensaver-command -version Monday 6 January 00:11:45 EST 2014 /home/justa/bin/xscreensaver-command -version Monday 6 January 00:12:15 EST 2014 /home/justa/bin/xscreensaver-command -version SO! Every 30 seconds, /usr/bin/xscreensaver-command -version is being called by SOMETHING, which is causing xscreensaver to wake up, it seems! What about lsof(1)¹ man lsof [...] +|-r [t[mfmt]] puts lsof in repeat mode. There lsof lists open files as selected by other options, delays t seconds (default fifteen), then repeats the listing, delaying and listing repetitively until stopped by a condition. [...] Good luck with actually getting it working. :) Any ideas how I might debug this further? Eg, is it possible to determine what's calling xscreensaver-command ? Hopefully, you'll soon find out. :) ¹ For debugging, not that lsof could be the cause. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140107024707.GA27901@tal
Re: something triggering my screensaver timeout (login dialog) - sid, xfce
On Sb, 04 ian 14, 13:33:05, Zenaan Harkness wrote: My login dialog, after I lock my screen, gets repeatedly triggered - as though some keyboard key or mouse movement occurs - even after unplugging my two mice. I have a trackpad which is disabled in bios. There is a trackpoint - the only thing left. You might have noticed that Trackpoints sometimes start drifting. Something like that would definitely trigger the timeout. On ThinkPads it helped if I wiggled them a bit. You might want to compare your xev output with the output of xev when touching the TrackPoint to see if this is the culprit. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: something triggering my screensaver timeout (login dialog) - sid, xfce
On 1/5/14, Andrei POPESCU andreimpope...@gmail.com wrote: On Sb, 04 ian 14, 13:33:05, Zenaan Harkness wrote: My login dialog, after I lock my screen, gets repeatedly triggered - as though some keyboard key or mouse movement occurs - even after unplugging my two mice. I have a trackpad which is disabled in bios. There is a trackpoint - the only thing left. You might have noticed that Trackpoints sometimes start drifting. Something like that would definitely trigger the timeout. On ThinkPads it helped if I wiggled them a bit. This is true. The wiggle is useful for trackpoint drifting. My trackpoint has no drift - eg. running xev by itself (brings user-level window), keep cursor in xev window, no mouse movement events at all (I have mouse, trackball, trackpoint, disabled trackpad) for over a minute. Yet I lock the screen with Ctrl-Alt-L, and inside 20seconds, the unlock password dialog appears! So the events as I posted earlier are the culprit I can only guess. And they are not mouse move (Motion Notify) events as far as I can tell. Here are some sample MotionNotify events: MotionNotify event, serial 37, synthetic NO, window 0xae1, root 0xb2, subw 0x0, time 169639919, (36,124), root:(918,632), state 0x10, is_hint 0, same_screen YES MotionNotify event, serial 37, synthetic NO, window 0xae1, root 0xb2, subw 0x0, time 169639927, (37,124), root:(919,632), state 0x10, is_hint 0, same_screen YES OK, time for some cannons: I wrote a brief wrapper script for xscreensaver and xscreensaver-command, and redirected the /usr/bin/ versions to my versions which output two lines to a log file. Heres some output: /home/justa/bin/xscreensaver-command -version Monday 6 January 00:11:15 EST 2014 /home/justa/bin/xscreensaver-command -version Monday 6 January 00:11:45 EST 2014 /home/justa/bin/xscreensaver-command -version Monday 6 January 00:12:15 EST 2014 /home/justa/bin/xscreensaver-command -version SO! Every 30 seconds, /usr/bin/xscreensaver-command -version is being called by SOMETHING, which is causing xscreensaver to wake up, it seems! from man xscreensaver-command : -version Prints the version of xscreensaver that is currently running on the display: that is, the actual version number of the running xscreensaver background process, rather than the version number of xscreensaver- command. (To see the version number of xscreensaver-command itself, use the -help option.) So this is contacting xscreensaver, which is getting turned into: xscreensaver-command -deactivate Any ideas how I might debug this further? Eg, is it possible to determine what's calling xscreensaver-command ? TIA Zenaan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caosgnsslr53m_2ahyo1kmfdq-mevakmb+ssjugu4bcannel...@mail.gmail.com
Re: something triggering my screensaver timeout (login dialog) - sid, xfce
On 4 January 2014 02:33, Zenaan Harkness z...@freedbms.net wrote: My login dialog, after I lock my screen, gets repeatedly triggered - as though some keyboard key or mouse movement occurs - even after unplugging my two mice. I have a trackpad which is disabled in bios. There is a trackpoint - the only thing left. Is there a program or cmd line script I could run, to deterministically show what triggered xscreensaver? TIA Zenaan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOsGNSTFo+ZuGk-Zz2iOR7c=C_41=2di=7MT_N3=ru4p2tg...@mail.gmail.com xev -- rob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOZWb-p7S1dABPNHfXkP2fRiqJAVF_aU=5g0mn4suytcdzp...@mail.gmail.com
Re: something triggering my screensaver timeout (login dialog) - sid, xfce
On 1/4/14, Robin rc.rattusrat...@gmail.com wrote: On 4 January 2014 02:33, Zenaan Harkness z...@freedbms.net wrote: My login dialog, after I lock my screen, gets repeatedly triggered - as though some keyboard key or mouse movement occurs - even after unplugging my two mice. I have a trackpad which is disabled in bios. There is a trackpoint - the only thing left. Is there a program or cmd line script I could run, to deterministically show what triggered xscreensaver? xev Perfect thanks! So I ran xev from a Linux console (first: export DISPLAY=:0) and from another Linux console (two GNU screen sessions in one Linux console actually, so I could detach, and reattach in X later, to cut and paste into this email): $ xscreensaver-command -lock xscreensaver-command: activating and locking. Here is the xev output in response to the screensaver locking (ie in response to running xscreensaver-command -lock): $ xev -root PropertyNotify event, serial 18, synthetic NO, window 0xb2, atom 0x22f (_SCREENSAVER_STATUS), time 124226344, state PropertyNewValue FocusIn event, serial 18, synthetic NO, window 0xb2, mode NotifyGrab, detail NotifyInferior KeymapNotify event, serial 18, synthetic NO, window 0x0, keys: 4294967197 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 EnterNotify event, serial 18, synthetic NO, window 0xb2, root 0xb2, subw 0x0, time 124226348, (2321,323), root:(2321,323), mode NotifyGrab, detail NotifyInferior, same_screen YES, focus NO, state 16 KeymapNotify event, serial 18, synthetic NO, window 0x0, keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ConfigureNotify event, serial 19, synthetic NO, window 0xb2, event 0xb2, window 0x4c1, (0,0), width 1920, height 1200, border_width 0, above 0x4c5, override YES MapNotify event, serial 19, synthetic NO, window 0xb2, event 0xb2, window 0x4c1, override YES ConfigureNotify event, serial 19, synthetic NO, window 0xb2, event 0xb2, window 0x4c5, (1920,0), width 1920, height 1200, border_width 0, above 0x4c1, override YES MapNotify event, serial 19, synthetic NO, window 0xb2, event 0xb2, window 0x4c5, override YES PropertyNotify event, serial 19, synthetic NO, window 0xb2, atom 0x22f (_SCREENSAVER_STATUS), time 124226360, state PropertyNewValue UnmapNotify event, serial 19, synthetic NO, window 0xb2, event 0xb2, window 0x7e, from_configure NO ConfigureNotify event, serial 19, synthetic NO, window 0xb2, event 0xb2, window 0x4c1, (0,0), width 1920, height 1200, border_width 0, above 0x4c5, override YES ConfigureNotify event, serial 19, synthetic NO, window 0xb2, event 0xb2, window 0x4c5, (1920,0), width 1920, height 1200, border_width 0, above 0x4c1, override YES and here is the remaining output, a short while later (may be 10 seconds), just staying in the linux console running xev, _not_ going to console/terminal/x on Ctrl-Alt-F7 , where the xscreensaver unlock password entry dialog is (it seems) activated by these events: ConfigureNotify event, serial 19, synthetic NO, window 0xb2, event 0xb2, window 0x4c1, (0,0), width 1920, height 1200, border_width 0, above 0x4c5, override YES ConfigureNotify event, serial 19, synthetic NO, window 0xb2, event 0xb2, window 0x4c5, (1920,0), width 1920, height 1200, border_width 0, above 0x4c1, override YES CreateNotify event, serial 19, synthetic NO, window 0xb2, parent 0xb2, window 0x4c6c016, (2591,472), width 578, height 256 border_width 1, override YES MapNotify event, serial 19, synthetic NO, window 0xb2, event 0xb2, window 0x4c6c016, override YES LeaveNotify event, serial 19, synthetic NO, window 0xb2, root 0xb2, subw 0x0, time 124241358, (2321,323), root:(2321,323), mode NotifyUngrab, detail NotifyInferior, same_screen YES, focus NO, state 16 I waited for over half a minute (no other xev events) before finally going to X (Ctrl-Alt-F7), and sure enough the password screensaver unlock dialog was well on its way to timeout (I have a 1 minute timeout set), so clearly the above xev events (which displayed rapidly one after the other) are indicative of what triggered the screensaver unlock dialog. This has never happened before - only since my last sid upgrade (maybe a week ago or so). Is anyone able to decode the above events? TIA Zenaan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOsGNSQLV7SFaizfwscbPhtHJsXFhs=6pefap163qkv-f+k...@mail.gmail.com
something triggering my screensaver timeout (login dialog) - sid, xfce
My login dialog, after I lock my screen, gets repeatedly triggered - as though some keyboard key or mouse movement occurs - even after unplugging my two mice. I have a trackpad which is disabled in bios. There is a trackpoint - the only thing left. Is there a program or cmd line script I could run, to deterministically show what triggered xscreensaver? TIA Zenaan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOsGNSTFo+ZuGk-Zz2iOR7c=C_41=2di=7MT_N3=ru4p2tg...@mail.gmail.com
