Bug 347730

Summary: System Settings crash when click "Overview" button
Product: [I don't know] kde Reporter: Xu Zhao <nuklly>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash Keywords: drkonqi
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Xu Zhao 2015-05-14 19:20:01 UTC
Application: systemsettings5 (5.3.0)

Qt Version: 5.4.1
Operating System: Linux 3.16.7-21-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
I installed kscreen5.
Click "Display and Monitor" enter the page, then click "Overview".

Should back to Overview.
Buggy symptom: the whole system settings crashed.

Version: KDE 5.9
openSUSE 13.2

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1de04b4780 (LWP 5333))]

Thread 3 (Thread 0x7f1dcc369700 (LWP 5334)):
#0  0x00007f1ddc30fc3d in poll () at /lib64/libc.so.6
#1  0x00007f1dd9e20322 in  () at /usr/lib64/libxcb.so.1
#2  0x00007f1dd9e21def in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x00007f1dcf13abd9 in  () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#4  0x00007f1ddc9897cf in  () at /usr/lib64/libQt5Core.so.5
#5  0x00007f1dd869d0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x00007f1ddc31806d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f1dbc574700 (LWP 5336)):
#0  0x00007f1ddc30fc3d in poll () at /lib64/libc.so.6
#1  0x00007f1dd8181be4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f1dd8181cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f1ddcbbb14b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007f1ddcb61d5b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x00007f1ddc984baa in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x00007f1ddb7803f8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x00007f1ddc9897cf in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007f1dd869d0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x00007f1ddc31806d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f1de04b4780 (LWP 5333)):
[KCrash Handler]
#5  0x00007f1ddb078880 in QQuickWindow::maybeUpdate() () at /usr/lib64/libQt5Quick.so.5
#6  0x00007f1ddb065a78 in QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) () at /usr/lib64/libQt5Quick.so.5
#7  0x00007f1ddb06f585 in  () at /usr/lib64/libQt5Quick.so.5
#8  0x00007f1ddcb94456 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#9  0x00007f1ddb06dff3 in QQuickItem::event(QEvent*) () at /usr/lib64/libQt5Quick.so.5
#10 0x00007f1dddf83b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#11 0x00007f1dddf88a26 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#12 0x00007f1ddcb63df5 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#13 0x00007f1ddcb65c8f in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#14 0x00007f1ddcbbbcb3 in  () at /usr/lib64/libQt5Core.so.5
#15 0x00007f1dd8181a04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#16 0x00007f1dd8181c48 in  () at /usr/lib64/libglib-2.0.so.0
#17 0x00007f1dd8181cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#18 0x00007f1ddcbbb12c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#19 0x00007f1ddcb61d5b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#20 0x00007f1ddcb693c6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#21 0x00000000004101bf in main ()

Reported using DrKonqi
Comment 1 Christoph Feck 2015-05-16 17:05:25 UTC

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