Bug 196323

Summary:	Make the "Report bug..." in-application feature as painless to use as Dr. Konqi
Product:	[Frameworks and Libraries] kdelibs	Reporter:	Michael Liddle <michael>
Component:	kbugreport	Assignee:	kdelibs bugs <kdelibs-bugs>
Status:	REPORTED ---
Severity:	wishlist	CC:	andresbajotierra, wizard
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Unspecified
Latest Commit:		Version Fixed In:

Description Michael Liddle 2009-06-13 12:53:16 UTC

Version:            (using KDE 4.2.90)
Installed from:    SuSE RPMs

I don't know if this is the correct place to post this wish (does Dr. Konqi handle the "Report bug..." menu option), or whether it is already in the pipeline or not (there's a similar closed report already but I couldn't tell if it applied only to the crash reporting part). So apologies in advance if I'm out of step here :)

The new Dr. Konqi crash reporting feature is absolutely awesome. It completely takes all the pain out of using b.k.o. (in my experience). I don't know if you've seen a much higher rate of crash reporting since its introduction, but I'm certainly far more inclined to do so now; it almost make crash reporting a pleasure!

However I think it would be really useful if the "Help -> Report bug..." menu option in all KDE apps. also used such a streamlined dialog rather than opening up the b.k.o. website. 

I would also suggest considering changing the "Report bug..." to "Report bug/wish..." (emphasising that it's not just bugs that can be reported). Or perhaps even a separate "Make wish..." menu entry.

Just some ideas :)

Comment 1 Dario Andres 2009-06-20 21:57:20 UTC

First of all: thanks for your comments about DrKonqi. We are, indeed, getting better crash reports since we introduced it to KDE. 

The "Report bug" feature is not handled by DrKonqi but kdelibs. I'm reassigning.
I'm adding me to the CC so I can track this. May be we could work on your proposal in the future.

Thanks :)

Comment 2 Christoph Feck 2009-08-19 15:19:00 UTC

*** Bug 204319 has been marked as a duplicate of this bug. ***