Bug 155207

Summary:	(Fedora 8) all KDE applications crash (SIGABRT) right after being started
Product:	[I don't know] kde	Reporter:	Ming Pan <fallspinach>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	rdieter
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Ming Pan 2008-01-07 00:27:37 UTC

Version:            (using KDE KDE 3.5.8)
Installed from:    Fedora RPMs
Compiler:          gcc-4.1.2-33 is on the system 
OS:                Linux

I did a clean install of Fedora 8 from the DVD image. Whenever I start a KDE application, e.g. kate, kdvi, kdevelop, kompare, or any other KDE application from the K menu, it crashes and gives me the "KDE Crash Handler". Here is the Backtrace I got from a kate crash:

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208849936 (LWP 5873)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0x00110402 in __kernel_vsyscall ()
#7  0x00731690 in raise () from /lib/libc.so.6
#8  0x00732f91 in abort () from /lib/libc.so.6
#9  0x007699eb in __libc_message () from /lib/libc.so.6
#10 0x00771ac1 in _int_free () from /lib/libc.so.6
#11 0x007750f0 in free () from /lib/libc.so.6
#12 0x00c676f1 in operator delete () from /usr/lib/libstdc++.so.6
#13 0x00c4428d in std::string::_Rep::_M_destroy ()
   from /usr/lib/libstdc++.so.6
#14 0x006554a6 in ?? () from /usr/lib/qt-3.3/plugins/inputmethods/libqscim.so
#15 0x0065f2c6 in ?? () from /usr/lib/qt-3.3/plugins/inputmethods/libqscim.so
#16 0x00704fc0 in ?? () from /lib/ld-linux.so.2
#17 0x085bf560 in ?? ()
#18 0xbfaca888 in ?? ()
#19 0x0064feb9 in _init ()
   from /usr/lib/qt-3.3/plugins/inputmethods/libqscim.so
Backtrace stopped: frame did not save the PC

Comment 1 Ming Pan 2008-01-07 00:39:06 UTC

I sorry -- I was not precise just now:

NOT ALL KDE applications crash -- I just found two applications do survive: konsole, kontact. There may be more to survive but these are the only two I can find so far. But the list of crashed applications is far longer than the survivors.

It seems to be some simple thing ... don't know why not reported by others.

Comment 2 Ming Pan 2008-01-07 01:00:38 UTC

Just resolved it (kind of):

There is an older version of libstdc++ (version 5) in the /usr/lib directory. Everything works fine after it's been removed. But some applications depend on version 5 of libstdc++ ... more for me to worry.

Is there any way to allow more than one versions of libstdc++ existing in /usr/lib?