Created attachment 176523 [details] Journactl -b log SUMMARY Plasma shell crashes on idle when monitors turns off need to restart it with systemctl --user restart plasma-plasmashell.service after long periods monitors wont turn on anymore need to force reboot STEPS TO REPRODUCE 1. Set display and Brightness to turn off screen 10min 2. Let computer monitor to turn off and leave it for a while 3. Wake up screen by moving mouse or pressing keyboard button OBSERVED RESULT Plasmashell is crashed no desktop and panel appears EXPECTED RESULT Desktop and panel should come visible when screen turns on SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.1 ADDITIONAL INFORMATION Processor 5800x ryzen GPU 6700xt AMD Memory 32GB CL 16 Mesa 1:24.3.1-3 Kernel 6.12.4-zen1-1-zen
If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the `coredumpctl` command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Thanks!
Possibly it's not a crash but rather something like Bug 496923, especially if you check and there's no actual crash. Are you using X11 or Wayland? Do you have multiple screens?
Created attachment 176541 [details] backtrace copied from coredumpctl gdb
(In reply to Nate Graham from comment #2) > Possibly it's not a crash but rather something like Bug 496923, especially > if you check and there's no actual crash. > > Are you using X11 or Wayland? > > Do you have multiple screens? Using wayland I have two monitors but 2nd monitor is always disabled unless I need to do something special. It always on though so I can wake it with hotkey if I want to. I added text to attachments what I got from coredumpctl gdb
Hmm, unfortunately the backtrace is almost all question marks, so not very useful. Can you follow the Arch Linux instructions to get debuginfod running and then get a new backtrace?
(In reply to Nate Graham from comment #5) > Hmm, unfortunately the backtrace is almost all question marks, so not very > useful. Can you follow the Arch Linux instructions to get debuginfod running > and then get a new backtrace? Hmm actually that coredumpctl --reverse crash which I had might not be related. I think my issue might be same as this, but on wayland. https://bugs.kde.org/show_bug.cgi?id=496923 . I tried to follow arch wiki for backtracing, but I got exact same results.
🐛🧹 ⚠️ 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.