Bug 271055 - Crashing while running 'Locale'
Summary: Crashing while running 'Locale'
Status: RESOLVED DUPLICATE of bug 262488
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_language (show other bugs)
Version: 1.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: John Layt
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-15 21:21 UTC by DEZDEchado
Modified: 2011-04-16 02:55 UTC (History)
1 user (show)

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 DEZDEchado 2011-04-15 21:21:37 UTC
Application: systemsettings (1.0)
KDE Platform Version: 4.6.2 (4.6.2)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-7-generic x86_64
Distribution: Ubuntu Natty (development branch)

-- Information about the crash:
- What I was doing when the application crashed:
Running  'System Settings'->'Locale'
Craching occures every time.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f637e866780 (LWP 24440))]

Thread 2 (Thread 0x7f6363390700 (LWP 24443)):
#0  0x00007f637bd87f03 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f6379b04104 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f6379b04639 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f637c4cf446 in QEventDispatcherGlib::processEvents (this=0x13eeb30, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007f637c4a3882 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f637c4a3abc in QEventLoop::exec (this=0x7f636338fdd0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007f637c3ba924 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:492
#7  0x00007f637c485c2f in QInotifyFileSystemWatcherEngine::run (this=0x13ee1c0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f637c3bd175 in QThreadPrivate::start (arg=0x13ee1c0) at thread/qthread_unix.cpp:320
#9  0x00007f6379fcfd8c in start_thread (arg=0x7f6363390700) at pthread_create.c:304
#10 0x00007f637bd9504d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f637e866780 (LWP 24440)):
[KCrash Handler]
#6  ref (this=<value optimized out>, dayPeriod=<value optimized out>) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121
#7  QString (this=<value optimized out>, dayPeriod=<value optimized out>) at /usr/include/qt4/QtCore/qstring.h:729
#8  KCMLocale::dayPeriodText (this=<value optimized out>, dayPeriod=<value optimized out>) at ../../../kcontrol/locale/kcmlocale.cpp:2452
#9  0x00007f636297698a in KCMLocale::initAmPmSymbols (this=0x15247c0) at ../../../kcontrol/locale/kcmlocale.cpp:2513
#10 0x00007f6362979cc1 in KCMLocale::initSettingsWidgets (this=0x15247c0) at ../../../kcontrol/locale/kcmlocale.cpp:674
#11 0x00007f636297ab2d in KCMLocale::load (this=0x15247c0) at ../../../kcontrol/locale/kcmlocale.cpp:425
#12 0x00007f637de9b611 in KCModule::qt_metacall (this=0x15247c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x15a4f70) at ./kcmodule.moc:89
#13 0x00007f636297a200 in KCMLocale::qt_metacall (this=0x15247c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x15a4f70) at ./kcmlocale.moc:201
#14 0x00007f637c4b849a in QObject::event (this=0x15247c0, e=<value optimized out>) at kernel/qobject.cpp:1226
#15 0x00007f637d12b66d in QWidget::event (this=0x15247c0, event=0x16a2340) at kernel/qwidget.cpp:8718
#16 0x00007f637d0da9e4 in QApplicationPrivate::notify_helper (this=0xec9aa0, receiver=0x15247c0, e=0x16a2340) at kernel/qapplication.cpp:4462
#17 0x00007f637d0df3aa in QApplication::notify (this=<value optimized out>, receiver=0x15247c0, e=0x16a2340) at kernel/qapplication.cpp:4341
#18 0x00007f637ddf9866 in KApplication::notify (this=0x7fff58b8e920, receiver=0x15247c0, event=0x16a2340) at ../../kdeui/kernel/kapplication.cpp:311
#19 0x00007f637c4a449c in QCoreApplication::notifyInternal (this=0x7fff58b8e920, receiver=0x15247c0, event=0x16a2340) at kernel/qcoreapplication.cpp:731
#20 0x00007f637c4a7c25 in sendEvent (receiver=0x0, event_type=0, data=0xe6f220) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xe6f220) at kernel/qcoreapplication.cpp:1372
#22 0x00007f637c4cf253 in sendPostedEvents (s=0xec01c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#23 postEventSourceDispatch (s=0xec01c0) at kernel/qeventdispatcher_glib.cpp:277
#24 0x00007f6379b03bcd in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007f6379b043a8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007f6379b04639 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007f637c4cf3ef in QEventDispatcherGlib::processEvents (this=0xeb9ab0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#28 0x00007f637d181dfe in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x00007f637c4a3882 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#30 0x00007f637c4a3abc in QEventLoop::exec (this=0x7fff58b8e8b0, flags=...) at kernel/qeventloop.cpp:201
#31 0x00007f637c4a7ecb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#32 0x0000000000411616 in main (argc=5, argv=<value optimized out>) at ../../../systemsettings/app/main.cpp:49

This bug may be a duplicate of or related to bug 262488.

Possible duplicates by query: bug 269712, bug 267120, bug 262488, bug 259790.

Reported using DrKonqi
Comment 1 Dario Andres 2011-04-16 02:55:11 UTC
[Comment from a bug triager]
This issue is being tracked at bug 262488, merging.
Thanks

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