Bug 346604 - Attempting to opening kcm Workspace Themes crashes System Settings
Summary: Attempting to opening kcm Workspace Themes crashes System Settings
Status: RESOLVED DUPLICATE of bug 346519
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-04-24 23:28 UTC by William C. Mitchell
Modified: 2015-04-25 09:11 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 William C. Mitchell 2015-04-24 23:28:33 UTC
Application: systemsettings5 (5.2.2)

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

-- Information about the crash:
- What I was doing when the application crashed: Google Chrome was open on desktop; I had also just changed the Colors module to Wonton Soup, but had closed and reopened System Settings in the interim.

- Custom settings of the application: see above - Colors module had been changes to Wonton Soup.

- This crash repeated three consectutive times.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fceeb750780 (LWP 32182))]

Thread 3 (Thread 0x7fced8f80700 (LWP 32183)):
#0  0x00007fcee7eb88dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fcee61d2b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007fcee61d464f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007fcedbd13099 in QXcbEventReader::run (this=0x2167a50) at qxcbconnection.cpp:1105
#4  0x00007fcee8539b0e in QThreadPrivate::start (arg=0x2167a50) at thread/qthread_unix.cpp:337
#5  0x00007fcee50ec6aa in start_thread (arg=0x7fced8f80700) at pthread_create.c:333
#6  0x00007fcee7ec3eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fceca42a700 (LWP 32184)):
#0  0x00007fcee7eb88dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fcee4bcdebc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fcee4bcdfcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fcee87d0c6c in QEventDispatcherGlib::processEvents (this=0x7fcec40008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#4  0x00007fcee87753e2 in QEventLoop::exec (this=this@entry=0x7fceca429e20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x00007fcee8534b44 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:503
#6  0x00007fcee74fff65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x00007fcee8539b0e in QThreadPrivate::start (arg=0x25dab90) at thread/qthread_unix.cpp:337
#8  0x00007fcee50ec6aa in start_thread (arg=0x7fceca42a700) at pthread_create.c:333
#9  0x00007fcee7ec3eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fceeb750780 (LWP 32182)):
[KCrash Handler]
#6  0x00007fcee7df2267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#7  0x00007fcee7df3eca in __GI_abort () at abort.c:89
#8  0x00007fcee8526edf in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1415
#9  QMessageLogger::fatal (this=0x7ffd87583880, msg=<optimized out>) at global/qlogging.cpp:636
#10 0x00007fcee6fa7791 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x00007fcee6fb106f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x00007fcee6fb130a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#13 0x00007fcee8faf7b5 in QWindow::event (this=0x25e8a20, ev=<optimized out>) at kernel/qwindow.cpp:2051
#14 0x00007fcee6fe2dd3 in QQuickWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#15 0x00007fcee9563b2c in QApplicationPrivate::notify_helper (this=0x213a550, receiver=0x25e8a20, e=0x7ffd87583d00) at kernel/qapplication.cpp:3720
#16 0x00007fcee9569000 in QApplication::notify (this=0x7ffd87584100, receiver=0x25e8a20, e=0x7ffd87583d00) at kernel/qapplication.cpp:3503
#17 0x00007fcee8777c2b in QCoreApplication::notifyInternal (this=0x7ffd87584100, receiver=receiver@entry=0x25e8a20, event=event@entry=0x7ffd87583d00) at kernel/qcoreapplication.cpp:935
#18 0x00007fcee8fa7e86 in sendSpontaneousEvent (event=0x7ffd87583d00, receiver=0x25e8a20) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#19 QGuiApplicationPrivate::processExposeEvent (e=0x24d3390) at kernel/qguiapplication.cpp:2613
#20 0x00007fcee8fa8bbd in QGuiApplicationPrivate::processWindowSystemEvent (e=e@entry=0x24d3390) at kernel/qguiapplication.cpp:1638
#21 0x00007fcee8f8d34f in QWindowSystemInterface::sendWindowSystemEvents (flags=...) at kernel/qwindowsysteminterface.cpp:572
#22 0x00007fcedbd3d590 in userEventSourceDispatch (source=<optimized out>) at eventdispatchers/qeventdispatcher_glib.cpp:70
#23 0x00007fcee4bcdc3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007fcee4bcdf20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007fcee4bcdfcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007fcee87d0c57 in QEventDispatcherGlib::processEvents (this=0x21af190, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#27 0x00007fcee87753e2 in QEventLoop::exec (this=this@entry=0x7ffd87583fe0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#28 0x00007fcee877d02c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188
#29 0x00007fcee8f9e31c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1510
#30 0x00007fcee955f7a5 in QApplication::exec () at kernel/qapplication.cpp:2956
#31 0x000000000040eebc in main (argc=1, argv=<optimized out>) at ../../app/main.cpp:54

Reported using DrKonqi
Comment 1 Christoph Feck 2015-04-25 09:11:48 UTC

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