Created attachment 142141 [details] screenshot SUMMARY Every time I try to report a Discover crash, I get the result seen in the attached screenshot. EXPECTED RESULT drkonqi should report Discover crash SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 Graphics Platform: Wayland
https://invent.kde.org/plasma/discover/-/commit/7674dae2c3b7c52f4552300b416616f0ce647759 bugaddress mustn't be set (when using bugzilla), or must be submit@bugs.kde.org
Ugh, this is messy. We set bugaddress in Discover to support the new Kirigami "report a bug action" that appears by default in the About page. I guess it's a classic "multiple sources of truth" problem, since that action in Discover pulls its bug reporting URL from the app itself, whereas DrKonqi pulls its data from a separate repo/location. Could we make DrKonqi introspect the value of bugaddress in the app to see if it matches the value that's set elsewhere, maybe? Or make the Kirigami action able to see the URL from the other place, if not overridden in the app?
After commenting the line that adds the bug address URL to the aboutData DrKonqi works as expected. bug reported for testing through DrKonqi after commenting that line: #443362
This seems more like a DrKonqi bug than a Discover one to me...
(In reply to Nate Graham from comment #2) > Ugh, this is messy. We set bugaddress in Discover to support the new > Kirigami "report a bug action" that appears by default in the About page. I > guess it's a classic "multiple sources of truth" problem, since that action > in Discover pulls its bug reporting URL from the app itself, whereas DrKonqi > pulls its data from a separate repo/location. > > Could we make DrKonqi introspect the value of bugaddress in the app to see > if it matches the value that's set elsewhere, maybe? No, the app has crashed, we can't ask it anything ;) I haven't given this any thought but it seems to me kirigami needs to assemble KAboutData::bugAddress, ::productName and ::componentName to the actual bugs.kde.org address (if submit@bugs.kde.org was used as address). That is how this works in kbugreportdialog and drkonqi ultimately.
If DrKonqi can't ask the app for anything after it crashed, how can it get confused by the app setting its own bug address internally?
It gets the data passed along by kcrash which excavates it from kaboutdata.
Gotcha. Felipe, would you be able to investigate possible fixes? Thanks!
*** This bug has been marked as a duplicate of bug 444554 ***