Summary: | Sometimes when I wake up my two monitors from sleep, when I right click on the desktop to get the context menu, plasmashell crashes and then restarts. | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Ziad <ziadns> |
Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | kde, nate, ziadns |
Priority: | NOR | Keywords: | multiscreen |
Version First Reported In: | 6.0.4 | ||
Target Milestone: | 1.0 | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Backtrace of the crash.
Backtrace from coredumpctl gdb |
Description
Ziad
2024-05-24 21:50:07 UTC
More info from Info Center: Operating System: Manjaro Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.9.0-1-MANJARO (64-bit) Graphics Platform: Wayland Mesa Version: 24.0.6-1 Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT Thank you for the bug report! Unfortunately I can't reproduce the crash myself on current git master, and the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong. Could you please install debug symbols and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again! Created attachment 170438 [details]
Backtrace from coredumpctl gdb
Backtrace from coredumpctl gdb
I unfortunately, I couldn't access the gdb prompt in coredumpctl to type bt because I received the following error: Cannot access "/var/lib/systemd/coredump/core.plasmashell.1000.24c367af4f044862be148099e8cbd88f.22882.1716552437000000.zst": No such file or directory Darn. Unfortunately without that the backtrace is useless and unactionable. :( If this happens again, please feel free to open a new bug report, and make sure it has debug symbols. :) Your best bet is tro try using Arch's debuginfod server (see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Arch_Linux) because from what I can tell, Manjaro doesn't have its own yet. This is probably also something to bring up with the Manjaro folks (see https://forum.manjaro.org/t/any-fix-to-find-debug-symbols-for-stable-packages/140688). I posted a new bug report with a better explanation of the steps to reproduce and with a backtrace with debug symbols: Bug 488474 (https://bugs.kde.org/show_bug.cgi?id=488474). |