445436 2021-11-13 17:57:01 +0000 [Wayland] On multi screen setups, moving a window to a different workspace makes it flicker and also stay visible on the current workspace 2021-12-04 12:34:49 +0000 1 1 4 Plasma kwin wayland-generic 5.23.3 Arch Linux Linux RESOLVED DUPLICATE 444172 NOR normal --- 0 firlaevhanskde.upstream314 kwin-bugs-null dev.bacteriostat nate 0 oldest_to_newest 2077341 0 firlaevhanskde.upstream314 2021-11-13 17:57:01 +0000 SUMMARY On Wayland, when I use a keyboard shortcut to move a window to a different workspace / virtual desktop on a system with two monitors, the window flickers a lot, but stays visible on the current workspace. Clicking it makes it disappear, though while it is still visible you can use a keyboard shortcut again to move it to yet another workspace (or back to the current one). This issue does NOT occur with just one monitor (but I think it used to). It also does NOT occur if instead of a keyboard shortcut, the Alt+F3 menu is used to move the window to a different workspace STEPS TO REPRODUCE 1. Be on Wayland and have more than one monitor 2. Have >1 workspace and set KWin keyboard shortcuts for moving a window to a specific workspace 3. Use the shortcut to move a window to a different workspace OBSERVED RESULT The window flickers and stays visible on the current workspace even though it was moved to a different one EXPECTED RESULT The window should simply disappear since it is no longer supposed to be on that workspace. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.16-zen1-1-zen (64-bit) Graphics Platform: Wayland ... and also on KDE Neon unstable 2082608 1 dev.bacteriostat 2021-12-04 12:29:25 +0000 Your description looks very similar to mine issue with moving windows with shortcuts to other activities and virtual desktops. https://bugs.kde.org/show_bug.cgi?id=444172. 2082611 2 firlaevhanskde.upstream314 2021-12-04 12:34:49 +0000 Indeed, that seems to be the same issue. *** This bug has been marked as a duplicate of bug 444172 ***