Bug 348192 - Using KDE5 settings manager
Summary: Using KDE5 settings manager
Status: RESOLVED DUPLICATE of bug 344651
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-05-25 03:15 UTC by Seth Izenzon
Modified: 2015-05-31 13:56 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 Seth Izenzon 2015-05-25 03:15:37 UTC
Application: systemsettings5 (5.3.0)

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

-- Information about the crash:
- What I was doing when the application crashed:
Using KDE settings manager. Specifically in the Desktop Animation settings. This has happened more than once in various parts of the settings manager.
- Unusual behavior I noticed:
None
- Custom settings of the application:
None

The crash can be reproduced every time.

-- 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 0x7fc0692ca780 (LWP 22800))]

Thread 4 (Thread 0x7fc0568ef700 (LWP 22801)):
#0  0x00007fc065a038dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fc063cf9b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007fc063cfb64f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007fc05970b099 in QXcbEventReader::run (this=0x215be60) at qxcbconnection.cpp:1105
#4  0x00007fc06608bb0e in QThreadPrivate::start (arg=0x215be60) at thread/qthread_unix.cpp:337
#5  0x00007fc062bf76aa in start_thread (arg=0x7fc0568ef700) at pthread_create.c:333
#6  0x00007fc065a0eeed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fc03c89f700 (LWP 22818)):
#0  0x00007fc0626d0dd0 in g_main_context_acquire () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fc0626d1d75 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fc0626d1fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fc066322c6c in QEventDispatcherGlib::processEvents (this=0x7fc02c103250, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#4  0x00007fc0662c73e2 in QEventLoop::exec (this=this@entry=0x7fc03c89ee40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x00007fc066086b44 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:503
#6  0x00007fc06608bb0e in QThreadPrivate::start (arg=0x28f1b70) at thread/qthread_unix.cpp:337
#7  0x00007fc062bf76aa in start_thread (arg=0x7fc03c89f700) at pthread_create.c:333
#8  0x00007fc065a0eeed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fc045017700 (LWP 22832)):
#0  0x00007fc065a038dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fc0626d1ebc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fc0626d2242 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fc031927ae6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007fc0626f8955 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fc062bf76aa in start_thread (arg=0x7fc045017700) at pthread_create.c:333
#6  0x00007fc065a0eeed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fc0692ca780 (LWP 22800)):
[KCrash Handler]
#6  0x00007fc064af8d89 in QQuickItemPrivate::addToDirtyList() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x00007fc064af8e28 in QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x00007fc064b03045 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x00007fc0662fb73a in QObject::event (this=0x371c3b0, e=<optimized out>) at kernel/qobject.cpp:1245
#10 0x00007fc064b01b6b in QQuickItem::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x00007fc0670c3b2c in QApplicationPrivate::notify_helper (this=0x212e930, receiver=0x371c3b0, e=0x7fc04005bfc0) at kernel/qapplication.cpp:3720
#12 0x00007fc0670c9000 in QApplication::notify (this=0x7ffcb0aa45b0, receiver=0x371c3b0, e=0x7fc04005bfc0) at kernel/qapplication.cpp:3503
#13 0x00007fc0662c9c2b in QCoreApplication::notifyInternal (this=0x7ffcb0aa45b0, receiver=0x371c3b0, event=event@entry=0x7fc04005bfc0) at kernel/qcoreapplication.cpp:935
#14 0x00007fc0662cbc9b in sendEvent (event=0x7fc04005bfc0, 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=0x212db50) at kernel/qcoreapplication.cpp:1552
#16 0x00007fc0662cc298 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1410
#17 0x00007fc066322843 in postEventSourceDispatch (s=0x219cd80) at kernel/qeventdispatcher_glib.cpp:271
#18 0x00007fc0626d1c3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fc0626d1f20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fc0626d1fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fc066322c57 in QEventDispatcherGlib::processEvents (this=0x2199450, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#22 0x00007fc0662c73e2 in QEventLoop::exec (this=this@entry=0x7ffcb0aa4490, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#23 0x00007fc0662cf02c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188
#24 0x00007fc066afb31c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1510
#25 0x00007fc0670bf7a5 in QApplication::exec () at kernel/qapplication.cpp:2956
#26 0x000000000040ef5b in main (argc=1, argv=<optimized out>) at ../../app/main.cpp:55

Reported using DrKonqi
Comment 1 Christoph Feck 2015-05-31 13:56:51 UTC

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