Summary: | Discover crashes on launch in AbstractResource::reportNewState() due to some Fwupd issue | ||
---|---|---|---|
Product: | [Applications] Discover | Reporter: | Gregory Smitherman <greg.smitherman> |
Component: | fwupd Backend | Assignee: | Abhijeet Sharma <sharma.abhijeet2096> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | admin, andrasszerencses1, armandogarciasf, arojas, basuda.mensajes1, bbrannock, beowuff, berndmj, bob.groeneveld, broot0999, dbnaruto1, diplarosm, don, esqhumberto, etienne, frodekolgrov, icuxeva, jesaenh, jesper_huijgens, joern477, kde.erik, kde, kde, kenxshiba, ktodorov, lnxusr, marius.ux, matheus.novais734, maxvanceffer, me, mroberto71, murakami.marco, natale, nate, ozolinsemils, przem.formela, pujos.michael, ringofvoid, robert.skubij, smoreau17, strzol, thomas.jouas, virtualspectre8 |
Priority: | VHI | Keywords: | drkonqi |
Version: | 5.14.4 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=404816 | ||
Latest Commit: | https://commits.kde.org/discover/baac08a40851699585e80b0a226c4fd683579a7b | Version Fixed In: | 5.14.5.1, 5.15.1, 5.16.0 |
Attachments: |
After installation of DbugSymb
plasma-discover 5.14.5 crashes on launch (after reinstalling it) New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
Description
Gregory Smitherman
2018-12-18 23:43:59 UTC
I always said, Discover is a basket case. Users run from it like hostages. (In reply to KDErobo3me from comment #1) > I always said, Discover is a basket case. Users run from it like hostages. My mother always said "If you don't have something nice to say, don't say anything at all." https://community.kde.org/Get_Involved/Bug_Reporting#Remember_your_manners *** Bug 402471 has been marked as a duplicate of this bug. *** *** Bug 403018 has been marked as a duplicate of this bug. *** I cannot reproduce, if somebody could provide a backtrace with debug symbols, that would be helpful. Created attachment 117358 [details]
After installation of DbugSymb
Hey, I'm sorry but that's not showing the debug symbols for the fwupd backend which is what we're after. Which package did you install? I am not used with these kinds of procedure. I installed Plasma-discover-debug. Tell me what I must do. Sorry SM If it helps, I made a clean install of Neon 5.14.5 on a separate partition of the same machine, and in this case Discover does not crash. SM But after a short time in use Discover crashed again Sorry *** Bug 403204 has been marked as a duplicate of this bug. *** *** Bug 403110 has been marked as a duplicate of this bug. *** *** Bug 403139 has been marked as a duplicate of this bug. *** *** Bug 403181 has been marked as a duplicate of this bug. *** *** Bug 403161 has been marked as a duplicate of this bug. *** *** Bug 403158 has been marked as a duplicate of this bug. *** *** Bug 403096 has been marked as a duplicate of this bug. *** *** Bug 403066 has been marked as a duplicate of this bug. *** *** Bug 403044 has been marked as a duplicate of this bug. *** *** Bug 403022 has been marked as a duplicate of this bug. *** Importance: NOR crash? I really hope NOR doesn't stand for normal, because the update system of a DE crashing is anything but normal. As can be attested by the numerous duplicate reports, this isn't an isolated incident. Perhaps an upgrade to the importance and status, again, due to the numerous reports, is in order to facilitate a quicker fix? So if Discover crashing every time is normal for Plasma 5.14.5, do we need to wait for 5.15 for a working version of Discover? (I already submitted a crash report with debug symbols btw) Yes. :( *** Bug 402523 has been marked as a duplicate of this bug. *** Seems fwupd-related. From https://bugs.kde.org/show_bug.cgi?id=402523#c5: (In reply to Yancy Burns from comment #5) > (In reply to ktodorov from comment #1) > > after removing fwupd-backend.so from > > /usr/lib/x86_64-linux-gnu/qt5/plugins/discover Discover can be started > > without crash > > I also moved the file fwupd-backend.so from the same path and Discover then > started fine. Next, I shutdown Discover, moved the file back, and Discover > then started up again fine. More complete backtrace showing symbols in fwupd: -- Backtrace (Reduced): #6 0x00007f367d811d62 in AbstractResource::reportNewState (this=0x55afa61c0940) at ./libdiscover/resources/AbstractResource.cpp:143 #7 0x00007f367a77018f in QtPrivate::QSlotObjectBase::call (a=0x7ffcbb5444a0, r=0x55afa61c0940, this=0x55afa47bc700) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:376 [...] #10 0x00007f367d822cf3 in AbstractResource::stateChanged (this=this@entry=0x55afa61c0940) at ./obj-x86_64-linux-gnu/libdiscover/DiscoverCommon_autogen/3YJK5W5UP7/moc_AbstractResource.cpp:430 #11 0x00007f363edeca2d in FwupdResource::setState (this=this@entry=0x55afa61c0940, state=state@entry=AbstractResource::Upgradeable) at ./libdiscover/backends/FwupdBackend/FwupdResource.cpp:141 #12 0x00007f363edf1cb5 in FwupdBackend::createApp (this=this@entry=0x55afa49081a0, device=device@entry=0x7f3630004590) at ./libdiscover/backends/FwupdBackend/FwupdBackend.cpp:235 *** Bug 403245 has been marked as a duplicate of this bug. *** On a different computer with the same issue, I just manually ran "fwupd get-updates" and "fwupd update" to update the bios. I then ran Discover again on that box and it started up fine. Created attachment 117491 [details] plasma-discover 5.14.5 crashes on launch (after reinstalling it) My system plasma-discover 5.14.5 Qt Version: 5.11.2 KDE Frameworks Version: 5.54.0 Kernel Version: 4.15.0-43-generic Distribution: KDE neon User Edition 5.14 Previously it worked however I reinstalled Discover trying to resolve this bug: https://bugs.kde.org/show_bug.cgi?id=399981. It's probably fwupd related indeed because Discover starts after: fwupdmgr refresh fwupdmgr update *** Bug 403270 has been marked as a duplicate of this bug. *** *** Bug 403261 has been marked as a duplicate of this bug. *** *** Bug 403256 has been marked as a duplicate of this bug. *** *** Bug 403290 has been marked as a duplicate of this bug. *** *** Bug 403293 has been marked as a duplicate of this bug. *** Created attachment 117518 [details]
New crash information added by DrKonqi
plasma-discover (5.14.5) using Qt 5.11.2
- What I was doing when the application crashed:
I started Discover and it directly crashes after it was started.
-- Backtrace (Reduced):
#6 0x00007fbfed872d62 in AbstractResource::reportNewState (this=0x556de51671d0) at ./libdiscover/resources/AbstractResource.cpp:143
#7 0x00007fbfea7cf18f in QtPrivate::QSlotObjectBase::call (a=0x7ffd81af6c70, r=0x556de51671d0, this=0x7fbf98003630) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:376
[...]
#10 0x00007fbfed883cf3 in AbstractResource::stateChanged (this=this@entry=0x556de51671d0) at ./obj-x86_64-linux-gnu/libdiscover/DiscoverCommon_autogen/3YJK5W5UP7/moc_AbstractResource.cpp:430
#11 0x00007fbfad59ca2d in FwupdResource::setState (this=this@entry=0x556de51671d0, state=state@entry=AbstractResource::Upgradeable) at ./libdiscover/backends/FwupdBackend/FwupdResource.cpp:141
#12 0x00007fbfad5a1cb5 in FwupdBackend::createApp (this=this@entry=0x556de5a09a50, device=device@entry=0x7fbf98002de0) at ./libdiscover/backends/FwupdBackend/FwupdBackend.cpp:235
I tried the plasma-discover version from /dev/stable archives (5.14.5+p18.04+git 20190117.1427-0 on my neon/user installation, and Discover no more crashes. Instaled by temporarily activating the /dev/stable repository and then back to /user repository SM *** Bug 403341 has been marked as a duplicate of this bug. *** *** Bug 403392 has been marked as a duplicate of this bug. *** *** Bug 403383 has been marked as a duplicate of this bug. *** *** Bug 403651 has been marked as a duplicate of this bug. *** *** Bug 403738 has been marked as a duplicate of this bug. *** *** Bug 403538 has been marked as a duplicate of this bug. *** *** Bug 403577 has been marked as a duplicate of this bug. *** *** Bug 403597 has been marked as a duplicate of this bug. *** Created attachment 117765 [details]
New crash information added by DrKonqi
plasma-discover (5.14.5) using Qt 5.11.2
- What I was doing when the application crashed:
KDE crashes shortly after first run, with update buttons greyed-out. After first crash, the application will just instantly crash.
-- Backtrace (Reduced):
#6 0x00007f9c8c06fd62 in AbstractResource::reportNewState (this=0x5628ab81ee20) at ./libdiscover/resources/AbstractResource.cpp:143
#7 0x00007f9c88fcc18f in QtPrivate::QSlotObjectBase::call (a=0x7ffec28bb990, r=0x5628ab81ee20, this=0x7f9c48014ac0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:376
[...]
#10 0x00007f9c8c080cf3 in AbstractResource::stateChanged (this=this@entry=0x5628ab81ee20) at ./obj-x86_64-linux-gnu/libdiscover/DiscoverCommon_autogen/3YJK5W5UP7/moc_AbstractResource.cpp:430
#11 0x00007f9c427d0a2d in FwupdResource::setState (this=this@entry=0x5628ab81ee20, state=state@entry=AbstractResource::Upgradeable) at ./libdiscover/backends/FwupdBackend/FwupdResource.cpp:141
#12 0x00007f9c427d5cb5 in FwupdBackend::createApp (this=this@entry=0x5628a9ea5380, device=device@entry=0x7f9c480045d0) at ./libdiscover/backends/FwupdBackend/FwupdBackend.cpp:235
(In reply to Andras from comment #28) > Created attachment 117491 [details] > plasma-discover 5.14.5 crashes on launch (after reinstalling it) > > My system > plasma-discover 5.14.5 > Qt Version: 5.11.2 > KDE Frameworks Version: 5.54.0 > Kernel Version: 4.15.0-43-generic > Distribution: KDE neon User Edition 5.14 > > Previously it worked however I reinstalled Discover trying to resolve this > bug: https://bugs.kde.org/show_bug.cgi?id=399981. > It's probably fwupd related indeed because Discover starts after: > fwupdmgr refresh > fwupdmgr update I can confirm that I am now able to start Discover, without any crash by running fwupdmgr refresh && fwupdmgr update. There was an update applied to my Logitech Unifying Receiver (not sure if that matters). Now everything works. (In reply to Andras from comment #28) > Created attachment 117491 [details] > plasma-discover 5.14.5 crashes on launch (after reinstalling it) > > My system > plasma-discover 5.14.5 > Qt Version: 5.11.2 > KDE Frameworks Version: 5.54.0 > Kernel Version: 4.15.0-43-generic > Distribution: KDE neon User Edition 5.14 > > Previously it worked however I reinstalled Discover trying to resolve this > bug: https://bugs.kde.org/show_bug.cgi?id=399981. > It's probably fwupd related indeed because Discover starts after: > fwupdmgr refresh > fwupdmgr update Yes, I can confirm the same. An available update for Logitech Unifying Receiver in Fwupd seems to crash Discover. After fwupdmgr refresh && fwupdmgr update, Discover does not crash. *** Bug 403960 has been marked as a duplicate of this bug. *** *** Bug 403858 has been marked as a duplicate of this bug. *** *** Bug 403828 has been marked as a duplicate of this bug. *** *** Bug 403662 has been marked as a duplicate of this bug. *** *** Bug 404066 has been marked as a duplicate of this bug. *** Created attachment 117959 [details]
New crash information added by DrKonqi
plasma-discover (5.14.5) using Qt 5.12.0
- What I was doing when the application crashed:
Started up KDE Neon, proceeded to open Discover through menu. Crash. Attempted opening via terminal. Crash. Crashes consistently every single time.
As another user reported in a comment, I was able to avoid a crash by removing the file fwupd-backend.so. Replacing the file to the /usr/lib/x86_64-linux-gnu/qt5/plugins/discover directory reproduced consistent crashes at every effort to open Discover.
As some others have expressed in comments, after running fwupdmgr refresh && fwupdmgr update, Discover does not crash.
-- Backtrace (Reduced):
#6 0x00007fadc73b1d62 in AbstractResource::reportNewState (this=0x564d4e978170) at ./libdiscover/resources/AbstractResource.cpp:143
#7 0x00007fadc41faf3f in QtPrivate::QSlotObjectBase::call (a=0x7ffeb8717940, r=0x564d4e978170, this=0x564d4e978990) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
[...]
#10 0x00007fadc73c2cf3 in AbstractResource::stateChanged (this=this@entry=0x564d4e978170) at ./obj-x86_64-linux-gnu/libdiscover/DiscoverCommon_autogen/3YJK5W5UP7/moc_AbstractResource.cpp:430
#11 0x00007fad7d5a1a2d in FwupdResource::setState (this=this@entry=0x564d4e978170, state=state@entry=AbstractResource::Upgradeable) at ./libdiscover/backends/FwupdBackend/FwupdResource.cpp:141
#12 0x00007fad7d5a6cb5 in FwupdBackend::createApp (this=this@entry=0x564d4d09f430, device=device@entry=0x7fad74002d90) at ./libdiscover/backends/FwupdBackend/FwupdBackend.cpp:235
(In reply to lurulf from comment #46) > (In reply to Andras from comment #28) > > Created attachment 117491 [details] > > plasma-discover 5.14.5 crashes on launch (after reinstalling it) > > > > My system > > plasma-discover 5.14.5 > > Qt Version: 5.11.2 > > KDE Frameworks Version: 5.54.0 > > Kernel Version: 4.15.0-43-generic > > Distribution: KDE neon User Edition 5.14 > > > > Previously it worked however I reinstalled Discover trying to resolve this > > bug: https://bugs.kde.org/show_bug.cgi?id=399981. > > It's probably fwupd related indeed because Discover starts after: > > fwupdmgr refresh > > fwupdmgr update > > Yes, I can confirm the same. An available update for Logitech Unifying > Receiver in Fwupd seems to crash Discover. After fwupdmgr refresh && > fwupdmgr update, Discover does not crash. Same here. Same bug fixed same way with update to the Logitech Unifying Receiver. *** Bug 404134 has been marked as a duplicate of this bug. *** Thank you everybody for all the backtraces! I've just pushed a patch which we're hoping will fix the issue, but as none of us have been able to reproduce it at our end, it'd be super helpful if someone out there who does have the issue would be able to give it a test for us by compiling Discover out of the master branch and see whether the issue persists. Fixed with https://cgit.kde.org/discover.git/commit/?id=8c673e79ab452254051d158c885b9b4bf127392e So far this is 5.16 only, but we're going to look into backporting it to 5.15 and potentially even 5.14 too. Stay tuned... Git commit baac08a40851699585e80b0a226c4fd683579a7b by Nate Graham, on behalf of Dan Leinir Turthra Jensen. Committed on 12/02/2019 at 17:53. Pushed by ngraham into branch 'Plasma/5.14'. Set parent on newly created fwupd resource Without this patch, the resource lacks a parent backend, which causes issues when attempting to signal changes in it later on (as AbstractResource depends on there being a backend set) Differential Revision: https://phabricator.kde.org/D18946 M +1 -1 libdiscover/backends/FwupdBackend/FwupdBackend.cpp M +1 -1 libdiscover/backends/FwupdBackend/FwupdBackend.h https://commits.kde.org/discover/baac08a40851699585e80b0a226c4fd683579a7b *** Bug 404421 has been marked as a duplicate of this bug. *** We got another report of this in 5.15.0 via Bug 404816. :( *** Bug 404816 has been marked as a duplicate of this bug. *** (In reply to Nate Graham from comment #59) > We got another report of this in 5.15.0 via Bug 404816. :( 5.15.0 does not have the fix Urgh, you're right, it's in 5.15.1. Derp. |