Bug 371722 - Let crash handler install debug packages
Summary: Let crash handler install debug packages
Status: RESOLVED WORKSFORME
Alias: None
Product: neon
Classification: KDE Neon
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-26 19:07 UTC by Pascal d'Hermilly
Modified: 2022-12-10 05:13 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
We are almost there screenshot - but I'm not getting the prompt for password. (45.65 KB, image/png)
2017-05-09 08:41 UTC, Pascal d'Hermilly
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal d'Hermilly 2016-10-26 19:07:37 UTC
It's overcomplicated to find and install debug packages.
In Kubuntu the crash-handler offered to install debug-packages to improve the crash-information (perhaps only in kde4).
Can't we have such a button in KDE Neon? Especially because the crashes are so valuable to due to recent code.
Currently I can click 'List of files' that look like a link. It will give me lots of .so files and then it's up to me the daft user to find the right packages one by one and install it through CLI.
Comment 1 rockonthemoonfm 2016-12-31 05:59:50 UTC
yes, actually I don't even know how to get a backtrace in User edition 5.8.5
Comment 2 Pascal d'Hermilly 2017-02-16 08:59:45 UTC
It's a huge waste of testers that debug packages are not suggested and that the crash handler says 'Your report is not useful so you can't report'.
Comment 3 Pascal d'Hermilly 2017-04-27 19:06:08 UTC
Using crash-happy Kdenlive - it's quite frustrating that my many crash reports are denied by crash handler because there are no debug packages.
Comment 4 Pascal d'Hermilly 2017-04-27 19:06:52 UTC
Especially since KDE Neon is supposed to give this quick feedback loop to the developers.
Comment 5 Pascal d'Hermilly 2017-05-09 08:41:39 UTC
Created attachment 105412 [details]
We are almost there screenshot - but I'm not getting the prompt for password.

Now after a plasma crash I was able to click somehing like "get debug packages", but unfortunately it looks like it's searching forever or the password prompt just never happens.
Super nice to see progress though :D
Comment 6 Harald Sitter 2017-05-09 09:26:54 UTC
Nope it's installing after you've authenticated.
Comment 7 Pascal d'Hermilly 2017-05-09 09:39:28 UTC
(In reply to Harald Sitter from comment #6)
> Nope it's installing after you've authenticated.

But it didn't ask me to authenticate - even check for hidden windows in the taskbar.

Eventually I clicked cancel and drkonqi crashed and also wanted to install debug packages for it. From there it could have been an endless loop, it seems ;-)
Comment 8 Harald Sitter 2017-05-09 11:49:54 UTC
Oh, sorry, I didn't read your comment properly. Nevermind then :S
Comment 9 Harald Sitter 2017-05-09 12:52:14 UTC
if you could run the installer manually on a terminal and paste the output here that'd be very handy

drkonqi-pk-debug-installer /usr/bin/plasmashell
Comment 10 Pascal d'Hermilly 2017-05-09 20:35:21 UTC
(In reply to Harald Sitter from comment #9)
> if you could run the installer manually on a terminal and paste the output
> here that'd be very handy
> 
> drkonqi-pk-debug-installer /usr/bin/plasmashell

It seems to work flawlessly. It asks me for a password.
I've not filled it because I want to see it work for when I actually have a crash. 


output in case you can still use it:
 drkonqi-pk-debug-installer /usr/bin/plasmashell
PackageKit::Transaction(0xf42b80)
FileResolver(0xf45450) found "plasma-workspace;4:5.9.5.1-0neon+16.04+build75;amd64;installed:neon-xenial-main"
candidates ("plasma-workspace-dbgsym", "plasma-workspace-dbg")
DebugResolver(0xf463e0) dbgfound "plasma-workspace-dbg;4:5.5.5.2-0ubuntu1;i386;ubuntu-xenial-universe" ()
DebugResolver(0xf463e0) 1
DebugResolver(0xf463e0) dbgfound "plasma-workspace-dbg;4:5.9.5.1-0neon+16.04+build75;amd64;neon-xenial-main" ("plasma-workspace-dbg;4:5.5.5.2-0ubuntu1;i386;ubuntu-xenial-universe")
DebugResolver(0xf463e0) 2
FileResolver(0xf45450) ++ packages for "plasma-workspace;4:5.9.5.1-0neon+16.04+build75;amd64;installed:neon-xenial-main" ("plasma-workspace-dbg;4:5.9.5.1-0neon+16.04+build75;amd64;neon-xenial-main")
"plasma-workspace;4:5.9.5.1-0neon+16.04+build75;amd64;installed:neon-xenial-main" ("plasma-workspace-dbg;4:5.9.5.1-0neon+16.04+build75;amd64;neon-xenial-main") QSet(FileResolver(0xf45450)) FileResolver(0xf45450)
DO INSTALL QSet("plasma-workspace-dbg;4:5.9.5.1-0neon+16.04+build75;amd64;neon-xenial-main")
2
Comment 11 Harald Sitter 2017-05-09 20:46:47 UTC
Yeah, if it should not work on an actual crash copy your ~/.cache/xsession-errors file. It should technically have similar output to the one you posted which should help in debugging why it didn't work.
Comment 12 Justin Zobel 2022-11-10 22:32:28 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 13 Bug Janitor Service 2022-11-25 05:16:28 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 14 Bug Janitor Service 2022-12-10 05:13:44 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!