Bug 444195 - Certain UI elements in some applications stop responding to clicks
Summary: Certain UI elements in some applications stop responding to clicks
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.22.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-21 14:22 UTC by Linus Kardell
Modified: 2021-11-05 21:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Linus Kardell 2021-10-21 14:22:40 UTC
SUMMARY
Sometimes some UI elements in various applications stop responding to clicks, and instead trying to click it activates the UI element behind it. Symptoms I've noticed is that you stop being able to click scrollbars and editor pop-ups in VSCode, and merge arrows and crosses in Meld. You also stop being able to drag folders in the bookmarks toolbar in Firefox.

I haven't been able to find any exact steps to reproduce it, but it tends to happen when I've been on a different activity or desktop and then switch back to the activity/desktop with the application on it it. It then starts responding normally again if I click a different window and go back to the affected window. It also tends to happen when I bring up Yakuake. Not sure exactly where the the bug is, whether it's due to kwin, or something in GTK, or in the applications themselves (but that would be unlikely since I see similar issues in multiple unrelated applications).

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20211012
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.14.9-1-default (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 62.7 Gibyte of RAM
Graphics Processor: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2
Comment 1 Nate Graham 2021-10-21 17:35:03 UTC
KWin isn't responsible for input on X11; seems like an X server or input driver problem?
Comment 2 Linus Kardell 2021-11-02 14:04:30 UTC
Perhaps. Don't see how it would be a driver though, the clicks still go to the application, just to the wrong part of it, but I don't know much about that.
Comment 3 Linus Kardell 2021-11-05 14:36:36 UTC
Also reported at https://bugzilla.opensuse.org/show_bug.cgi?id=1192388 and https://github.com/microsoft/vscode/issues/133371.

Guess it's not a KDE issue, because it also happens in IceWM (and way more consistently at that).
Comment 4 Nate Graham 2021-11-05 21:15:06 UTC
OK, thanks!