| Summary: | Plasma (plasmashell) segmentation fault | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | underpinnedd |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | kde, nate |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.24.6 | ||
| Target Milestone: | 1.0 | ||
| Platform: | FreeBSD Ports | ||
| OS: | FreeBSD | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
underpinnedd
2022-09-11 07:31:25 UTC
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. |