Bug 320367 - Either stop asking for crash information or fix it
Summary: Either stop asking for crash information or fix it
Status: RESOLVED DUPLICATE of bug 319043
Alias: None
Product: drkonqi
Classification: Applications
Component: backtraceparsing (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: George Kiagiadakis
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-27 20:48 UTC by bkorb
Modified: 2019-07-02 14:03 UTC (History)
1 user (show)

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


Attachments
The "Hi, KDE has messed up" window (104.57 KB, image/x-xcf)
2013-05-27 20:53 UTC, bkorb
Details
The inadequate back trace (679.92 KB, image/x-xcf)
2013-05-27 20:54 UTC, bkorb
Details
The "your help is unhelpful" message (133.55 KB, image/x-xcf)
2013-05-27 20:55 UTC, bkorb
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bkorb 2013-05-27 20:48:31 UTC
I've installed the debug symbols, but your crash collection tool doesn't think I have.

Reproducible: Always

Steps to Reproduce:
1. Get KDE to crash somehow
2. try to report the problem
3.
Actual Results:  
It says, "your information does not have any value for us"

Expected Results:  
the bug report would be filed

JPG images coming shortly
Comment 1 bkorb 2013-05-27 20:53:41 UTC
Created attachment 80108 [details]
The "Hi, KDE has messed up" window
Comment 2 bkorb 2013-05-27 20:54:30 UTC
Created attachment 80109 [details]
The inadequate back trace
Comment 3 bkorb 2013-05-27 20:55:37 UTC
Created attachment 80110 [details]
The "your help is unhelpful" message
Comment 4 Christoph Feck 2013-06-13 21:37:12 UTC
Could you add the full backtrace (as a text, not image) here? From what can be seen, indeed most debug symbols are missing. If you are using openSUSE, could you also add the output of "rpm -qa | grep debug"?
Comment 5 bkorb 2013-06-14 00:37:59 UTC
(In reply to comment #4)
> Could you add the full backtrace (as a text, not image) here?

Only if I happen to trigger another crash.  Were it readily reproducible, I'd have filed a bug report against the component that crashed, instead of the crash gathering tool.  I am guessing you also know that I am not allowed to text-capture the back trace.  Perhaps I could if the backtrace display tool were able to allow the clipboard to do its thing?  Dunno.  In any event, ksnapshot was the only way I could get it at all.

> From what can
> be seen, indeed most debug symbols are missing. If you are using openSUSE,
> could you also add the output of "rpm -qa | grep debug"?

> $ rpm -qa |grep -i debug
> libnettle-debugsource-2.5-2.1.1.x86_64
> liblcms1-debuginfo-1.19-11.1.1.x86_64
> texlive-lua-visual-debug-2012.60.0.0.4svn25881-4.2.1.noarch
> nettle-debuginfo-2.5-2.1.1.x86_64
> liblcms2-2-debuginfo-2.4-2.1.1.x86_64
> bind-debuginfo-9.9.2P2-2.3.1.x86_64
> digikam-debuginfo-3.2.0-1.25.8.x86_64

If this doesn't include the debug info for the plasma desk top (it doesn't look like it to me), then what happened?  I told the crash capture tool to tell YaST to install the needed debug symbols, so if they are not there, then there's a snafu somewhere in the drkonqi->YaST->download-debug-symbols process.  I _did_ tell it to get the debug symbols.  That was followed by, "can't find them", per the last attachment.
Comment 6 Christoph Feck 2013-06-28 11:25:43 UTC
> Perhaps I could if the backtrace display tool were able to allow the clipboard to do its thing?

There are tool buttons below the backtrace to Copy it to clipboard or Save it to a file. Then you can manually add it to a bug report.

The button to install missing debug symbols has been added for distributions to implement this feature. If it does not work, please report it to the bug tracker of your distribution.
Comment 7 Andrew Crouthamel 2018-11-10 03:21:10 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-11-20 04:08:08 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Harald Sitter 2019-07-02 14:03:00 UTC

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