Re: [Fluxbox-users] fluxbox permanentely freezes pointer device

[Thomas L. <tho...@gm...>]

On Mon, Aug 08, 2016 at 09:22:18AM +0000, NEURURER.Anton wrote:
>The screensaver is triggered implicitly (300 seconds delay time).
There goes my theory :-(

>If the screensaver is active it performs an active grab on mouse and keyboard:
Yes, that's a "normal" security feature of screensavers.

>I dont see how fluxbox could perform an active grab at the same time?
It doesn't. It's frozen from a passive grab (at least in the log you
provided), ie. probably lacks a
"XAllowEvents(dpy, AsyncPointer, CurrentTime);" somewhere.

Could be the be.time driven call in Window.cc isn't sufficient.
Since you can apparently reproduce this "quite some", can you invoke a
patch (resp. simply alter the call "s/be.time/CurrentTime")?

Cheers,
Thomas