Bug 433779 - DrKonqui refuses to submit a bug report
Summary: DrKonqui refuses to submit a bug report
Status: RESOLVED INTENTIONAL
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Stefan Brüns
URL:
Keywords: usability
: 441780 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-03-01 08:12 UTC by Dan Dascalescu
Modified: 2023-04-24 21:16 UTC (History)
4 users (show)

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


Attachments
baloo_file_extractor crash screenshot (51.09 KB, image/png)
2021-03-01 08:12 UTC, Dan Dascalescu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Dascalescu 2021-03-01 08:12:12 UTC
Created attachment 136274 [details]
baloo_file_extractor crash screenshot

Baloo crashed when I started a Wayland session (`dbus-run-session startplasma-wayland`) and I couldn't report the creash.
Comment 1 Stefan Brüns 2021-03-02 18:21:11 UTC
IMHO thats a bug in drkonqui. If not passed an address explicitly, it should use its default, it already has one:

https://invent.kde.org/plasma/drkonqi/-/blob/master/src/bugreportaddress.h#L20
Comment 2 Nate Graham 2021-03-02 20:20:47 UTC
DrKonqi should be improved too, to send bugs with no address to the generic "kde" component.

However baloo_file_extractor crashes should definitely come here, and we should make sure that an appropriate address is defined.

Dan, can you file a separate bug report asking for DrKonqi to send bugs with undefined addresses to the generic "kde" component? Thanks!
Comment 3 Harald Sitter 2021-03-03 21:57:17 UTC
You need to add your product mappings to https://invent.kde.org/plasma/drkonqi/-/blob/master/src/data/mappings routing to 'kde' when mapping is missing is part of some other report somewhere already
Comment 4 Harald Sitter 2021-03-03 22:16:15 UTC
Oh actually that's only part true. I believe the problem is that you need to have kaboutdata, that's how we expect the report address to be set in kcrash.
Comment 5 Nate Graham 2021-03-04 14:33:36 UTC
Ah, and it was removed in https://phabricator.kde.org/D28940. I guess that's the proximate cause of this regression.
Comment 6 Stefan Brüns 2021-03-04 15:03:50 UTC
So why should we configure a default address in multiple locations? Bugzilla obviously already has default assignees.

DrKonqui will use a default address when the aboutdata has "submit@bugs.kde.org", silently accept "no-longer-exists@bogus.org", but complains about an empty string.
Comment 7 Harald Sitter 2021-03-05 11:16:43 UTC
It is not. The application sets the address in applications scope. When it crashes KCrash forwards the address to Drkonqi. Drkonqi checks if that address is OUR address and if so it routes the report to bugzilla. When it is not our address it instead tells the user to send the report that was generated as a mail to the divergent address. When no address was provided drkonqi doesn't know what's what and shrugs because it hasn't gotten the information it requires to determine what to do.
Comment 8 Stefan Brüns 2021-03-05 17:07:54 UTC
(Whatever "It is not" refers to)

The fact you have to set an address is specified neither in KCrash nor in any DrKonqu documentation.

If one default-constructs KAboutData, the bugAddress is implicitly set, so apparently it is sane to expect the default to be the KDE bugzilla.

KCrash knows if KAboutData has been set - why can't it provide the same default as KAboutData?

Why does DrKonqui require an explicit bugaddress, and does not default to submits@bugs.kde.org if it is not specified? If someone wants to override it, fine, but why specify a default value?
Comment 9 Nate Graham 2022-11-30 17:12:48 UTC
*** Bug 441780 has been marked as a duplicate of this bug. ***
Comment 10 Stefan Brüns 2023-04-24 21:16:57 UTC
The kcrash framework should provide and use a sane default.

Anything explicitly set in the application is prone to become outdated.