Created attachment 168791 [details] Showing what is happening when the bug occurs. *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Open any app 2. Maximize it OBSERVED RESULT After clicking on any icon in the taskbar (WIFI, Sound, Clipboard, Vaults, etc.), a small window with more details should open. EXPECTED RESULT Should open the respective small window with their details. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION When the OS reboots, it returns to its original functionality. After maximizing any window, the only way to return is to reboot the OS again. I tried changing from floating to static style and had the same results.
I resolved the issue I was experiencing by reinstalling the operating system and deleting the .config file in the ~/home directory. This annoying bug prevented me from completing any task related to the system tray taskbar. I suspect the issue arose when I migrated from KDE Fedora 39, as I did not delete the .config file and kept the same desktop environment. It seems that some configurations from KDE 5 to 6 did not match properly, resulting in this problem. When utilizing the taskbar without floating, the system tray icon remains invisible even after a reboot. However, with the floating taskbar, the system-tray window reappears normally after a reboot or if the taskbar is removed and reinserted. It seems that maximizing the window may cause the floating taskbar to become fixed and trigger the bug.
From your last comment, it seems that you fixed this by removing your existing Plasma configuration. Does the issue still affect you, and can you still reproduce it on a current version of Plasma?
(In reply to cwo from comment #2) > From your last comment, it seems that you fixed this by removing your > existing Plasma configuration. Does the issue still affect you, and can you > still reproduce it on a current version of Plasma? No. After a fresh install, the bug was gone in any shape or form.
Thanks for reporting back. While this obviously shouldn't happen, I don't think there's anything more we can do here now that you can't reproduce the bug anymore. If the misbehavior comes back, please reopen this bug report or file a new one.