SUMMARY 4 finger touchpad swipe up/down very inconsistent over time. STEPS TO REPRODUCE 1. Open several windows of any type. 2. Use that desktop for 5-10 min. 3. Attempt to swipe up using 4 finger touchpad gesture, sensitivity/rate/etc has changed significantly over time, and then improves after multiple attemps. OBSERVED RESULT It seems this is a time sensitive bug. Swipe up with 4 fingers works fine if done immediately after boot, or if done often (within 10s or so of a swipe). But wait some number of minutes, say 10, and 4 finger swipe up may not work at all. Using 3 finger swipe to move L/R (which works fine), then, using 4 finger swipe works as expected. The 4 finger swipe also seems to be worse (happen sooner, and be less sensitive) if swiping while a window is in full desktop mode. EXPECTED RESULT Consistency when using 4 finger swipe over a period of time and using various desktop configurations. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION
are you on Wayland or X11?
Wayland.
It will probably be useful if you can - immediately after noticing an issue with the overview effect (4-finger swipe up) - to run this command in a terminal and attach the resulting kwin.log file: journalctl --user SYSLOG_IDENTIFIER=kwin_wayland -S -1m > kwin.log
Thanks, will do, soon.
So it seems, that when this 4-finger swipe problem happens, if I use the mouse to un-hide the panel to open a termnial (to run the requested command), then the 4 finger swipe works fine. Making it difficult to run the requested time when the problem is happening. I'll try writing a script to run the command every 30s or so.
(In reply to freedriven from comment #5) > So it seems, that when this 4-finger swipe problem happens, if I use the > mouse to un-hide the panel to open a termnial (to run the requested > command), then the 4 finger swipe works fine. Making it difficult to run the > requested time when the problem is happening. That is fine - the command is to extract the log for the last minute. You don't have to execute "as it happens", only not more than a minute after it happened.
I've run it a few times after the 4 finger swipe basically stopped working. I've only gotten: "-- No entries --"
(In reply to freedriven from comment #7) > I've run it a few times after the 4 finger swipe basically stopped working. > I've only gotten: > "-- No entries --" Are you sure you are running on Wayland?
wayland is selected at login. Also: loginctl shloginctl show-session "$XDG_SESSION_ID" -p Type Type=wayland
OK, on my system kwin logging is set to debug level so it is quite noisy, though higher level log messages from kwin are actually rare. Maybe you can enable debug logging and see if there's anything interesting.
I think I finally caught it. Output of "journalctl --user SYSLOG_IDENTIFIER=kwin_wayland -S -5m" Jul 19 10:46:28 Home666 kwin_wayland[1944]: This plugin does not support raise() Jul 19 10:46:28 Home666 kwin_wayland[1944]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT) Jul 19 10:46:28 Home666 kwin_wayland[1944]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT) Jul 19 10:46:28 Home666 kwin_wayland[1944]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT) Jul 19 10:46:28 Home666 kwin_wayland[1944]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT) Jul 19 10:46:28 Home666 kwin_wayland[1944]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT) Repeat last line about 10 times.