Bug 210637

Summary:	Language module fails to start
Product:	[Applications] systemsettings	Reporter:	Pavel Baranchikov <maednoldor>
Component:	kcmshell	Assignee:	kdelibs bugs <kdelibs-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	andresbajotierra
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Crash report from KDE

Description Pavel Baranchikov 2009-10-15 08:01:29 UTC

Version:           1.0 (using KDE 4.3.2)
OS:                Linux
Installed from:    SuSE RPMs

Neither from GUI, nor from console, language module does not start - it crashes:

pavel@rzn-sepak-bpa:~/Documents/Статьи> kcmshell4 language         
QMutex::lock: mutex lock failure:                                  
QMutex::lock: mutex unlock failure:                                
*** glibc detected *** kcmshell4: free(): invalid pointer: 0x08212a58 ***
======= Backtrace: =========                                             
/lib/libc.so.6[0xb6b01654]                                               
/lib/libc.so.6(cfree+0x9c)[0xb6b02f3c]                                   
/usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0xb6ce3ec1]                         
/usr/lib/libQtCore.so.4[0xb786016d]                                      
/usr/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x208)[0xb785cd18]
/usr/lib/libQtCore.so.4(_ZN16QCoreApplication16sendPostedEventsEP7QObjecti+0x2d)[0xb785cfad]                      
/usr/lib/libQtCore.so.4[0xb7887c8f]                                                                               
/usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1e8)[0xb63759c8]                                              
/usr/lib/libglib-2.0.so.0[0xb6379083]                                                                             
/usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x71)[0xb6379241]                                              
/usr/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x58)[0xb78878d8]
/usr/lib/libQtGui.so.4[0xb6edeca5]                                                                                           
/usr/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x4a)[0xb785a78a]                    
/usr/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xf2)[0xb785abd2]                              
/usr/lib/libQtGui.so.4(_ZN7QDialog4execEv+0x103)[0xb7310173]                                                                 
/usr/lib/libkdeinit4_kcmshell4.so(kdemain+0x147d)[0xb804cb8d]                                                                
kcmshell4[0x80486a2]                                                                                                         
/lib/libc.so.6(__libc_start_main+0xe5)[0xb6aab705]                                                                           
kcmshell4[0x80485e1]                                                                                                         
======= Memory map: ========                                                                                                 
08048000-08049000 r-xp 00000000 08:06 993667     /usr/bin/kcmshell4                                                          
08049000-0804a000 r--p 00000000 08:06 993667     /usr/bin/kcmshell4                                                          
0804a000-0804b000 rw-p 00001000 08:06 993667     /usr/bin/kcmshell4                                                          
 and a log of output else

Comment 1 Pavel Baranchikov 2009-10-15 08:02:43 UTC

Created attachment 37588 [details]
Crash report from KDE

Comment 2 Christoph Feck 2009-10-15 15:40:33 UTC

This possibly is related to an oversight while backporting fixes to 4.3.2. Packagers are instructed to provide updated packages. You might want to check in a few days for updated packages.

Comment 3 Dario Andres 2009-10-16 18:10:25 UTC

Indeed, this looks like the memory corruption affecting the Region&Language module: bug 209751. Thanks

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