| Summary: | Enabling/disabling Night Color will sometimes lead to a hard crash of the system | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Paul Meier <public.paul.meier+kde> |
| Component: | Brightness and Color widget | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | cwo.kde, kdedev, natalie_clarius, nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.1.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Paul Meier
2024-09-08 16:56:21 UTC
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! (In reply to TraceyC from comment #1) > 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! There is no coredump I can provide because the system crashes in a way, that absolutely nothing is logged. I assume I would need to run the entirety of Plasma in a way that everything is logged immediately. I don't know how to achieve such logging however. > There is no coredump I can provide because the system crashes in a way, that > absolutely nothing is logged. > I assume I would need to run the entirety of Plasma in a way that everything > is logged immediately. > I don't know how to achieve such logging however. Can you try the steps outlined in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB? Basically installing gdb, then running plasmashell inside gdb until the crash occurs. Sometimes this will help if no crash report/coredump is automatically generated. If the system is actually hard-crashing, it might well be a graphics card or kernel bug. Just to make sure, you see nothing relevant in "journalctl -S today" after the crash happens (and rebooting)? (In reply to cwo from comment #3) > > There is no coredump I can provide because the system crashes in a way, that > > absolutely nothing is logged. > > I assume I would need to run the entirety of Plasma in a way that everything > > is logged immediately. > > I don't know how to achieve such logging however. > > Can you try the steps outlined in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB? > Basically installing gdb, then running plasmashell inside gdb until the > crash occurs. Sometimes this will help if no crash report/coredump is > automatically generated. I will do this when I have time, thanks. > If the system is actually hard-crashing, it might well be a graphics card or > kernel bug. Just to make sure, you see nothing relevant in "journalctl -S > today" after the crash happens (and rebooting)? It is actualkly hard-crashing. I assume that nightcolor triggers some crash of amdgpu, but this crash really only happens in Plasma. journalctl shows absolutely nothing, the time of the crash is never even in it, because the system crashes so abruptly. If it's crashing, then there's a coredump and you can get a backtrace. If there's no coredump, there's actually no crash. This could be a sign that something is not crashing, but rather exiting, perhaps with a Wayland protocol error. Can you be specific about what exactly is happening? When you say "The system will hard crash", please be very specific about what's happening that leads you to this conclusion. (In reply to Nate Graham from comment #5) > If it's crashing, then there's a coredump and you can get a backtrace. If > there's no coredump, there's actually no crash. This could be a sign that > something is not crashing, but rather exiting, perhaps with a Wayland > protocol error. > > Can you be specific about what exactly is happening? When you say "The > system will hard crash", please be very specific about what's happening that > leads you to this conclusion. I am currently not able to work on my system as I am not home, but let elaborate on the crash as expected. I can replicate this crash everytime, but it happens at different times. Sometimes I can switch night colour on and off many times and nothing happens. If the crash occurs the system will stop entirely, meaning that any output from the system stops and it becomes completely unresponsive. The monitors do display the last image that was shown while the crash occured. SSH'ing into the system, switching to TTY or trying SysRQ to reboot the system all do not work, the system is indeed completely unresponsive. I wrote in an earlier comment that I suspect amdgpu to be crashing, because those crashes looked and behaved similarly. The issue is, that no other GUI I've tried (Gnome/Hyprland) were able to cause this crash in my testing. It only occurs in KDE Plasma. I will attach the logs from running plasmashell with gdb when I am able, though this will have to wait a few days. . 🐛🧹 ⚠️ 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. |