Re: Awesome becomes unresponsive to mouse

[Uli Schlachter]

Hi,

Am 23.07.2016 um 05:25 schrieb Ranko Kohime:
> I've had the issue for a while that some combination of circumstances will 
> cause
> Awesome to be unresponsive to mouse clicks, on the menu, taglist, and
> clientlist, as well as any permanent (red) notifications.  System tray icons 
> are
> still responsive, and hotkeys are still responsive, just not the mouse.  I've
> pretty much narrowed it down to USB devices as the cause: nearly anytime I
> hotplug or hotunplug a USB audio device, mouse or keyboard (thumb drives don't
> seem to affect it), I get this problem.
[...]
> interested to know if anyone else has run into this problem, and possibly
> found a fix/workaround for it.

The problem is Qt. Close all Qt apps when this happens and mouse input will work
again.

https://github.com/awesomeWM/awesome/issues/415
https://bugreports.qt.io/browse/QTBUG-49952

A fix is to upgrade to a newer Qt version. A 'workaround' is to upgrade to a
newer awesome version. This will make the problem go away everywhere except on
the root window (but apparently you didn't even notice that mouse clicks don't
work here, so that might be ok for you).

Qt uses the XInput extension to be able to tell apart different input devices
(which of the connected mouses generated a mouse click?). When a new input
device appears, Qt re-grabs mouse events on all of its windows for all input
devices. Due to a bug in Qt, it also grabbed mouse events on the root window,
which means that awesome will not see the event as it is only sent to Qt.

The workaround in newer awesome versions makes awesome grab mouse input on its
own window instead of just on the root window where Qt steals them. However, no
workaround for clicks on the root window is possible.

Cheers,
Uli
-- 
"Every once in a while, declare peace. It confuses the hell out of your enemies"
 - 79th Rule of Acquisition

--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

Awesome becomes unresponsive to mouse

[Ranko Kohime]

First of all, I'm running Awesome 3.5.9 on Arch Linux, on an Intel i7-4790K,
32GB of RAM, with an Nvidia GTX 980 Ti with the proprietary drivers (and two
separate X screens driving one monitor each), starting 2 instances of Awesome
with different configs from my .xinitrc.  Not running any display manager.

I've had the issue for a while that some combination of circumstances will cause
Awesome to be unresponsive to mouse clicks, on the menu, taglist, and
clientlist, as well as any permanent (red) notifications.  System tray icons are
still responsive, and hotkeys are still responsive, just not the mouse.  I've
pretty much narrowed it down to USB devices as the cause: nearly anytime I
hotplug or hotunplug a USB audio device, mouse or keyboard (thumb drives don't
seem to affect it), I get this problem.

It usually goes away at some point as I'm closing down apps for a reboot,
without any real rhyme or reason as to which app needs to be closed to correct
the problem.

Sometimes it'll only be one or the other display that has the problem, and
sometimes it'll be both.  When it's just one, it usually follows whichever
monitor has the mouse at the moment of the USB event.

Thus far, I've not been able to deduce the reason for this behavior, as it
doesn't trigger any messages either in the Xorg log, or when redirecting console
output to a file when starting Awesome.

I'd be interested to know if anyone else has run into this problem, and possibly
found a fix/workaround for it.


-- 
Ranko Kohime

Blog: 
PGP Pubkey: 

-- 
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.