Bug 350462 - systemsettings crash after returning from Display KCM
Summary: systemsettings crash after returning from Display KCM
Status: RESOLVED DUPLICATE of bug 344651
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-07-21 18:58 UTC by Sergiu Bivol
Modified: 2015-07-28 11:42 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sergiu Bivol 2015-07-21 18:58:07 UTC
Application: systemsettings5 (5.3.1)

Qt Version: 5.4.1
Operating System: Linux 3.19.0-23-generic x86_64
Distribution: Ubuntu 15.04

-- Information about the crash:
- What I was doing when the application crashed:
I have opened System Settings -> Displays and Screens, then returned to System Settings. System Settings always crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Configurări de sistem (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fad83de6780 (LWP 28015))]

Thread 3 (Thread 0x7fad744df700 (LWP 28016)):
#0  0x00007fad8054c8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fad7e866b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007fad7e86864f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007fad77272099 in QXcbEventReader::run (this=0x10f1910) at qxcbconnection.cpp:1105
#4  0x00007fad80bcdb0e in QThreadPrivate::start (arg=0x10f1910) at thread/qthread_unix.cpp:337
#5  0x00007fad7d7806aa in start_thread (arg=0x7fad744df700) at pthread_create.c:333
#6  0x00007fad80557eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fad61bc8700 (LWP 28019)):
#0  0x00007fad7d2a67a4 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fad7d2613f0 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fad7d261de8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fad7d261fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fad80e64c6c in QEventDispatcherGlib::processEvents (this=0x7fad540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#5  0x00007fad80e093e2 in QEventLoop::exec (this=this@entry=0x7fad61bc7e40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x00007fad80bc8b44 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:503
#7  0x00007fad80bcdb0e in QThreadPrivate::start (arg=0x18effe0) at thread/qthread_unix.cpp:337
#8  0x00007fad7d7806aa in start_thread (arg=0x7fad61bc8700) at pthread_create.c:333
#9  0x00007fad80557eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fad83de6780 (LWP 28015)):
[KCrash Handler]
#6  0x00007fad7f655d7e in QQuickItemPrivate::addToDirtyList() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x00007fad7f655e28 in QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x00007fad7f660045 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x00007fad80e3d73a in QObject::event (this=0x1a79fa0, e=<optimized out>) at kernel/qobject.cpp:1245
#10 0x00007fad7f65eb6b in QQuickItem::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x00007fad81bf7b2c in QApplicationPrivate::notify_helper (this=0x10d8e70, receiver=0x1a79fa0, e=0x7fad480605a0) at kernel/qapplication.cpp:3720
#12 0x00007fad81bfd000 in QApplication::notify (this=0x7ffd8fbc1860, receiver=0x1a79fa0, e=0x7fad480605a0) at kernel/qapplication.cpp:3503
#13 0x00007fad80e0bc2b in QCoreApplication::notifyInternal (this=0x7ffd8fbc1860, receiver=0x1a79fa0, event=event@entry=0x7fad480605a0) at kernel/qcoreapplication.cpp:935
#14 0x00007fad80e0dc9b in sendEvent (event=0x7fad480605a0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:228
#15 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x10d80c0) at kernel/qcoreapplication.cpp:1552
#16 0x00007fad80e0e298 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1410
#17 0x00007fad80e64843 in postEventSourceDispatch (s=0x11184e0) at kernel/qeventdispatcher_glib.cpp:271
#18 0x00007fad7d261c3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fad7d261f20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fad7d261fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fad80e64c57 in QEventDispatcherGlib::processEvents (this=0x1117990, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#22 0x00007fad80e093e2 in QEventLoop::exec (this=this@entry=0x7ffd8fbc1740, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#23 0x00007fad80e1102c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188
#24 0x00007fad8163231c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1510
#25 0x00007fad81bf37a5 in QApplication::exec () at kernel/qapplication.cpp:2956
#26 0x000000000040ef6b in main (argc=1, argv=<optimized out>) at ../../app/main.cpp:55

Reported using DrKonqi
Comment 1 Christoph Feck 2015-07-28 11:42:54 UTC

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