Created attachment 181030 [details] kcrash-report-file STEPS TO REPRODUCE 1. on every systemstart OBSERVED RESULT crash of plasmashell, black screen EXPECTED RESULT working plasmashell After starting Plasma (auto-login), the background image and taskbar load. Then the screen goes black, the image and taskbar disappear, and a crash handler window from "plasmashell" opens. I can write a bug report, but during that time, Plasma reloads and crashes a total of five times. Each time, a new crash handler window opens. I can launch krunner with Alt+F2 and launch some programs: Sysmon, Brave, but Kmail, for example, also crashes. The error keeps occurring, presumably since the last update to KDE Frameworks 6.13 last week. I was able to temporarily resolve the issue by switching from Nouveau to the proprietary NVIDIA driver. I have attached a kcrash bug report. By the way: I'm also having problems with gdb since some month, which regularly floods RAM after crashes. This happens here too, but it's probably an unrelated bug. From the KDE Info Center: Operating System: KDE neon 6.3 KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.13.0 Qt Version: 6.9.0 Kernel Version: 6.11.0-25-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4460 CPU @ 3.20GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 750 Ti Manufacturer: MSI Product Name: MS-7817 System Version: 1.0
Thanks, but I'm afraid the file you attached has no backtrace of the crash in it. We need this to debug it. Can you follow the instructions at https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl and get one? Thanks!
(In reply to Nate Graham from comment #1) > Thanks, but I'm afraid the file you attached has no backtrace of the crash > in it. We need this to debug it. Can you follow the instructions at > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > and get one? > > Thanks! Remember: "I'm also having problems with gdb since some month, which regularly floods RAM after crashes. This happens here too, but it's probably an unrelated bug." Gdb produces some GB in RAM until the system collapses. I solve this problem by killing gdb. No gdb - no backtrace, sorry. Maybe I need to solve this problem first. If you have any ideas, let me know.
If there's no backtrace, then unfortunately we can't debug the issue. You'll need to sort out that issue first.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.