Bug 394461 - Updater crashes when loaded
Summary: Updater crashes when loaded
Status: RESOLVED DUPLICATE of bug 390066
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.12.90
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2018-05-20 07:04 UTC by Jurgen
Modified: 2018-05-28 16:36 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jurgen 2018-05-20 07:04:30 UTC
Application: plasma-discover (5.12.90)

Qt Version: 5.10.0
Frameworks Version: 5.47.0
Operating System: Linux 4.13.0-41-generic x86_64
Distribution: KDE neon Developer Edition

-- Information about the crash:
This happens every time - even after a fresh reboot.
I have gone to the Konsole and did an apt upgrade and dist-upgrade. All upgrades are done.
Can't launch the upgrader/software  centre.

The crash can be reproduced every time.

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

Thread 3 (Thread 0x7f2ed3439700 (LWP 3669)):
#0  0x00007f2eec376568 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x00007f2eec5ab9d1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x00007f2ee6328dc1 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f2ee6329330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f2ee632949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f2eec5ab5cb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f2eec55264a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f2eec372554 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f2eecf4da35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x00007f2eec3776eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f2ee84216ba in start_thread (arg=0x7f2ed3439700) at pthread_create.c:333
#11 0x00007f2eeb97b41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f2ed464a700 (LWP 3668)):
#0  0x00007f2eeb96f74d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007f2ee632938c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f2ee632949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f2eec5ab5cb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f2eec55264a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f2eec372554 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f2eee2732c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007f2eec3776eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f2ee84216ba in start_thread (arg=0x7f2ed464a700) at pthread_create.c:333
#9  0x00007f2eeb97b41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f2ef065d8c0 (LWP 3666)):
[KCrash Handler]
#6  DiscoverObject::modes (this=this@entry=0x23a6640) at /workspace/build/discover/DiscoverObject.cpp:152
#7  0x0000000000416a3a in DiscoverObject::openMode (this=this@entry=0x23a6640, _mode=...) at /workspace/build/discover/DiscoverObject.cpp:164
#8  0x0000000000414784 in processArgs (parser=0x23281d0, mainWindow=mainWindow@entry=0x23a6640) at /workspace/build/discover/main.cpp:72
#9  0x0000000000412c4c in main (argc=3, argv=<optimized out>) at /workspace/build/discover/main.cpp:138

Possible duplicates by query: bug 390066.

Reported using DrKonqi
Comment 1 Aleix Pol 2018-05-28 16:36:21 UTC

*** This bug has been marked as a duplicate of bug 390066 ***