Application: plasmashell (5.24.6) Qt Version: 5.15.5 Frameworks Version: 5.95.0 Operating System: FreeBSD 13.1-RELEASE-p2 amd64 Windowing System: X11 Distribution (Platform): FreeBSD Ports DrKonqi: 5.24.6 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Every time I login to KDE after a fresh boot, KDE crashes with a "Plasma (plasmashell) segmentation fault" error. The desktop disappears - no wallpaper or panels are visible. Applications like Konsole, Firefox, Thunderbird continue to run though. The only way to get back to normal is to restart Xorg and login to KDE again. This is on FreeBSD 13.1-RELEASE-p2. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault (lldb) process attach --pid 48636 (lldb) settings set term-width 200 (lldb) thread info (lldb) bt all Possible duplicates by query: bug 458927, bug 458852, bug 458841, bug 458829, bug 458807. Reported using DrKonqi
If something crashed, we need a backtrace of it so we can figure out what's going on. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports. Can you please attach one? Thanks!
(In reply to Nate Graham from comment #1) > If something crashed, we need a backtrace of it so we can figure out what's > going on. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports. > > Can you please attach one? Thanks! I've followed the steps from https://community.kde.org/Plasma/Debugging to attach gdb to the plasmashell process and wait for the crash to occur. But it hasn't happened again in the last 7 days. I assume that the backtrace captured with DrKonqi would have the required crash information. But if that information is not useful, then I'm not sure if there is any meaning to reporting a bug via DrKonqi. This is the "backtrace" captured by DrKonqi when the crash occurred, before I reported it... -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault (lldb) process attach --pid 48636 (lldb) settings set term-width 200 (lldb) thread info (lldb) bt all
Darn. Let's close this for now and we can re-open it if you experience the issue again.