Application: systemsettings5 (5.2.1) Qt Version: 5.4.0 Operating System: Linux 3.18.0-13-generic x86_64 Distribution: Ubuntu Vivid Vervet (development branch) -- Information about the crash: - What I was doing when the application crashed: Changed from one section to another, the application asked if I wanted to first save my changes, I accepted and then it crashed. -- Backtrace: Application: Ustawienia systemowe (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f28734f37c0 (LWP 2614))] Thread 2 (Thread 0x7f286229e700 (LWP 2615)): #0 0x00007f286fc520fd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f286e9a0b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x00007f286e9a264f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x00007f286505e0b9 in QXcbEventReader::run (this=0x22e7840) at qxcbconnection.cpp:1105 #4 0x00007f28702d9a4e in QThreadPrivate::start (arg=0x22e7840) at thread/qthread_unix.cpp:337 #5 0x00007f286d8b80a5 in start_thread (arg=0x7f286229e700) at pthread_create.c:309 #6 0x00007f286fc5c5ad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f28734f37c0 (LWP 2614)): [KCrash Handler] #6 0x00007f2852dbeb7b in QQuickItemPrivate::addToDirtyList() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x00007f2852dbec38 in QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x00007f2852dc8e75 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x00007f28705496ca in QObject::event (this=0x27c42a0, e=<optimized out>) at kernel/qobject.cpp:1245 #10 0x00007f2852dc799b in QQuickItem::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x00007f28713082ec in QApplicationPrivate::notify_helper (this=0x22b9f90, receiver=0x27c42a0, e=0x7f2820444b60) at kernel/qapplication.cpp:3722 #12 0x00007f287130d960 in QApplication::notify (this=0x7fffc7270b90, receiver=0x27c42a0, e=0x7f2820444b60) at kernel/qapplication.cpp:3505 #13 0x00007f2870517bdb in QCoreApplication::notifyInternal (this=0x7fffc7270b90, receiver=0x27c42a0, event=event@entry=0x7f2820444b60) at kernel/qcoreapplication.cpp:932 #14 0x00007f2870519c4b in sendEvent (event=0x7f2820444b60, 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=0x22b96c0) at kernel/qcoreapplication.cpp:1536 #16 0x00007f287051a248 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1394 #17 0x00007f28705706a3 in postEventSourceDispatch (s=0x2326d40) at kernel/qeventdispatcher_glib.cpp:271 #18 0x00007f286d398c3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x00007f286d398f20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x00007f286d398fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x00007f2870570ab7 in QEventDispatcherGlib::processEvents (this=0x2337320, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #22 0x00007f2870515392 in QEventLoop::exec (this=this@entry=0x7fffc7270a70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #23 0x00007f287051cfdc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1185 #24 0x00007f2870d4419c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1535 #25 0x00007f2871303f55 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
If this is reproducible, could you mention which systemsettings pages you visited? It could be related to the KWin decoration page.
I just reproduced it: - opened system settings - click on display and monitor (not sure of the correct names, using polish language) - click the " < " symbol in top left to go back to settings - crash
Still crashing on 5.2.2
*** This bug has been marked as a duplicate of bug 344651 ***