Bug 347483 - Crash of system settings (Systemeinstellungen) after graphics pane
Summary: Crash of system settings (Systemeinstellungen) after graphics pane
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-09 19:26 UTC by Christian Mayer
Modified: 2015-05-09 19:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Mayer 2015-05-09 19:26:47 UTC
Application: systemsettings5 (5.2.2)

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

-- Information about the crash:
- What I was doing when the application crashed:
I had the graphics pane open and switched away from it. The crash is even happening when I didn't change any setting...

- Unusual behavior I noticed:
I get slight artifacts on the screen during system interaction like moving the mouse cursor over a list where the current line gets highlighted. Or during some (menu) animation.
The artifact are shadows on the top part of the screen. 
When the animation is stoped no artifacts are remaining.

The crash can be reproduced every time.

-- Backtrace:
Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8b7832d780 (LWP 12454))]

Thread 2 (Thread 0x7f8b4248a700 (LWP 12883)):
#0  0x00007f8b74aaa49d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f8b6dc36f45 in ?? () from /usr/lib/nvidia-340/tls/libnvidia-tls.so.340.76
#2  0x00007f8b718072f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f8b717c396c in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f8b717c3e60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f8b717c4242 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f8b4d165ae6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#7  0x00007f8b717ea955 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x00007f8b71ce26aa in start_thread (arg=0x7f8b4248a700) at pthread_create.c:333
#9  0x00007f8b74ab9eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f8b7832d780 (LWP 12454)):
[KCrash Handler]
#6  0x00007f8b73bb7d6b in QQuickItemPrivate::addToDirtyList() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x00007f8b73bb7e28 in QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x00007f8b73bc2045 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x00007f8b7539f73a in QObject::event (this=0x24b2d20, e=<optimized out>) at kernel/qobject.cpp:1245
#10 0x00007f8b73bc0b6b in QQuickItem::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x00007f8b76159b2c in QApplicationPrivate::notify_helper (this=0x6cd430, receiver=0x24b2d20, e=0x7f8af8071590) at kernel/qapplication.cpp:3720
#12 0x00007f8b7615f000 in QApplication::notify (this=0x7ffe08dbafb0, receiver=0x24b2d20, e=0x7f8af8071590) at kernel/qapplication.cpp:3503
#13 0x00007f8b7536dc2b in QCoreApplication::notifyInternal (this=0x7ffe08dbafb0, receiver=0x24b2d20, event=event@entry=0x7f8af8071590) at kernel/qcoreapplication.cpp:935
#14 0x00007f8b7536fc9b in sendEvent (event=0x7f8af8071590, 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=0x6cc650) at kernel/qcoreapplication.cpp:1552
#16 0x00007f8b75370298 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1410
#17 0x00007f8b753c6843 in postEventSourceDispatch (s=0x735650) at kernel/qeventdispatcher_glib.cpp:271
#18 0x00007f8b717c3c3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f8b717c3f20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f8b717c3fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f8b753c6c57 in QEventDispatcherGlib::processEvents (this=0x742d40, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#22 0x00007f8b7536b3e2 in QEventLoop::exec (this=this@entry=0x7ffe08dbae90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#23 0x00007f8b7537302c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188
#24 0x00007f8b75b9431c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1510
#25 0x00007f8b761557a5 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
Comment 1 Christoph Feck 2015-05-09 19:53:37 UTC

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