Application that crashed: systemsettings Version of the application: 1.0 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.3 Operating System: Linux 2.6.31-ARCH i686 What I was doing when the application crashed: not much to add... I'm using the kdemod version of kde4 from the chakra distribution -- Backtrace: Application: Systemeinstellungen (systemsettings), signal: Aborted [KCrash Handler] #6 0xb78df424 in __kernel_vsyscall () #7 0xb63c8411 in raise () from /lib/libc.so.6 #8 0xb63c9c12 in abort () from /lib/libc.so.6 #9 0xb640371d in __libc_message () from /lib/libc.so.6 #10 0xb6409581 in malloc_printerr () from /lib/libc.so.6 #11 0xb640ac82 in _int_free () from /lib/libc.so.6 #12 0xb640dd4d in free () from /lib/libc.so.6 #13 0xb66543c2 in QLocalePrivate::doubleToString () from /usr/lib/libQtCore.so.4 #14 0xb666dd1f in QString::setNum () from /usr/lib/libQtCore.so.4 #15 0xb666ddc6 in QString::number () from /usr/lib/libQtCore.so.4 #16 0xb6a04f69 in KLocale::formatNumber () from /usr/lib/libkdecore.so.5 #17 0xb347a8ee in KLocaleSample::slotLocaleChanged () from /usr/lib/kde4/kcm_locale.so #18 0xb347aee1 in KLocaleSample::qt_metacall () from /usr/lib/kde4/kcm_locale.so #19 0xb6727fcc in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #20 0xb6728c02 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #21 0xb347e617 in KLocaleConfigMoney::localeChanged () from /usr/lib/kde4/kcm_locale.so #22 0xb347f9dd in KLocaleConfigMoney::qt_metacall () from /usr/lib/kde4/kcm_locale.so #23 0xb6727fcc in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #24 0xb6728c02 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #25 0xb7018f83 in QLineEdit::textChanged () from /usr/lib/libQtGui.so.4 #26 0xb701e39c in ?? () from /usr/lib/libQtGui.so.4 #27 0xb701e0c1 in ?? () from /usr/lib/libQtGui.so.4 #28 0xb701f96b in QLineEdit::setText () from /usr/lib/libQtGui.so.4 #29 0xb347f79e in KLocaleConfigMoney::slotLocaleChanged () from /usr/lib/kde4/kcm_locale.so #30 0xb347f9b3 in KLocaleConfigMoney::qt_metacall () from /usr/lib/kde4/kcm_locale.so #31 0xb6727fcc in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #32 0xb6728c02 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #33 0xb34735d7 in KLocaleApplication::localeChanged () from /usr/lib/kde4/kcm_locale.so #34 0xb3473c06 in KLocaleApplication::load () from /usr/lib/kde4/kcm_locale.so #35 0xb770c416 in KCModule::qt_metacall () from /usr/lib/libkdeui.so.5 #36 0xb347481a in KLocaleApplication::qt_metacall () from /usr/lib/kde4/kcm_locale.so #37 0xb6720cbb in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4 #38 0xb67223be in QObject::event () from /usr/lib/libQtCore.so.4 #39 0xb6c64ac6 in QWidget::event () from /usr/lib/libQtGui.so.4 #40 0xb6c10924 in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #41 0xb6c17f5a in QApplication::notify () from /usr/lib/libQtGui.so.4 #42 0xb76530da in KApplication::notify () from /usr/lib/libkdeui.so.5 #43 0xb67125ab in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #44 0xb67131d2 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #45 0xb671339d in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4 #46 0xb673d0df in ?? () from /usr/lib/libQtCore.so.4 #47 0xb5bd9d98 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #48 0xb5bdd3e0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #49 0xb5bdd513 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #50 0xb673cd0c in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #51 0xb6cae705 in ?? () from /usr/lib/libQtGui.so.4 #52 0xb6710b99 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #53 0xb6710fea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #54 0xb671345f in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #55 0xb6c107a7 in QApplication::exec () from /usr/lib/libQtGui.so.4 #56 0x08052eee in _start () Reported using DrKonqi
I guess this could be related to some KLocale regressions on 4.3.2: bug 209712. Thanks
*** This bug has been marked as a duplicate of bug 209751 ***