Created attachment 415314 [details] emerge --info When plugging / unplugging an input device (mouse, keyboard) in awesome with a Qt5 application running (tested with owncloud-client and kdiff3), awesome does not react to mouse clicks. When killing / restarting all Qt5 applications, awesome continues to work as expected. Other applications do not seem to be affected. I run x11-wm/awesome-3.5.6-r1. I have tried to reproduce this problem in Xfce without success. However, it is reproducible with the default awesome configuration. I've also unsuccessfully tried qtgui-5.5.1 with USE=-evdev. The problem is also reproducible with awesome from git master. The bug occurs with Qt 5.5.1 but not after a downgrade to Qt 5.4.2.
i can confirm this problem too. [I] dev-qt/qtgui Available versions: (4) 4.8.6-r4 (~)4.8.7 (5) 5.4.2-r1^t (~)5.5.1^t {(+)accessibility aqua cups dbus debug egl eglfs evdev +exceptions +gif gles2 +glib gtkstyle +harfbuzz ibus jpeg libinput mng nas nis pch +png qt3support test tiff trace tslib tuio +udev +xcb xinerama +xv ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="32 64 x32"} Installed versions: 4.8.7(4)(08:18:59 12.11.2015)(accessibility cups exceptions glib mng qt3support tiff xv -aqua -debug -egl -gtkstyle -nas -nis -pch -trace -xinerama ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="32 64 -x32") 5.5.1(5)^t(19:15:19 11.11.2015)(accessibility dbus egl gif gles2 jpeg png udev xcb -debug -eglfs -evdev -gtkstyle -ibus -libinput -test -tslib -tuio) Homepage: https://www.qt.io/ Description: Portage 2.2.24 (python 3.5.0-final-0, default/linux/amd64/13.0/desktop, gcc-4.9.3, glibc-2.22-r1, 4.3.0-gentoo x86_64) ================================================================= System uname: Linux-4.3.0-gentoo-x86_64-Intel-R-_Core-TM-_i7-3740QM_CPU_@_2.70GHz-with-gentoo-2.2 KiB Mem: 24627044 total, 21267652 free KiB Swap: 26488828 total, 26488828 free Timestamp of repository gentoo: Fri, 13 Nov 2015 16:30:01 +0000 Timestamp of repository poly-c: Fri, 13 Nov 2015 06:32:13 +0000 sh bash 4.3_p42 ld GNU ld (Gentoo 2.25.1 p1.1) 2.25.1 app-shells/bash: 4.3_p42::gentoo dev-java/java-config: 2.2.0::gentoo dev-lang/perl: 5.22.0::gentoo dev-lang/python: 2.7.10-r2::gentoo, 3.4.3-r2::gentoo, 3.5.0-r1::gentoo dev-util/cmake: 3.4.0::gentoo dev-util/pkgconfig: 0.29::gentoo sys-apps/baselayout: 2.2::gentoo sys-apps/openrc: 0.18.3::gentoo sys-apps/sandbox: 2.9::gentoo sys-devel/autoconf: 2.13::gentoo, 2.69-r1::gentoo sys-devel/automake: 1.11.6-r1::gentoo, 1.13.4::gentoo, 1.14.1::gentoo, 1.15::gentoo sys-devel/binutils: 2.25.1-r1::gentoo sys-devel/gcc: 4.9.3::gentoo sys-devel/gcc-config: 1.8::gentoo sys-devel/libtool: 2.4.6-r1::gentoo sys-devel/make: 4.1-r1::gentoo sys-kernel/linux-headers: 4.3::gentoo (virtual/os-headers) sys-libs/glibc: 2.22-r1::gentoo Repositories:
See also the upstream bug: https://github.com/awesomeWM/awesome/issues/415
who should the assignee be here? the dev or the proxied maintainer?
Created attachment 421908 [details, diff] Patch for Qt 5.5 This turned out to be a Qt bug. See [1] for the upstream bug report, patch and a detailed explanation. [1] https://bugreports.qt.io/browse/QTBUG-49952
(In reply to n0t3p4d.opensource from comment #4) > Created attachment 421908 [details, diff] [details, diff] > Patch for Qt 5.5 > > This turned out to be a Qt bug. > See [1] for the upstream bug report, patch and a detailed explanation. > > [1] https://bugreports.qt.io/browse/QTBUG-49952 Cool, this patch applied to dev-qt/qtcore-5.5.1 seems to fix the issue.
I think this bug should be reassigned to qt herd. It'd be nice to have qtcore 5.5 patched.
CC'ing Qt team to investigate.
(In reply to Priit Laes (IRC: plaes) from comment #5) > (In reply to n0t3p4d.opensource from comment #4) > > Created attachment 421908 [details, diff] [details, diff] [details, diff] > > Patch for Qt 5.5 > > > > This turned out to be a Qt bug. > > See [1] for the upstream bug report, patch and a detailed explanation. > > > > [1] https://bugreports.qt.io/browse/QTBUG-49952 > > Cool, this patch applied to dev-qt/qtcore-5.5.1 seems to fix the issue. I think I was overly optimistic, as the issue is back after a longer usage and another suspend-resume cycle.
(In reply to Priit Laes (IRC: plaes) from comment #8) > I think I was overly optimistic, as the issue is back after a longer usage > and another suspend-resume cycle. You should let upstream now that the patch is not enough then. Thanks.
s/now/know/
As a workaround, you can set QT_XCB_NO_XI2_MOUSE=1 . I've successfully tested the patch without this hack but forgot to permanently disable it.
If you don't want to patch Qt: x11-wm/awesome-3.5.7 has a workaround implemented.
Does 3.5.7 workaround work for those affected?
(In reply to Davide Pesavento from comment #9) > You should let upstream now that the patch is not enough then. Thanks. In Gentoo Bug 616568 "dev-qt/*:5/5.7 :: Any USB event :: QT 5.7.1 "eats up" background mouse events from all other screens" I gave REFERENCE: Detailed description & analysis @ Awesome WM Bug list, Issue 1752: . . . [ https://github.com/awesomeWM/awesome/issues/1752 ] and pointed to my upstream QTBUG-60394 "QTBUG-49952 revived: Any USB event :: QT 5.7.1 "eats up" background mouse events from all other screens" [ https://bugreports.qt.io/browse/QTBUG-60394 ]
Is this still reproducible with stable Qt (5.7.1) and awesome-4? Awesome-3.5 is soon to be removed from the tree anyway.