SUMMARY Since upgrading to Plasma 6.4.1 I can no longer move windows to specific activities using the X11 version of KWin. They disappear from the taskbar and correctly show within the taskbar on the intended activity but the window is present on all activities. It does not matter if Icon only Task manager is used or the Icon and text task manager. Previous versions of Plasma worked correctly (including 6.3 series). STEPS TO REPRODUCE 1. Make sure you have at least 2 activities active. 2. Open any application. Doesn't matter if it is a KDE app or not. 3. Right click the windows taskbar icon and click "Show in activities" > "Move to activity ACTIVITY_NAME" OBSERVED RESULT The application window remains on all activities. The taskbar icon for the application will disappear to the intended activity. EXPECTED RESULT The window should only be present on the intended activity. SOFTWARE/OS VERSIONS Operating System: KDE neon User Edition KDE Plasma Version: 6.4.1 KDE Frameworks Version: 6.15.0 Qt Version: 6.9.0 Kernel Version: 6.11.0-28-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6440HQ CPU @ 2.60GHz Memory: 32 GiB of RAM (31.1 GiB usable) Graphics Processor: Mesa Intel® HD Graphics 530 ADDITIONAL INFORMATION It does not matter if using the checkboxes or the Move to activity is used within Show in Activities context menu. The result remains the same. The window remains on all activities. It also does not matter if the X11 compositor is enabled or disabled. KActivityManager Activity manager seems to be running just fine with no errors in the journal. I've not yet tested the Wayland session. I don't use Wayland yet because session management still does not work there. I'm hopeful that will change though. Note this does not seem to be the same as issue #502022. Plasma 6.3 was fine for me and that seems to only happen to some windows under specific conditions and can be worked around. What I am seeing is no windows under any condition can be limited to a specific activity. Its as if "All activities" was chosen for the window.
I've created a new user on my machine to test a more vanilla setup. Unfortunately the X11 session is still broken in regards to placing windows on specific activities. However, I tested the Wayland session and it is working correctly there. I switched back and fourth between the two window sessions but activity windows remained broken on X11 and working on Wayland. I was surprised that I can still right click a window decoration to access the Activities context menu on Wayland as it does not show in X11 and after web searching a little I was under the impression it was removed from the window context menu in favour of moving it to the taskbar. I do much prefer accessing it within the windows context menu though as I find it more intuitive. Especially when you have a stack of windows of the same application.
The same problem here Operating System: KDE neon User Edition KDE Plasma Version: 6.4.1 KDE Frameworks Version: 6.15.0 Qt Version: 6.9.0 Kernel Version: 6.11.0-28-generic (64-bit) Graphics Platform: X11 Processors: 20 × 13th Gen Intel® Core™ i5-13600K Memory: 32 GiB of RAM (31.1 GiB usable) Graphics Processor 1: NVIDIA GeForce RTX 4070 SUPER Graphics Processor 2: Intel® Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7D36 System Version: 2.0
Just adding I've updated my system to Plasma 6.4.2 and the problem still persists. Activities are functionally useless at the moment on X11.
*** Bug 507067 has been marked as a duplicate of this bug. ***
I've just updated my KDE Neon installation and the problem seems to have been fixed! I can now use a window's context menu to move the window between different activities and it will only show in the chosen activities. The update upgraded Plasma to 6.4.3 so I guess there was a fix somewhere in there though going through the changelog does not mention anything related to resolving this bug. It does mention one bug related to activity workspaces in #501393 being fixed though that was different to this but maybe the changes fixed this issue? Who knows? Just glad the issue seems to have gone. I've left the issue open for now to give @serhumanos and @info@st11.link a chance to test with Plasma 6.4.3 and confirm the issue is fixed for them.
Seems to be fixed in Plasma 6.4.3