Application: systemsettings5 (5.2.2) Qt Version: 5.4.1 Operating System: Linux 3.19.0-28-generic x86_64 Distribution: Ubuntu 15.04 -- Information about the crash: - What I was doing when the application crashed: Wanted to temporarily turn off the desktop effects. Clicked around a bit in the Desktop Behavior, Workspace Theme and Display and Monitor but could not find how. Did not change anything. Closed System Settings using Esc when in the Display and Monitor view. That's when the Crash Reporting Assistant showed up. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0bcc541780 (LWP 10201))] Thread 2 (Thread 0x7f0bb9ac7700 (LWP 10202)): #0 0x00007f0bc8c6b8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f0bc6f61b72 in poll (__timeout=-1, __nfds=1, __fds=0x7f0bb9ac6d40) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x254c770, cond=cond@entry=0x254c7b0, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:447 #3 0x00007f0bc6f6364f in xcb_wait_for_event (c=0x254c770) at ../../src/xcb_in.c:622 #4 0x00007f0bbc8db099 in QXcbEventReader::run (this=0x255a9d0) at qxcbconnection.cpp:1105 #5 0x00007f0bc92f3b0e in QThreadPrivate::start (arg=0x255a9d0) at thread/qthread_unix.cpp:337 #6 0x00007f0bc5e5f6aa in start_thread (arg=0x7f0bb9ac7700) at pthread_create.c:333 #7 0x00007f0bc8c76eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f0bcc541780 (LWP 10201)): [KCrash Handler] #6 0x00007f0bc7d60d7e in QQuickItemPrivate::addToDirtyList() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x00007f0bc7d60e28 in QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x00007f0bc7d6b045 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x00007f0bc956373a in QObject::event (this=0x2fe3bd0, e=<optimized out>) at kernel/qobject.cpp:1245 #10 0x00007f0bc7d69b6b in QQuickItem::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x00007f0bca32bb2c in QApplicationPrivate::notify_helper (this=0x252c550, receiver=0x2fe3bd0, e=0x7f0ba41eaf10) at kernel/qapplication.cpp:3720 #12 0x00007f0bca331000 in QApplication::notify (this=0x7fff80b5dbb0, receiver=0x2fe3bd0, e=0x7f0ba41eaf10) at kernel/qapplication.cpp:3503 #13 0x00007f0bc9531c2b in QCoreApplication::notifyInternal (this=0x7fff80b5dbb0, receiver=0x2fe3bd0, event=event@entry=0x7f0ba41eaf10) at kernel/qcoreapplication.cpp:935 #14 0x00007f0bc9533c9b in sendEvent (event=0x7f0ba41eaf10, 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=0x252b770) at kernel/qcoreapplication.cpp:1552 #16 0x00007f0bc9534298 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1410 #17 0x00007f0bc958a843 in postEventSourceDispatch (s=0x25a5cd0) at kernel/qeventdispatcher_glib.cpp:271 #18 0x00007f0bc5939c3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x00007f0bc5939f20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x00007f0bc5939fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x00007f0bc958ac57 in QEventDispatcherGlib::processEvents (this=0x25b2000, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #22 0x00007f0bc952f3e2 in QEventLoop::exec (this=this@entry=0x7fff80b5da90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #23 0x00007f0bc953702c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188 #24 0x00007f0bc9d6331c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1510 #25 0x00007f0bca3277a5 in QApplication::exec () at kernel/qapplication.cpp:2956 #26 0x000000000040eebc in main (argc=1, argv=<optimized out>) at ../../app/main.cpp:54 Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 344651 ***