*** 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 I have a dual monitor setup with 4 desktop, and I have no idea what KDE session manager is doing. I will see window either where they should be or pop up in the wrong desktop over and over long after I have selected to "Save the session" and have setting set to restore session "When session was manually saved" Also the other annoying thing about "Save session" is there are no notification anything has happened after the button pressed. The button itself doesn't even show a feedback it is being pressed. STEPS TO REPRODUCE 1. Open windows and move then to different desktops. 2. Make sure session restore is set to restort from manually saved. 3. Saved session manually. 4. Reboot, session is not restored. OBSERVED RESULT 1. No windows are restored. 2. For multiple brave browser windows, one of them never remembers the desktop it should be restored when I open the brave browser and select "restore" because of another bug that fails to tell it to shut down correctly before reboot or shutdowm. KDE is a hot mess. I look forward for this and other bug not getting fix and being marked as dup! keep up the good work. EXPECTED RESULT Operating System: openSUSE Tumbleweed 20240426 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0
Thank you for your bug report! Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting), as this version of the KDE software is out of support from KDE, and so it's possible that the bug exists only in Debian at this point. Could you report the bug to Debian using the report bug utility (https://packages.debian.org/stable/utils/reportbug)? If necessary, the maintainer of the package will forward the bug upstream. Thanks for understanding!
Sorry I meant to do that for another bug report.