Bug 445954 - Unable to generate crash information from plasma-discover crash
Summary: Unable to generate crash information from plasma-discover crash
Status: RESOLVED WORKSFORME
Alias: None
Product: drkonqi
Classification: Applications
Component: backtraceparsing (other bugs)
Version First Reported In: 5.23.3
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-23 02:29 UTC by Alex
Modified: 2021-11-23 12:13 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Screenshot of drkonqi (43.79 KB, image/png)
2021-11-23 02:29 UTC, Alex 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alex 2021-11-23 02:29:41 UTC 
Created attachment 143854 [details]
Screenshot of drkonqi

I encountered this plasma-discover crash: https://bugs.kde.org/show_bug.cgi?id=443745

However, drkonqi seems to be unable to generate crash info for it, despite having gdb installed. I was able to manually use gdb to get a backtrace from this crash.

Maybe this is related to the fact that the crash did not appear in coredumpctl. In that case, the message that drkonqi displays should at least be more informative.

Distro: Fedora 34
Frameworks: 5.88.0
Comment 1 Alex 2021-11-23 11:11:44 UTC 
Sorry, I meant to say I'm on Fedora 35.
Comment 2 Harald Sitter 2021-11-23 12:13:08 UTC 
Not much to go on unfortunately. You could ask fedora to enable the coredump backend. It's much more reliable than the kcrash one. Chances are there was a segfault after the segfault this then screws up tracing.