Bug 319043

Summary:	Bug reporting tool is buggy
Product:	[Applications] drkonqi	Reporter:	bkorb
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED DOWNSTREAM
Severity:	major	CC:	mail, sitter
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description bkorb 2013-04-29 02:07:48 UTC

I've had several crashes today, April 28, 2013.  openSuSE 12.3 x86-64
The bug reporting tool pops up, asks if I am willing to install debug info for the various crashing programs, I say "yes", it sees that they are already installed, and asks me again if I'd like to install the debug info.  After looping through this a couple of times, I now have to just dismiss the pop-under window (a "special feature" with focus follows mouse).  It's happened enough that I'm going to the trouble to file this bug report so I can also ask you to please find a way to shut up that pop under because I do not want to try to file a bug when it is impossible to do so.

Reproducible: Always

Steps to Reproduce:
1. trip on a bug that fires the debug report tool
2. download the relevant debug info
3. trip on the bug again.
Actual Results:  
infinite request loop

Expected Results:  
1. the original programs would not crash (digikam and some helper program for saving a jpg image from thunderbird)
2. the bug reporting tool would not be buggy

If you are going to ask someone to report a bug with a reporting tool, for gosh sakes make sure the thing is rock solid.

Comment 1 bkorb 2016-03-16 16:54:37 UTC

"Ping"  This has been so consistently true through the years I must conclude that nobody considers it important that KDE crashes get reported with debug information.  Is this true?  It's three years later now and it still happens and has happened every (and many) times.

Comment 2 Harald Sitter 2019-07-02 13:59:43 UTC

Sounds like your distribution's debug installer is not very reliable. This is outside our reach.

Comment 3 Harald Sitter 2019-07-02 14:03:00 UTC

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