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.
