Bug 434536 - "The debugger has quit unexpectedly." message in drkonqi
Summary: "The debugger has quit unexpectedly." message in drkonqi
Status: RESOLVED NOT A BUG
Alias: None
Product: drkonqi
Classification: Applications
Component: general (other bugs)
Version First Reported In: 5.21.2
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-17 09:44 UTC by Mohammed Sameer
Modified: 2021-05-27 17:54 UTC (History)
2 users (show)

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

Attachments
gwenview crash info (52.19 KB, image/png)
2021-03-17 09:44 UTC, Mohammed Sameer 		Details
developer information (46.88 KB, image/png)
2021-03-17 09:45 UTC, Mohammed Sameer 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mohammed Sameer 2021-03-17 09:44:10 UTC 
Created attachment 136777 [details]
gwenview crash info

SUMMARY
"The debugger has quit unexpectedly." message in drkonqi, when trying to report gwenview crash.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.21
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-67-generic
OS Type: 64-bit
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-5010U CPU @ 2.10GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

ADDITIONAL INFORMATION
I was trying to play a video in gwenview, then it crashed.
Comment 1 Mohammed Sameer 2021-03-17 09:45:14 UTC 
Created attachment 136778 [details]
developer information
Comment 2 Harald Sitter 2021-03-23 11:50:32 UTC 
Unfortunately there's nothing to go on here. Is this reproducible at all?
Comment 3 Mohammed Sameer 2021-03-24 07:11:39 UTC 
I cannot reproduce this issue.
Comment 4 Harald Sitter 2021-03-24 11:37:50 UTC 
Then we can't really do anything about it. It's possible that gwenview terminated before the debugger started. There is a window of time inbetween a crash and the debugger starting up where the application could crash *again* and disappear entirely. There are some technical elements in the work that will catch this in the future hopefully.