| Summary: | drkonqi writes SIGABRT corefile after ksecretd crashes | ||
|---|---|---|---|
| Product: | [Applications] drkonqi | Reporter: | Christian Hacker <sw4> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | crash | CC: | kdedev, mk.mateng |
| Priority: | NOR | ||
| Version First Reported In: | 6.5.4 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=514326 https://bugs.kde.org/show_bug.cgi?id=500179 https://bugs.kde.org/show_bug.cgi?id=514517 |
||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
journald log drkonqi SIGABRT corefile messages
journald log kded6 SIGABRT corefile messages |
||
|
Description
Christian Hacker
2026-01-11 06:51:16 UTC
Created attachment 188410 [details]
journald log kded6 SIGABRT corefile messages
> The Kde desktop screen was locked by the user at that time; with the external display
> switched off.
> The Kde user was already logged out, or may have been in the process of logging out
> of the desktop, at the times of the other instances of this problem.
As noted in the other issue, this is probably the main cause for the DrKonqi SIGABRT.
A suggestion to the devs: if something crashes outside of an active GUI session (e.g. when it's locked), could the DrKonqi start up be delayed until the session is activated? At that point, DrKonqi could look back at unreported crash logs, and show the necessary dialogs retroactively. (In reply to michaelk83 from comment #3) > A suggestion to the devs: if something crashes outside of an active GUI > session (e.g. when it's locked), could the DrKonqi start up be delayed until > the session is activated? At that point, DrKonqi could look back at > unreported crash logs, and show the necessary dialogs retroactively. That's not a bad suggestion, but it needs its own report. Please open a new bug report as "wishlist" so the developers can consider the feature request. (In reply to TraceyC from comment #4) > That's not a bad suggestion, but it needs its own report. It was offered as a direct solution to this issue. |