Hi all,
KDE Neon 24.04 noble stable. I’ve been experiencing this very frustrating issue where text selection is very finnicky. This is happening both in Chrome, Slack, Discord, and Firefox. Even when only one runs. It’s very simple, it seems the click event doesn’t seem to be registered properly, and it doens’t select anything. The mouse position is detected correctly and things like buttons do highlight but the click event doesn’t go through. I’m running 4 monitors on an x1 carbon, and it seems to occur on all monitors.
I can not figure what is causing it, and while the biggest effect is text selection, it also messes with window focus itself.
Libinput does show the events properly, for example this was an attempt to select text in a chrome window that didn’t work
$ sudo libinput debug-events
[…]
event17 POINTER_BUTTON +16.469s BTN_LEFT (272) pressed, seat count: 1
[…]
event17 POINTER_BUTTON +17.826s BTN_LEFT (272) released, seat count: 0
Running KWin.showDebugConsole I do see all events… but strangely enough, as the debug runs, and it slows down all events processing due to the amount of data to display… the bug mostly vanishes.
I am a bit puzzled, thoughts?
sounds like you have some unique settings under window behavior with window actions and pass click settings (wild guess).
i would run thru all the tabs and double check your settings, esp focus and window actions.
you can also just try resetting everything to defaults using the button at the bottom and see if that helps.
also check window rules to make sure you haven’t configured something odd.
So interestingly this seems to come in “waves”. Suddenly I can’t select using click drag, and then after a couple seconds it works again. It’s extremely intermittent, and sometimes it does not happen for minutes. It seems to be possibly caused by a spike in something? but there’s no cpu or io spike at that moment.
I tried resetting all window behavior, but everything was already at default as far as I can see.
There’s only one window rule bound to a single app that runs rarely.
It doesn’t seem to happen with X11 so I suspect this is something wayland related. Maybe related to clipboard since text selection also activates copy? Or some sort of GC mechanism…
This definitely appears to be wayland related. Even with chrome running on ozone+wayland, it always felt laggy and a bit delayed in text selection/click interactions. I’ve been running in x11 mode and while it has other issues(mostly performance and display performance) it does not have any of those pesky text selection issues. Is this worth create a bug for? I can relatively easily reproduce the issue and run debug while it happens. happy to run/build debug binaries too.
So I was wrong, it does occur in X11 mode. I just changed the scaling to be from system managed to app managed, and I hope that this will solve it. So far it seems better. But as this is intermitent…