Mouse click unresponsive until Alt-[key] pressed

[vnaipaul]

Hi,

We are seeing a problem with our apps not responding to mouse clicks occasionally, only to become responsive again after an Alt-[key] combination (at which point a menu drops as expected), as if the Alt-[key] combination is resetting something … a mouse event queue hitting limits ?

This problem was pretty bad under v5.3.10, and while its improved under v6, its still pretty disruptive.

Does anyone recognize this ?

Maybe related … we also have poor double-click responsiveness in general, as if the DE mouse-double-click-interval is ignored (yet Xfce’s double-click ‘lightbulb’ test behaves as expected).

Thanks,

Val

• NoMachine Enterprise Terminal Server (eval) v6.0.66 on CentOS-6
• NoMachine Terminal Server Node (eval) v6.0.66 on CentOS-6, Xfce 4.8 + xfwm4, virtual desktop
• Windows 8 + Firefox (~v50)

[graywolf]

Did you experience that with generic Xfce apps or something more specific?

[vnaipaul]

Its with our own Qt-based app–its a fairly mature product.

Good point, it occurred to me yesterday that a baseline would be useful too, I started playing with Xfce’s terminal app:  no signs of the problem there but I might not have been using it for long enough for the problem to show up.

[vnaipaul]

Correction about the test client machine:  Windows 7 Pro (SP1) + Firefox 52.5.3 (32-bit) with 8GB memory.

[graywolf]

All the symptoms make me think that the Qt app didn’t release a mouse grab.

Which is the Qt version in use?

[vnaipaul]

Good lead … the Qt libs are unresolved (ldd reports “not found”).

I’m pretty sure I didn’t install this app properly come to think, and I didn’t install Qt I’m sure, though it more or less works otherwise (maybe it has a fallback if Qt isn’t available ?).  This aligns with us not seeing this problem outside of this NoMachine deployment.

Comparing to a properly installed version btw, ldd reports libQt* v4, which resolves to v4.6.2.

I’ll reinstall and retest.

Thanks graywolf.

[vnaipaul]

I think this has been resolved after a proper re-install of our Qt app:  the Qt libs shipped with the product were being found it turned out (there was no fallback), but there were other unresolved libraries that are now found.

And the double-click responsiveness was a separate issue–I had to change the threshold in the xfce-perchannel-xml file.

[graywolf]

Happy that your problem is solved. Thanks for letting us know!

[Author]

Posts