Bug 427782 - failed to install debug symbols
Summary: failed to install debug symbols
Status: RESOLVED DUPLICATE of bug 400386
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages User Edition (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-15 22:40 UTC by u.an.i
Modified: 2020-11-17 11:15 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
crash reporting assistant step in question (136.10 KB, image/png)
2020-10-15 22:40 UTC, u.an.i
Details
crash reporting assistant: fetching debug symbols failed (200.63 KB, image/png)
2020-10-16 15:22 UTC, u.an.i
Details

Note You need to log in before you can comment on or make changes to this bug.
Description u.an.i 2020-10-15 22:40:21 UTC
Created attachment 132399 [details]
crash reporting assistant step in question

in Crash Reporting Assistant I am asked "Please select which additional information you can provide:"; I selected "What I was doing when the application 'Dolphin' crashed" but I am not offered any opportunity to enter this information as text.

Secondly, for that Dolphin crash, CRA was not able to install debug symbols.

I am no Linux developer nor Linux expert and knowing which, even knowing of apt itself, debug package (name!) I would have to apt-get is beyond the capabilities of most users targeted by nice UI such as of your KDE neon and even if they knew, they might expect things to work and can not be bothered to wade through further multiple steps.

People thinking they can help and spending time with CRA should be encouraged and supported. Currently ending the wizard with "... does not contain enough information to be helpful" is not comforting.
Comment 1 Nate Graham 2020-10-16 13:50:21 UTC
One issue per bug report please. :)

You're given the opportunity to add additional information in a text field on the next page of the wizard.

So let's use this bug report to track the issue installing debug symbols. Can you clarify how it failed? What did it say?
Comment 2 u.an.i 2020-10-16 15:22:19 UTC
(I just managed to repro the other bug I reported wrt Dolphin)

Inside the CRA (not inside the initial dialogue offering to report a bug which opens the CRA where there is a tab with a trace and the opportunity to install debug symbols too)

Clicking button "Install Debug Symbols"

First: "Requesting debug symbols for this application"

Then: "Could not find debug symbol packages for this application" (see attachment nds.PNG)
Comment 3 u.an.i 2020-10-16 15:22:55 UTC
Created attachment 132430 [details]
crash reporting assistant: fetching debug symbols failed
Comment 4 u.an.i 2020-10-16 15:26:31 UTC
(btw.: in the whole CRA after ticking the checkbox "What I was doing ..." I don't see a textbox of some sort. As I can currently repro the crash I could take a screen recording and report this as a separate bug if you like)
Comment 5 Nate Graham 2020-10-16 15:59:30 UTC
Moving back to Neon then, to see why the debug symbols couldn't be installed from DrKonqi.

And yes, if you could file another bug to track the UX improvement idea of moving the "what I was doing" textbox into an earlier page, that would be nice.
Comment 6 Harald Sitter 2020-10-16 16:05:53 UTC
There is no input on the checkbox because it was expressly lamented in the past that people wrote down their life story, went to the next page to install debug symbols only to find that for whatever reason the trace couldn't produce sufficient quality and drkonqi refused to let them continue. So they had written all the text for naught.

The other way around was also lamented because if we put the tracing first the user would be prompted to install 500mib of debug symbols and then on the next page get asked about context they can provide and if the trace isn't 100% quality and the textual context isn't grand either drkonqi would also not let the bug get reported on account of being poor quality with all things considered. So possibly even twice the annoyance due to wasted effort.
Comment 7 Nate Graham 2020-10-16 16:09:10 UTC
Heh, thanks for that context. That makes a lot of sense.
Comment 8 Patrick Silva 2020-11-17 11:15:14 UTC

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