Bug 512575

Summary: DrKonqi refuses to report a crash, due to a non-existent component
Product: [Applications] drkonqi Reporter: Roke Julian Lockhart Beedell <4wy78uwh>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: sitter
Priority: NOR    
Version First Reported In: 6.5.3   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
URL: https://bugs.kde.org/describecomponents.cgi?product=kde
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: The Unreportable KCrash
A Screenshot, From DrKonqi, That Demonstrates That It Cannot Be Reported
Journal `77a69b58821c4f99ac4d4aa97d96aa11` Of Machine `427143abd98046a4b2c750e2ca0036ea`

Description Roke Julian Lockhart Beedell 2025-11-25 00:42:25 UTC 
Created attachment 187135 [details]
The Unreportable KCrash

# SUMMARY

DrKonqi refuses to report a crash, due to a non-existent component. The user should, instead, be able to at least direct the crash to the generic component.

# STEPS TO REPRODUCE

1. Have PlasmaShell crash.

2. Attempt to complete the manual report flow.

# OBSERVED RESULT

I saw “Failed to submit bug report: [51] There is no component named 'generic-crash' in the 'kde' product.”

# EXPECTED RESULT

It should have been reported to https://bugs.kde.org/enter_bug.cgi?product=kde&component=general.

# SOFTWARE/OS VERSIONS

> ~~~
> Operating System: Fedora Linux 43
> KDE Plasma Version: 6.5.3
> KDE Frameworks Version: 6.20.0
> Qt Version: 6.10.1
> Kernel Version: 6.17.8-300.fc43.x86_64 (64-bit)
> Graphics Platform: Wayland
> Processors: 16 × AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
> Memory: 32 GiB of RAM (30.6 GiB usable)
> Graphics Processor: AMD Radeon 780M Graphics
> ~~~
Comment 1 Roke Julian Lockhart Beedell 2025-11-25 00:44:00 UTC 
Created attachment 187136 [details]
A Screenshot, From DrKonqi, That Demonstrates That It Cannot Be Reported

Interestingly, resizing this window for the screenshot reproduced https://bugs.kde.org/show_bug.cgi?id=512527#c0.
Comment 2 Harald Sitter 2025-11-25 09:38:57 UTC 
Do you maybe have output from journalctl around that time? I'd like to know why the product failed to resolve for plasmashell.
Comment 3 Roke Julian Lockhart Beedell 2025-11-25 21:33:39 UTC 
Created attachment 187172 [details]
Journal `77a69b58821c4f99ac4d4aa97d96aa11` Of Machine `427143abd98046a4b2c750e2ca0036ea`

(In reply to Harald Sitter from comment #2)

> Do you maybe have output from journalctl around that time? I'd like to know
> why the product failed to resolve for plasmashell.

I believe so, although it doesn't appear very informative. See the attached log:

> ~~~
> RokeJulianLockhart@Beedell:~$ journalctl --list-boots -r
> IDX  BOOT ID                          FIRST ENTRY                 LAST ENTRY                 
>    0 b42ccd06cb2d4c43a2f6bef3ad1dc9ae Tue 2025-11-25 12:48:59 GMT Tue 2025-11-25 20:47:55 GMT
>   -1 77a69b58821c4f99ac4d4aa97d96aa11 Mon 2025-11-24 17:39:15 GMT Tue 2025-11-25 01:06:22 GMT
> ~~~

...specifically:

> ~~~
> Nov 24 23:46:45 drkonqi[81495]: QNetworkReply::HostNotFoundError "Host autoconfig.kde.org not found"
> Nov 24 23:46:45 drkonqi[81495]: ProtocolException: "Host bugs.kde.org not found" 3 "Host bugs.kde.org not found" "Host bugs.kde.org not found"
> Nov 24 23:46:45 drkonqi[81495]: "Host bugs.kde.org not found"
> Nov 24 23:46:45 drkonqi-coredump-launcher[81637]:            PID: 2762 (plasmashell)
> ~~~

I've removed the hostname from that excerpt, so re-add it if you try to `| grep` those lines.
Comment 4 Harald Sitter 2025-11-26 06:40:38 UTC 
Thanks.