STEPS TO REPRODUCE 1. You have two or more activities enabled. 2. You are in "activity X" and need to switch to "activity Y". 3. Switch using shortcut or by clicking on the plasmoid (either way works). 4. Now try to open the launcher. It will be behind the program windows. 5. Now try to open a program menu. It will also appear behind the windows. 6. Right-click on the title bar. The Kwin menu will also be behind the windows. 7. Therefore: IT IS IMPOSSIBLE TO USE THE SYSTEM MENUS. OBSERVED RESULT The observed result is that all menu windows are behind the application windows. EXPECTED RESULT The expected result is that this should not happen. SOFTWARE/OS VERSIONS Operating System: Garuda Linux KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.12.1-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Xeon® CPU E5-2620 v3 @ 2.40GHz Memory: 62.6 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series Manufacturer: HUANANZHI ADDITIONAL INFORMATION To get the menus working normally, keep switching between activities until it returns to normal. It may take one, two, or more attempts for it to return to normal. But the simple fact of being normal and switching activities, the risk of the next activity having this defect is almost certain. Rarely does it not occur this way. It doesn't matter if it's Wayland or Xorg.
Enabling the "Slide Back" Desktop Effect can cause behaviour like this (see bug #455429), do you have that enabled?
(In reply to Paul Worrall from comment #1) > Habilitar o efeito de desktop "Slide Back" pode causar um comportamento como > este (consulte bug #455429), você tem isso habilitado? Hello Paul, thank you for shedding light on the issue. From what I understand, the solution would be: A: Disable the effect in question. B: Toggle Kwin on and off with alt + shift + f12. I checked, and this is likely the problem. Now, I'm curious. Will this error be corrected at some point, given that it was reported in 2022? Thank you.
Sorry, I cannot comment on when bug #455429 will be fixed. *** This bug has been marked as a duplicate of bug 455429 ***