Summary: | Discover Crashes when trying to upgrade a package | ||
---|---|---|---|
Product: | [Applications] Discover | Reporter: | Michael Tunnell <m> |
Component: | discover | Assignee: | Aleix Pol <aleixpol> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | nate, sitter |
Priority: | NOR | Keywords: | drkonqi, triaged |
Version: | 5.11.0 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Michael Tunnell
2017-12-28 17:59:06 UTC
I tried it again but this time I utilized more patience. I was clicking the Update All button prior to everything loading in Discover like plugins and such. This time I waited for all of it to load then I clicked the button and the upgrade worked just fine. I will report back the next time I have an upgrade for further testing but it seems like it is caused by clicking the button prior to everything of Discover being loaded. Unfortunately there's no debug info for the critical part of the backtrace: #6 0x00007fee6edd2fca in ?? () from /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so Since you can reproduce this every time, could you install Discover debug packages (sudo apt install plasma-discover-dbgsym plasma-discover-private-dbg plasma-discover-updater-dbgsym), reproduce the crash, and attach a new backtrace? If you can provide the information requested in comment #2, please add it. my Neon install says "E: Unable to locate package plasma-discover-private-dbg" Discover hadn't crashed since my last comment but it did just now though when trying to install the debug software, I received that error. Nate, if "plasma-discover-private-dbg" cannot be found, should Michael add specific debug repositories? Ah, that's probably because I'm using Neon dev unstable. Michael, you could temporarily add this repository: deb http://archive.neon.kde.org/dev/unstable xenial main ...then install the aforementioned debug package, then remove the repo again. (In reply to Nate Graham from comment #6) > Ah, that's probably because I'm using Neon dev unstable. Michael, you could > temporarily add this repository: > > deb http://archive.neon.kde.org/dev/unstable xenial main > > ...then install the aforementioned debug package, then remove the repo again. DO NOT DO THIS! That'd install the debug symbols of the unstable build, not the build that is crashing for Michael. So that makes no sense to begin with. Also, randomly mixing another edition repo is super dangerous as that basically breaks any and all binary compatibility expectation as well as package version order. Generally, all packages use -dbgsym suffix (only some sometimes have a -dbg compatibility version, which is purely there for compatibility reasons). So, what you want to install is plasma-discover-private-dbgsym. All that said, what you really should be doing is use the drkonqi's install packages button or run the helper manually. e.g. `/usr/bin/installdbgsymbols.sh /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so` Oops, sorry for the bad advice, and thanks for setting me right, Harald! That'll teach people to listen to my ramblings... Michael, can you try Harald's suggestions? Thanks! Michael, did comment #7 help to resolve the issue? 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 set the bug status 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! Dear Bug Submitter, 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! |