Bug 265787 - While trying to report a ktorrent bug, Drkonqi refuses to generate a report
Summary: While trying to report a ktorrent bug, Drkonqi refuses to generate a report
Status: RESOLVED DUPLICATE of bug 265493
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Dario Andres
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-08 12:18 UTC by George R. Goffe
Modified: 2011-02-08 17:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description George R. Goffe 2011-02-08 12:18:46 UTC
Version:           unspecified (using KDE 4.5.5) 
OS:                Linux

Drkonqi dialog after ktorrent-4.1beta1 crash invites the user to install debug symbols. As far as I can tell, this installation fails. A konsole appears and seems to be running a yum install of debuginfo packages but disappears without any indication of success or failure leaving the user in the dialog which states essentially "backtrace useless". Attempts to continue again prompts the user to install debugging symbols which again behaves as stated above... a loop as it were.

What is the use of Drkonqi without debugging information?

Reproducible: Always

Steps to Reproduce:
Wait for ktorrent-4.1beta1 to crash as it seems to do readily. Drconqi appears and behaves as stated in "Details" above

Actual Results:  
Nothing of any apparent usefulness.

Expected Results:  
Bug report relating to ktorrent-4.1beta1 crash.

Running ktorrent-4.1beta1 with "strace -o ktorrent.strace -xvf ktorrent" appears to bypass the crash but fills up the filesystem with the strace output file. "normal" ktorrent behavior is observed.
Comment 1 George Kiagiadakis 2011-02-08 17:33:14 UTC
Please do not report the same bug more than once. I already told you in the other report that this is a problem in a piece of code that was written by your distribution and you should file a bug to your distribution's bug tracker.

Just googling for "fedora bug tracker" shows as first result:
https://bugzilla.redhat.com/index.cgi

Please file your bug there. Or alternatively, consider using one of the mailing lists at http://fedoraproject.org/wiki/Communicate to ask for help.

Thanks.

*** This bug has been marked as a duplicate of bug 265493 ***