Bug 184901

Summary:	system settings crash after changing keyboard layouts
Product:	[Applications] systemsettings	Reporter:	David Kay <magneus>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra, magneus
Priority:	NOR
Version:	4.2.0
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description David Kay 2009-02-19 08:49:53 UTC

Version:            (using KDE 4.2.0)
Compiler:          gcc version 4.1.2 (Gentoo 4.1.2 p1.0.2)
 CFLAGS="-march=nocona -O2 -pipe" 
OS:                Linux
Installed from:    Compiled From Sources

Only crashed system-settings. No other applications affected.

Unsure of exact cause of crash. 

Change time settings then added a keyboard layout (US-Dvorak), configured toggle hotkey (both shifts).

Crash occurred suddenly when closing system-settings.

Logfile:

Application: System Settings (systemsettings), signal SIGSEGV
0x00007f4e89c3f491 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 11399)]

Thread 2 (Thread 0x7f4e7b45e950 (LWP 11446)):
#0  0x00007f4e89c664a2 in select () from /lib/libc.so.6
#1  0x00007f4e8b675ca8 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#2  0x00007f4e8b5d1712 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#3  0x00007f4e8b363097 in start_thread () from /lib/libpthread.so.0
#4  0x00007f4e89c6c77d in clone () from /lib/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f4e8d41b760 (LWP 11399)):
[KCrash Handler]
#5  0x00007f4e8a851db6 in QWidgetPrivate::reparentFocusWidgets () from /usr/lib64/qt4/libQtGui.so.4
#6  0x00007f4e8a8620aa in QWidget::setParent () from /usr/lib64/qt4/libQtGui.so.4
#7  0x00007f4e8a862855 in QWidgetPrivate::init () from /usr/lib64/qt4/libQtGui.so.4
#8  0x00007f4e8a862e58 in QWidget::QWidget () from /usr/lib64/qt4/libQtGui.so.4
#9  0x00007f4e7d8246a2 in ?? () from /usr/kde/4.2/lib64/kde4/kcm_screensaver.so
#10 0x00007f4e7d81756d in ?? () from /usr/kde/4.2/lib64/kde4/kcm_screensaver.so
#11 0x00007f4e7d81a491 in ?? () from /usr/kde/4.2/lib64/kde4/kcm_screensaver.so
#12 0x00007f4e8b69f4dc in QMetaObject::activate () from /usr/lib64/qt4/libQtCore.so.4
#13 0x00007f4e7d5d68f5 in K3Process::processExited () from /usr/kde/4.2/lib64/libkde3support.so.4
#14 0x00007f4e7d5d6b8a in K3Process::wait () from /usr/kde/4.2/lib64/libkde3support.so.4
#15 0x00007f4e7d818fde in ?? () from /usr/kde/4.2/lib64/kde4/kcm_screensaver.so
#16 0x00007f4e8d015b24 in KCModuleProxy::deleteClient () from /usr/kde/4.2/lib64/libkutils.so.4
#17 0x00007f4e8d016216 in KCModuleProxy::~KCModuleProxy () from /usr/kde/4.2/lib64/libkutils.so.4
#18 0x00007f4e8b69c9e0 in QObjectPrivate::deleteChildren () from /usr/lib64/qt4/libQtCore.so.4
#19 0x00007f4e8a85a4ef in QWidget::~QWidget () from /usr/lib64/qt4/libQtGui.so.4
#20 0x00007f4e8b69c9e0 in QObjectPrivate::deleteChildren () from /usr/lib64/qt4/libQtCore.so.4
#21 0x00007f4e8a859f2f in QWidget::~QWidget () from /usr/lib64/qt4/libQtGui.so.4
#22 0x00007f4e8abf0ecf in QScrollArea::~QScrollArea () from /usr/lib64/qt4/libQtGui.so.4
#23 0x00007f4e8b69c9e0 in QObjectPrivate::deleteChildren () from /usr/lib64/qt4/libQtCore.so.4
#24 0x00007f4e8a859f2f in QWidget::~QWidget () from /usr/lib64/qt4/libQtGui.so.4
#25 0x00007f4e8c256469 in ?? () from /usr/kde/4.2/lib64/libkdeui.so.5
#26 0x00007f4e8b69c9e0 in QObjectPrivate::deleteChildren () from /usr/lib64/qt4/libQtCore.so.4
#27 0x00007f4e8a859f2f in QWidget::~QWidget () from /usr/lib64/qt4/libQtGui.so.4
#28 0x00007f4e8c258db1 in KPageWidget::~KPageWidget () from /usr/kde/4.2/lib64/libkdeui.so.5
#29 0x00007f4e8b69c9e0 in QObjectPrivate::deleteChildren () from /usr/lib64/qt4/libQtCore.so.4
#30 0x00007f4e8a859f2f in QWidget::~QWidget () from /usr/lib64/qt4/libQtGui.so.4
#31 0x000000000040f389 in _start ()

Comment 1 Dario Andres 2009-02-19 23:30:51 UTC

The crash is related to the ScreenSaver module ... I assume you used the Desktop/Screensaver module in the same SystemSettings session that crashed
The fix is in KDE4.2.1 and 4.3

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