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 0x4c00001, (0,0), width 1920, height 1200,
border_width 0, above 0x4c00005, override YES
MapNotify event, serial 19, synthetic NO, window 0xb2,
event 0xb2, window 0x4c00001, override YES
ConfigureNotify event, serial 19, synthetic NO, window 0xb2,
event 0xb2, window 0x4c00005, (1920,0), width 1920, height 1200,
border_width 0, above 0x4c00001, override YES
MapNotify event, serial 19, synthetic NO, window 0xb2,
event 0xb2, window 0x4c00005, 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 0x4c00001, (0,0), width 1920, height 1200,
border_width 0, above 0x4c00005, override YES
ConfigureNotify event, serial 19, synthetic NO, window 0xb2,
event 0xb2, window 0x4c00005, (1920,0), width 1920, height 1200,
border_width 0, above 0x4c00001, 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 0x4c00001, (0,0), width 1920, height 1200,
border_width 0, above 0x4c00005, override YES
ConfigureNotify event, serial 19, synthetic NO, window 0xb2,
event 0xb2, window 0x4c00005, (1920,0), width 1920, height 1200,
border_width 0, above 0x4c00001, 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
