Bug 311764

Summary:	Drkonqi should disable the "Report Bug" button when no debugger is installed and thus no backtrace can be obtained.
Product:	[Applications] drkonqi	Reporter:	Jekyll Wu <adaptee>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED NOT A BUG
Severity:	minor	CC:	4wy78uwh, mail
Priority:	NOR
Version:	2.1.5
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	backtrace tab when no debugger is availabel

Description Jekyll Wu 2012-12-16 08:58:21 UTC

Currently, drkonqi  shows some warning messages about no debugger, but the "Report Bug" button is still enabled. That is not good enough. It doesn't make sense to allow users to start the assistant at the first place in that situation.

That "Report Bug" button should be disabled in that case, until users have installed a debugger and pressed the "Refresh" button.





Reproducible: Always

Steps to Reproduce:
1. ensure gdb is not installed in the system
2. start konsole, and run "killall -6 konsole"

Actual Results:  
The "Report Bug" buttion is enabled.

Expected Results:  
The "Report bug" button is disabled

Comment 1 Jekyll Wu 2012-12-16 09:43:23 UTC

Created attachment 75863 [details]
backtrace tab when no debugger is availabel

Comment 2 George Kiagiadakis 2012-12-16 10:03:43 UTC

I disagree. In general, the backtrace tab is meant to be used by developers that want quick access to the backtrace. Normal users are meant to go directly from the main screen to the "report bug" dialog. Now the "report bug" dialog has a page where it generates a backtrace too. When users don't have the debugger software installed (gdb on linux), it will prompt them at that point to install it and reload the bactrace.

If you disable the "report bug" button, you will also need to have a visible indication on the main screen of why it is disabled, which I find no better than actually launching the dialog and being prompted there to install the debugger.

Comment 3 Jekyll Wu 2012-12-16 10:20:30 UTC

Yes, your argument is more convincing than mine. 

One related question is the "Debug" button in the screenshot. I think It should also be disabled in that case. But the "Debug"  button is also for developers (not even shown by default), so do you think that deserves a fix  or not?

Comment 4 George Kiagiadakis 2012-12-16 10:28:51 UTC

(In reply to comment #3)
> Yes, your argument is more convincing than mine. 
> 
> One related question is the "Debug" button in the screenshot. I think It
> should also be disabled in that case. But the "Debug"  button is also for
> developers (not even shown by default), so do you think that deserves a fix 
> or not?

No. The Debug button spawns a menu with the available debuggers. If no debugger is installed, it should show no options. However, even if the menu is empty, the button should not be disabled because it is possible that a debugger becomes available at a later point (for example, launching KDevelop while drkonqi is running offers an option to debug in KDevelop)