https://bugs.kde.org/show_bug.cgi?id=496251
Bug ID: 496251
Summary: "Switch desktop on edge" doesn't work in specific
condition(s)
Classification: Plasma
Product: kwin
Version: 6.1.5
Platform: Kubuntu
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: Hotcorners and edges
Assignee: kwin-bugs-n...@kde.org
Reporter: 3809940...@gmail.com
Target Milestone: ---
SUMMARY
I have virtual desktops enabled. Also "Switch desktop on edge" option is
enabled. So I can move to adjacent virtual desktops just by moving my cursor
there. After upgrading to KDE 6.1.5 (that is shipped with Kubuntu 24.10) I
started having problems switching between the virtual desktops.
STEPS TO REPRODUCE
Currently I only have evidence for mpv player. It happened with other
application(s) if I am remembering correctly, but I didn't note them. I will
update the issue if I encounter them again.
1. Open a movie file with mpv media player
2. Resize the window
3. Try to move the cursor to the screen edge to switch desktop
This is a semi reliable way to trigger this issue. Still it doesn't happen
every time when I follow these exact steps with the same file. That's why it is
hard to observe this problem. Resizing is the trigger in this situation (but as
I said it is not triggering every time).
OBSERVED RESULT
In the case above, window manager basically acts like this option is disabled:
"Switch desktop on edge"
Mouse cursor stops at the edge and doesn't switch to the next virtual desktop.
Sometimes it goes back to normal when I close this mpv player window. Sometimes
it stays stuck.
As a solution, I open a new Dolphin or Konsole window. This fixes the problem
and it starts switching desktops again.
EXPECTED RESULT
Cursor should continue to the next virtual desktop.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 24.10 / X11
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.6.2
ADDITIONAL INFORMATION
Applications like Firefox, Kate, Libreoffice, GIMP all work properly despite
different windowing toolkits. Considering the specific conditions for the
problem and probably low number of users affected, this looks like a pretty
minor problem to me. I am reporting this to provide more information in the
case that a similar problem is reported.
--
You are receiving this mail because:
You are watching all bug changes.
