Bug 402328 - Discover crashes on launch in AbstractResource::reportNewState() due to some Fwupd issue
Summary: Discover crashes on launch in AbstractResource::reportNewState() due to some ...
Status: RESOLVED FIXED
Alias: None
Product: Discover
Classification: Applications
Component: fwupd Backend (other bugs)
Version First Reported In: 5.14.4
Platform: Ubuntu Linux
: VHI crash
Target Milestone: ---
Assignee: Abhijeet Sharma
URL:
Keywords: drkonqi
: 402471 402523 403018 403022 403044 403066 403096 403110 403139 403158 403161 403181 403204 403245 403256 403261 403270 403290 403293 403341 403383 403392 403538 403577 403597 403651 403662 403738 403828 403858 403960 404066 404134 404421 404816 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-12-18 23:43 UTC by Gregory Smitherman
Modified: 2019-02-26 18:03 UTC (History)
43 users (show)

See Also:
Latest Commit: https://commits.kde.org/discover/baac08a40851699585e80b0a226c4fd683579a7b
Version Fixed In: 5.14.5.1, 5.15.1, 5.16.0
Sentry Crash Report:

Attachments
After installation of DbugSymb (40.30 KB, text/plain)
2019-01-09 15:12 UTC, Serge Moreau 		Details
plasma-discover 5.14.5 crashes on launch (after reinstalling it) (213.55 KB, text/plain)
2019-01-16 16:17 UTC, Andras 		Details
New crash information added by DrKonqi (17.11 KB, text/plain)
2019-01-17 19:42 UTC, joern477 		Details
New crash information added by DrKonqi (17.76 KB, text/plain)
2019-02-01 03:54 UTC, dbnaruto1 		Details
New crash information added by DrKonqi (21.28 KB, text/plain)
2019-02-10 02:07 UTC, Armando 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Gregory Smitherman 2018-12-18 23:43:59 UTC 
Application: plasma-discover (5.14.4)

Qt Version: 5.11.2
Frameworks Version: 5.54.0
Operating System: Linux 4.15.0-39-generic x86_64
Distribution: KDE neon Developer Edition

-- Information about the crash:
- What I was doing when the application crashed:

I simply opened Discover and it crashes immediately every time it's opened.

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0049220200 (LWP 30790))]

Thread 11 (Thread 0x7effeece7700 (LWP 30806)):
#0  0x00007f0044791bf9 in __GI___poll (fds=0x7effe00018a0, nfds=3, timeout=29809) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f003ecfc539 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f003ecfc64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f00450cc04b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f004507030a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f0044e9bbba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f0044ea6adb in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f0040e976db in start_thread (arg=0x7effeece7700) at pthread_create.c:463
#8  0x00007f004479e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7f0003498700 (LWP 30803)):
#0  0x00007f004478d0b4 in __GI___libc_read (fd=23, buf=0x7f0003497b90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x00007f003ed40cd0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f003ecfc027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f003ecfc4e0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f003ecfc64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f00450cc04b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f004507030a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f0044e9bbba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f0044ea6adb in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f0040e976db in start_thread (arg=0x7f0003498700) at pthread_create.c:463
#10 0x00007f004479e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7f0008a1f700 (LWP 30802)):
#0  0x00007f004479fa66 in __libc_recv (fd=7, buf=0x7efff8011898, len=8192, flags=0) at ../sysdeps/unix/sysv/linux/recv.c:28
#1  0x00007f0042bde9ec in  () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#2  0x00007f0042bcf155 in  () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#3  0x00007f0042bcf9a4 in QNetworkInterface::allInterfaces() () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#4  0x00007f000800b766 in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/bearer/libqgenericbearer.so
#5  0x00007f0045083125 in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f0045085098 in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f0042bbc4db in QNetworkConfigurationManagerPrivate::pollEngines() () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#8  0x00007f0042c40af5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#9  0x00007f00450a1075 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f00450ade47 in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007f00450ae1a8 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007f00450a1b9b in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007f0045071fd1 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f00450cb4be in QTimerInfoList::activateTimers() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f00450cbc81 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f003ecfc387 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007f003ecfc5c0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f003ecfc64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f00450cc02f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f004507030a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f0044e9bbba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f0044ea6adb in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007f0040e976db in start_thread (arg=0x7f0008a1f700) at pthread_create.c:463
#24 0x00007f004479e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7f0009ae8700 (LWP 30801)):
#0  0x00007f004478d0b4 in __GI___libc_read (fd=18, buf=0x7f0009ae7cd0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x00007f003ed40cd0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f003ecfc027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f003ecfc4e0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f003ecfc8d2 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f0010b91026 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6  0x00007f003ed24105 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007f0040e976db in start_thread (arg=0x7f0009ae8700) at pthread_create.c:463
#8  0x00007f004479e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7f000a2e9700 (LWP 30800)):
#0  0x00007f0044791bf9 in __GI___poll (fds=0x564d76705b20, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f003ecfc539 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f003ecfc64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f003ecfc691 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f003ed24105 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f0040e976db in start_thread (arg=0x7f000a2e9700) at pthread_create.c:463
#6  0x00007f004479e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f00188bc700 (LWP 30799)):
#0  0x00007f004478d0b4 in __GI___libc_read (fd=15, buf=0x7f00188bbb20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x00007f003ed40cd0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f003ecfc027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f003ecfc4e0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f003ecfc64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f00450cc04b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f004507030a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f0044e9bbba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f00484ab826 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x00007f0044ea6adb in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f0040e976db in start_thread (arg=0x7f00188bc700) at pthread_create.c:463
#11 0x00007f004479e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f0019d98700 (LWP 30798)):
#0  0x00007f0040e9d9f3 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x564d75f6f558) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x00007f0040e9d9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x564d75f6f508, cond=0x564d75f6f530) at pthread_cond_wait.c:502
#2  0x00007f0040e9d9f3 in __pthread_cond_wait (cond=0x564d75f6f530, mutex=0x564d75f6f508) at pthread_cond_wait.c:655
#3  0x00007f001ea1d46b in  () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
#4  0x00007f001ea1d197 in  () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
#5  0x00007f0040e976db in start_thread (arg=0x7f0019d98700) at pthread_create.c:463
#6  0x00007f004479e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f002ce79700 (LWP 30795)):
#0  0x00007f0044791bf9 in __GI___poll (fds=0x7f0020004a00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f003ecfc539 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f003ecfc64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f00450cc04b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f004507030a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f0044e9bbba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f0045a434f5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x00007f0044ea6adb in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f0040e976db in start_thread (arg=0x7f002ce79700) at pthread_create.c:463
#9  0x00007f004479e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f002e08a700 (LWP 30793)):
#0  0x00007f004478d0b4 in __GI___libc_read (fd=7, buf=0x7f002e089b60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x00007f003ed40cd0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f003ecfc027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f003ecfc4e0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f003ecfc64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f00450cc04b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f004507030a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f0044e9bbba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f0046d9de45 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x00007f0044ea6adb in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f0040e976db in start_thread (arg=0x7f002e08a700) at pthread_create.c:463
#11 0x00007f004479e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f00367bb700 (LWP 30791)):
#0  0x00007f0044791bf9 in __GI___poll (fds=0x7f00367baca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f003e431747 in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f003e43336a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f003977bed9 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007f0044ea6adb in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f0040e976db in start_thread (arg=0x7f00367bb700) at pthread_create.c:463
#6  0x00007f004479e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f0049220200 (LWP 30790)):
[KCrash Handler]
#6  0x00007f0048144d62 in AbstractResource::reportNewState() () at /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so
#7  0x00007f00450a118f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f001108bcb5 in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/fwupd-backend.so
#9  0x00007f001108c4e7 in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/fwupd-backend.so
#10 0x00007f001108cdc1 in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/fwupd-backend.so
#11 0x00007f00450a118f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007f0044ea4223 in QFutureWatcherBase::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007f004668de1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007f00466953ef in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007f0045071fe8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f0045074b2d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f00450cc9f3 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f003ecfc387 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f003ecfc5c0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f003ecfc64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f00450cc02f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f0039807761 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#23 0x00007f004507030a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00007f00450794d0 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x0000564d7583a868 in  ()
#26 0x00007f004469eb97 in __libc_start_main (main=0x564d75839f90, argc=1, argv=0x7fff8059bd58, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff8059bd48) at ../csu/libc-start.c:310
#27 0x0000564d7583aaea in _start ()

Reported using DrKonqi
Comment 1 KDErobo3me 2018-12-19 01:24:00 UTC 
I always said, Discover is a basket case. Users run from it like hostages.
Comment 2 Nate Graham 2018-12-27 03:09:24 UTC 
(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
Comment 3 Nate Graham 2018-12-27 04:17:59 UTC 
*** Bug 402471 has been marked as a duplicate of this bug. ***
Comment 4 Aleix Pol 2019-01-09 15:03:00 UTC 
*** Bug 403018 has been marked as a duplicate of this bug. ***
Comment 5 Aleix Pol 2019-01-09 15:04:36 UTC 
I cannot reproduce, if somebody could provide a backtrace with debug symbols, that would be helpful.
Comment 6 Serge Moreau 2019-01-09 15:12:35 UTC 
Created attachment 117358 [details]
After installation of DbugSymb
Comment 7 Aleix Pol 2019-01-09 19:28:19 UTC 
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?
Comment 8 Serge Moreau 2019-01-09 19:51:28 UTC 
I am not used with these kinds of procedure.
I installed Plasma-discover-debug.
Tell me what I must do.
Sorry
SM
Comment 9 Serge Moreau 2019-01-10 13:12:49 UTC 
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
Comment 10 Serge Moreau 2019-01-11 15:46:44 UTC 
But after a short time in use Discover crashed again
Sorry
Comment 11 Aleix Pol 2019-01-14 17:51:47 UTC 
*** Bug 403204 has been marked as a duplicate of this bug. ***
Comment 12 Aleix Pol 2019-01-14 17:52:13 UTC 
*** Bug 403110 has been marked as a duplicate of this bug. ***
Comment 13 Aleix Pol 2019-01-14 17:52:31 UTC 
*** Bug 403139 has been marked as a duplicate of this bug. ***
Comment 14 Aleix Pol 2019-01-14 17:53:11 UTC 
*** Bug 403181 has been marked as a duplicate of this bug. ***
Comment 15 Aleix Pol 2019-01-14 17:53:27 UTC 
*** Bug 403161 has been marked as a duplicate of this bug. ***
Comment 16 Aleix Pol 2019-01-14 17:53:36 UTC 
*** Bug 403158 has been marked as a duplicate of this bug. ***
Comment 17 Aleix Pol 2019-01-14 17:53:51 UTC 
*** Bug 403096 has been marked as a duplicate of this bug. ***
Comment 18 Aleix Pol 2019-01-14 17:54:00 UTC 
*** Bug 403066 has been marked as a duplicate of this bug. ***
Comment 19 Aleix Pol 2019-01-14 17:54:10 UTC 
*** Bug 403044 has been marked as a duplicate of this bug. ***
Comment 20 Aleix Pol 2019-01-14 18:18:06 UTC 
*** Bug 403022 has been marked as a duplicate of this bug. ***
Comment 21 lnxusr 2019-01-14 19:27:07 UTC 
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?
Comment 22 Wade Fogarty 2019-01-15 02:01:50 UTC 
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)
Comment 23 Nate Graham 2019-01-15 02:20:59 UTC 
Yes. :(
Comment 24 Nate Graham 2019-01-15 19:49:12 UTC 
*** Bug 402523 has been marked as a duplicate of this bug. ***
Comment 25 Nate Graham 2019-01-15 19:54:39 UTC 
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
Comment 26 Nate Graham 2019-01-15 23:01:21 UTC 
*** Bug 403245 has been marked as a duplicate of this bug. ***
Comment 27 Yancy Burns 2019-01-15 23:11:27 UTC 
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.
Comment 28 Andras 2019-01-16 16:17:13 UTC 
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
Comment 29 Nate Graham 2019-01-17 02:56:28 UTC 
*** Bug 403270 has been marked as a duplicate of this bug. ***
Comment 30 Nate Graham 2019-01-17 02:58:16 UTC 
*** Bug 403261 has been marked as a duplicate of this bug. ***
Comment 31 Nate Graham 2019-01-17 02:58:33 UTC 
*** Bug 403256 has been marked as a duplicate of this bug. ***
Comment 32 Christoph Feck 2019-01-17 07:17:50 UTC 
*** Bug 403290 has been marked as a duplicate of this bug. ***
Comment 33 Christoph Feck 2019-01-17 07:18:00 UTC 
*** Bug 403293 has been marked as a duplicate of this bug. ***
Comment 34 joern477 2019-01-17 19:42:07 UTC 
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
Comment 35 Serge Moreau 2019-01-18 08:50:59 UTC 
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
Comment 36 Nate Graham 2019-01-18 21:45:00 UTC 
*** Bug 403341 has been marked as a duplicate of this bug. ***
Comment 37 Nate Graham 2019-01-20 02:25:14 UTC 
*** Bug 403392 has been marked as a duplicate of this bug. ***
Comment 38 Nate Graham 2019-01-20 02:26:37 UTC 
*** Bug 403383 has been marked as a duplicate of this bug. ***
Comment 39 Aleix Pol 2019-01-31 15:26:35 UTC 
*** Bug 403651 has been marked as a duplicate of this bug. ***
Comment 40 Aleix Pol 2019-01-31 15:26:40 UTC 
*** Bug 403738 has been marked as a duplicate of this bug. ***
Comment 41 Aleix Pol 2019-01-31 15:27:36 UTC 
*** Bug 403538 has been marked as a duplicate of this bug. ***
Comment 42 Aleix Pol 2019-01-31 15:28:27 UTC 
*** Bug 403577 has been marked as a duplicate of this bug. ***
Comment 43 Aleix Pol 2019-01-31 15:28:37 UTC 
*** Bug 403597 has been marked as a duplicate of this bug. ***
Comment 44 dbnaruto1 2019-02-01 03:54:14 UTC 
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
Comment 45 dbnaruto1 2019-02-01 04:02:24 UTC 
(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.
Comment 46 lurulf 2019-02-04 10:12:25 UTC 
(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.
Comment 47 Nate Graham 2019-02-05 19:55:44 UTC 
*** Bug 403960 has been marked as a duplicate of this bug. ***
Comment 48 Nate Graham 2019-02-05 21:13:59 UTC 
*** Bug 403858 has been marked as a duplicate of this bug. ***
Comment 49 Nate Graham 2019-02-05 21:23:39 UTC 
*** Bug 403828 has been marked as a duplicate of this bug. ***
Comment 50 Nate Graham 2019-02-05 22:26:01 UTC 
*** Bug 403662 has been marked as a duplicate of this bug. ***
Comment 51 Nate Graham 2019-02-08 18:23:00 UTC 
*** Bug 404066 has been marked as a duplicate of this bug. ***
Comment 52 Armando 2019-02-10 02:07:46 UTC 
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
Comment 53 Don S. 2019-02-10 06:34:26 UTC 
(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.
Comment 54 Nate Graham 2019-02-11 20:12:21 UTC 
*** Bug 404134 has been marked as a duplicate of this bug. ***
Comment 55 Dan Leinir Turthra Jensen 2019-02-12 11:01:12 UTC 
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.
Comment 56 Nate Graham 2019-02-12 16:38:12 UTC 
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...
Comment 57 Nate Graham 2019-02-12 17:53:42 UTC 
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
Comment 58 Nate Graham 2019-02-18 22:11:15 UTC 
*** Bug 404421 has been marked as a duplicate of this bug. ***
Comment 59 Nate Graham 2019-02-26 16:53:17 UTC 
We got another report of this in 5.15.0 via Bug 404816. :(
Comment 60 Nate Graham 2019-02-26 16:53:52 UTC 
*** Bug 404816 has been marked as a duplicate of this bug. ***
Comment 61 Antonio Rojas 2019-02-26 16:59:37 UTC 
(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
Comment 62 Nate Graham 2019-02-26 18:03:12 UTC 
Urgh, you're right, it's in 5.15.1. Derp.