https://bugs.kde.org/show_bug.cgi?id=389674
--- Comment #11 from Fabian Vogt <fab...@ritter-vogt.de> --- Created attachment 110282 --> https://bugs.kde.org/attachment.cgi?id=110282&action=edit libinput list-devices Good news! (I think) The other threads are completely unrelated and waiting for events: Thread 4 (Thread 0x7fffdd6ab700 (LWP 26682)): #0 0x00007fffecb3af2b in poll () at /lib64/libc.so.6 #1 0x00007fffe6c74149 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fffe6c7425c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fffedee855f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #4 0x00007fffede8f4aa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x00007fffedcb68da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x00007fffedcbb8d0 in () at /usr/lib64/libQt5Core.so.5 #7 0x00007ffff02b1558 in start_thread () at /lib64/libpthread.so.0 #8 0x00007fffecb456df in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fffddeac700 (LWP 26681)): #0 0x00007fffecb3af2b in poll () at /lib64/libc.so.6 #1 0x00007fffe6c74149 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fffe6c7425c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fffedee855f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #4 0x00007fffede8f4aa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x00007fffedcb68da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x00007fffedcbb8d0 in () at /usr/lib64/libQt5Core.so.5 #7 0x00007ffff02b1558 in start_thread () at /lib64/libpthread.so.0 #8 0x00007fffecb456df in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fffde6ad700 (LWP 26680)): #0 0x00007fffecb3af2b in poll () at /lib64/libc.so.6 #1 0x00007fffe6c74149 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fffe6c7425c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fffedee855f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #4 0x00007fffede8f4aa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x00007fffedcb68da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x00007ffff2e96bd5 in () at /usr/lib64/libQt5DBus.so.5 #7 0x00007fffedcbb8d0 in () at /usr/lib64/libQt5Core.so.5 #8 0x00007ffff02b1558 in start_thread () at /lib64/libpthread.so.0 #9 0x00007fffecb456df in clone () at /lib64/libc.so.6 I found out that I can easily work around this by opening the lid while starting kwin_wayland. This seems to be caused by this: > sudo libinput debug-events -event3 DEVICE_ADDED Power Button seat0 default group1 cap:k -event4 DEVICE_ADDED Video Bus seat0 default group2 cap:k -event1 DEVICE_ADDED Lid Switch seat0 default group3 cap:S event1 SWITCH_TOGGLE +0.00s switch lid state 1 -event2 DEVICE_ADDED Sleep Button seat0 default group4 cap:k [...] some more DEVICE_ADDED -- You are receiving this mail because: You are watching all bug changes.
