Re: fluxbox permanentely freezes pointer device

On Thu, Aug 11, 2016 at 06:16:59AM +0000, NEURURER.Anton wrote:
>At the moment I am running several devices with your patch. So far no problems occurred.
Cool! =)

>I am doing some experiments with 2 other devices and I have found out that it is possible to freeze the mouse immediately and permanently if I change "be.time" to  "CurrentTime + 10000".

Yeah, no - that's the equivalent of "10000" - usually far in the past.
(CurrentTime is 0 and treated specially. The time isn't eg. resolved
dynamically since the async protocol would kill such attempts)

And yes, messing around with timestamps (also on the server) is
incredibly prone to cause such locks.
See https://bugs.kde.org/show_bug.cgi?id=348569 - clusterssh puts junk
into event timestamps and kwin uses event timestamps to update the servertime
(very good for performance, but very attackable as well)

>I think be.time could really be the cause of the problem.
Let's hope so and many thanks for the update.

Cheers,
Thomas

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. http://sdm.link/zohodev2dev