Summary: | Discover crashes prior to completing update process | ||
---|---|---|---|
Product: | [Applications] Discover | Reporter: | Frank Sandefur <fsandefur> |
Component: | discover | Assignee: | Aleix Pol <aleixpol> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | fsandefur |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.8.8 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Frank Sandefur
2018-01-03 23:26:05 UTC
Same happens to me with plasma-discover 5.8.8 in Kubuntu 16.04 64-bit. KDE Plasma version 5.8.8 KDE Frameworks version 5.36.0 Qt version 5.6.1 Kernel version 4.4.0-104-generic Every time, but the update procedure seems to complete even though the bars don't get to the end of the installing part. If I try sudo apt-get update && sudo apt-get upgrade it shows there's nothing to upgrade. Created attachment 109778 [details]
New crash information added by DrKonqi
plasma-discover (5.8.8) using Qt 5.6.1
- What I was doing when the application crashed: Attempted to let Discover do the updates, closed all other running software. Discover crashed before completion. Subsequently, I was unable to reboot my sytem using the plasma desktop menu. I had to use sudo reboot in the terminal.
-- Backtrace (Reduced):
#6 0x00007f66f191b428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7 0x00007f66f191d02a in __GI_abort () at abort.c:89
#8 0x00007f66f23cff41 in qt_message_fatal (context=..., message=<synthetic pointer>) at global/qlogging.cpp:1648
#9 QMessageLogger::fatal (this=this@entry=0x7ffc2385b570, msg=msg@entry=0x7f66f4c24322 "%s") at global/qlogging.cpp:790
#10 0x00007f66f4a91fe3 in QSGRenderLoop::handleContextCreationFailure (this=this@entry=0x1df0690, window=0x1ddb020, isEs=isEs@entry=false) at scenegraph/qsgrenderloop.cpp:262
*** This bug has been marked as a duplicate of bug 375913 *** Definitely NOT solved. THis bug has resulted - twice now - in an impartial update the rendered my system unbootable. A Discover crash cannot render the system unbootable, PackageKit will continue working on the background (check with pkcon and pkmon). Did you really compile it from sources? (In reply to Aleix Pol from comment #5) > A Discover crash cannot render the system unbootable, PackageKit will > continue working on the background (check with pkcon and pkmon). > > Did you really compile it from sources? My noting this as Compiled from Sources was an error on my part. I have installed everything from Either a dl'd DVD or repositories. I apologise for not noticing that until you asked. However, when the application crashed at a point the ongoing updates remain unfinished, leaves behind broken packages, and locks up my system before completing the boot up, I call that unbootable. I had to use grub to return to a previous configuration, drop to root, and use apt-get and dkpg to repair or complete the upgrades to be able to use my system. Frank, please read bug 375913 comment #2. If you get a different backtrace, I suggest to report it as a new bug. |