Re: fluxbox permanentely freezes pointer device

>Smells like fluxbox grabs the pointer, the screensaver grabs the server (or actively the pointer), fluxbox doesn't receive a button release (implying an auto-allow of the event) because of this and never allows the event explicitly.

>Is the screensaver triggered im- or explicitly? (ie. for idleness or from eg. a menu entry)

Hi Thomas

The screensaver is triggered implicitly (300 seconds delay time).

If the screensaver is active it performs an active grab on mouse and keyboard:

[308747.389] (II) Printing all currently active device grabs:
[308747.389] Active grab 0x1800000 (core) on device 'Virtual core pointer' (2):
[308747.389]       client pid 10624 xscreensaver
[308747.389]       at 243482375 (from active grab) (device thawed, state 1)
[308747.389]         core event mask 0x3ffc
[308747.389]       owner-events true, kb 1 ptr 1, confine 107, cursor 0x1800004
[308747.389] Active grab 0x1800000 (core) on device 'Virtual core keyboard' (3):
[308747.389]       client pid 10624 xscreensaver
[308747.389]       at 243482375 (from active grab) (device thawed, state 1)
[308747.389]         core event mask 0x3
[308747.389]       owner-events true, kb 1 ptr 0, confine 0, cursor 0x0
[308747.390] (II) End list of active device grabs

I dont see how fluxbox could perform an active grab at the same time? According to the xlib documentation this should result in an "AlreadyGrabbed" error.

In case the application is not usable any more there is only one active grab (fluxbox) in the xorg log. Then also the screensaver is never activated again.

 Best regards
Anton




------------------------------------------------------------------------------