https://bugs.kde.org/show_bug.cgi?id=511524
Bug ID: 511524
Summary: Allow DrKonqi to be manually invoked on a
CoredumpCtl-saved corefile
Classification: Applications
Product: drkonqi
Version First 6.5.1
Reported In:
Platform: Fedora RPMs
URL: https://discuss.kde.org/t/can-dr-konqi-be-reinvoked-af
ter-closure/34410?u=rokejulianlockhart
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 186416
--> https://bugs.kde.org/attachment.cgi?id=186416&action=edit
An Example Of A Konqi OOM
# SUMMARY
When Dr. Konqi initially appears, myriad bugs can prevent it being able
initially report a bug, without at least a reinvocation: [^3]
1. Some cause it to fail to parse the trace. [^6]
2. Thereafter, in the past, graphical and UX bugs prevented certain pages being
passed, [^5] or prevented the user being able to fix past inputs [^4] (which
matters, because KDE BZ doesn't permit `#c0` to be modified).
3. Some continue to prevent reports, like OOMs, if the user neglects to close
all other applications when Dr. Konqi appears. Considering that the user cannot
choose when to report a crash with Konqi, this bug is the most prominent
problem for me, and why I reported this. [^2]
# STEPS TO REPRODUCE
1. Be debugging a game, like 0AD, or running a short, insignificant render in
Blender.
2. Crash something huge, like Plasma Shell, in the background. An example is
the automatic theme switching that causes
https://bugs.kde.org/show_bug.cgi?id=506642#c21.
# OBSERVED RESULT
My FW16, with 32 GiB of (DDR5) SDRAM, frequently OOMs in these circumstances.
# EXPECTED RESULT
Like I can with `gnome-abrt-1.4.3-8.fc43` and `abrt-cli-2.17.7-1.fc43`, I
expect to be able to invoke the crash report wizard via `drkonqi-coredump-gui`
when I want to, so that I can wait until I've finished with those tasks. As it
is, I've still lost those reports due to the OOM, but have also wasted time.
I end-up just reporting most crashes downstream, to RedHat, due to this:
1. https://bugzilla.redhat.com/show_bug.cgi?id=2411864#c0
2. https://bugzilla.redhat.com/show_bug.cgi?id=2411868#c0
# SOFTWARE/OS VERSIONS
> ~~~
> Name : plasma-drkonqi
> Version : 6.5.1
> Release : 1.fc43
> Architecture: x86_64
> Install Date: Sat 01 Nov 2025 18:30:12 GMT
> Size : 3598509
> Signature : RSA/SHA256, Thu 30 Oct 2025 18:55:45 GMT, Key ID
> 829b606631645531
> Source RPM : plasma-drkonqi-6.5.1-1.fc43.src.rpm
> Build Date : Thu 30 Oct 2025 10:44:47 GMT
> Build Host : buildhw-x86-09.rdu3.fedoraproject.org
> Packager : Fedora Project
> Vendor : Fedora Project
> Bug URL : https://bugz.fedoraproject.org/plasma-drkonqi
> ~~~
# ADDITIONAL INFORMATION
[^1]:
https://discuss.kde.org/t/how-to-edit-my-comments-in-bugs-kde-org/38510/8?u=rokejulianlockhart
[^2]:
https://discuss.kde.org/t/can-dr-konqi-be-reinvoked-after-closure/34410?u=rokejulianlockhart
[^3]: https://bugs.kde.org/show_bug.cgi?id=505075
[^4]: https://bugs.kde.org/show_bug.cgi?id=456770
[^5]: https://bugs.kde.org/show_bug.cgi?id=456768
[^6]: https://bugs.kde.org/show_bug.cgi?id=454411
--
You are receiving this mail because:
You are watching all bug changes.
