Bug 375813 - DrKonqi can't report error because address is missing
Summary: DrKonqi can't report error because address is missing
Status: RESOLVED WORKSFORME
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: drkonqi
: 378390 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-01-31 19:39 UTC by pbhj
Modified: 2019-07-14 04:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pbhj 2017-01-31 19:39:34 UTC
Dolphin crashes and a dialog labelled "dolphin" is displayed. The dialog doesn't name the application it is created by but I assume from examining ps output that it's drkonqi.

drkonqi says "dolphin does not provide a bug reporting address" and so it can't report the [numerous] crashes that happen. Sadly it doesn't report where the address should be either.

drkonqi says dolphin is at fault hence reported here rather than as a bug on drkonqi. Other programs crash and reports work successfully, dolphin bug reporting definitely worked recently.

Dolphin 16.04.3
KDE Frameworks 5.28.0
Qt 5.6.1 (built against 5.6.1)
The xcb windowing system
Kubuntu 16.04
Comment 1 Elvis Angelaccio 2017-02-01 15:15:06 UTC
Dolphin does not set a specific address, which means it should use the default one. Do you have the "Report Bug..." button in the Help menu?
Comment 2 pbhj 2017-02-02 19:21:51 UTC
Thanks for looking Elvis - yes I do have the Report button and it opens this URL "https://bugs.kde.org/enter_bug.cgi?format=guided&product=dolphin&version=16.04.3" if I "Launch Bug Report Wizard".
Comment 3 pbhj 2017-02-02 21:47:43 UTC
I've reinstalled 2 packages:

>Setting up kde-runtime-data (4:16.04.3-0ubuntu2~ubuntu16.04~ppa61) ...
>Setting up plasma-workspace (4:5.8.5-0ubuntu2~ubuntu16.04~ppa2) ...

Also discovered and used 'kdebugdialog' and selected "drkonqi": which was listed twice, the one without numbers was deselected so I selected it.

Opened dolphin and forced a crash report using 'killall -SIGABRT dolphin'. 

Seems to be working correctly again!
Comment 4 Elvis Angelaccio 2017-04-03 17:59:43 UTC
*** Bug 378390 has been marked as a duplicate of this bug. ***
Comment 5 pbhj 2017-05-14 21:56:47 UTC
It's more weird: on crash now (attempting to open from the device pop-up menu in the kde tray on Kubuntu) the "report" button is again greyed out. There is no longer a duplicate entry as there was in my previous report; if I load dolphin in the normal way and send a sigabrt then I do get an active "report" button, so it seems it's situational as to whether dolphin (or is that drkonqi) can get the address or not.
Comment 6 Harald Sitter 2019-06-14 14:31:56 UTC
This would be a problem in kcrash or dolphin. KCrash picks the bug report address out of KAboutData, if that is not correctly set then kcrash doesn't know the address, doesn't forward it to drkonqi and then drkonqi cannot report the bug because it doesn't know where to report it.

Can you still reproduce the problem?
Comment 7 Bug Janitor Service 2019-06-29 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2019-07-14 04:33:10 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!