| Summary: | plasmashell crash on startup 6.0.4 | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Elite <eliteamdgaming> |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | nate |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 6.0.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 6.1.1 | |
| Sentry Crash Report: | |||
|
Description
Elite
2024-04-18 21:06:02 UTC
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: > #4 0x000078c16d78a1d6 in ??? () at /usr/lib/qt6/qml/org/kde/plasma/private/kicker/libkickerplugin.so If you can still reproduce the issue in Plasma 6.1.4 or newer, could you please 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! (In reply to Nate Graham from comment #1) > 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: > > > #4 0x000078c16d78a1d6 in ??? () at /usr/lib/qt6/qml/org/kde/plasma/private/kicker/libkickerplugin.so > > If you can still reproduce the issue in Plasma 6.1.4 or newer, could you > please 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! Thankfully I think it was fixed back in 6.1.1. I found at the time changing kernels stopped it. I've since swapped the kernel back and no issues since then. Fantastic news! |