Description of problem: QT and KDE apps crash and caused SISGSEV straight after opening, even though logging in to KDE session is normal. Apps also crash when launched from GNOME. Can't produce useful backtraces, but this happened after updating my system since May 20. List of Apps that crash include amaroK, lyx, Konqueror, k3b. Version-Release number of selected component (if applicable): qt-3.3.5-13 (i386, x86_64) kdebase-3.5.2-0.4.fc5 (both arch) kdelibs-3.5.2-0.2.fc5 (both arch) amarok-1.4-0.12.beta3.fc5 lyx-1.4.1-4.fc5 k3b-0.12.14-0.FC5.2 kdemultimedia-3.5.2-0.1.fc5 kdenetwork-3.5.2-0.1.fc5 kdegraphics-3.5.2-0.1.fc5 How reproducible: All KDE applications expected to crash whenever opened. Steps to Reproduce: 1. Log in to system 2. Open KDE/QT app 3. After a few seconds, Crash Actual results: Application crashes Expected results: Application to run smoothly Additional info: Just did a clean install of FC5 where everything worked as per normal until doing a massive update. After that, the problem is reproduced.
Just to corroborate this, here is the backtrace of k3b (not too useful, but points out the culprit library: K3B bactrace, as reported by KCrash handler: (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) ... [Thread debugging using libthread_db enabled] [New Thread 47457266815136 (LWP 18778)] (no debugging symbols found) ... [KCrash handler] #5 0x00002b298621dd52 in scim::QScimInputContext::metaObject () from /usr/lib64/qt-3.3/plugins/inputmethods/libqscim.so #6 0x0000000000000000 in ?? () amaroK produces the same. Running the above mentionned packages on x86_64 Core 5
Created attachment 129838 [details] bz2 compressed output from "strace -o kdvi.strace.txt kdvi"
Please add i686 to the list of hardware affected. I also have kde/qt applications crashing/SIGSEGV 11-ing after the last week's round of FC5 updates (from yum, with just core, updates, extras enabled). The applications will open and run, but immediately crash upon closing. This occurs both logged into GNOME as well as KDE. Here is a typical backtrace (this one right after closing kdvi, but I get exactly the same backtrace with k3b, kate, kppp, etc.) (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) <== many times [Thread debugging using libthread_db enabled] [New Thread -1208153408 (LWP 5288)] (no debugging symbols found) <== many times [KCrash handler] #6 0x009b898e in exit () from /lib/libc.so.6 #7 0x009a372c in __libc_start_main () from /lib/libc.so.6 #8 0x080501c1 in ?? () I attached above the output of "strace -o kdvi.strace.txt kdvi"
it seems a bug in scim-qtimm, SCIM input method module for Qt. Could you please remove this package scim-qtimm (rpm -e scim-qtimm) and try again? Thanks
Indeed, that worked. AmaroK starts now, and presumably so will K3B... (checking -\|/-) Yes it does, so I assume the other apps will also work. Thanks for the tip, and one question: Why was scim-qtimm needed? Will it be marked as a dep for future updates? Thanks!
Removing scim-qtimm also fixed the problem on i686 as well.
One odd thing is I've had the same version of scim-qtimm-0.9.4-2.1.1 since installing FC5 from disk; it hasn't changed. And yet the problems with kde/qt applications didn't start until ~1 week ago.
Hi, as expected removing scim qtimm solved the problem. Lyx and amaroK now running. Thanks!
*** Bug 192587 has been marked as a duplicate of this bug. ***
This is related to the fact that scim-qtimm can't build with libstdc++so7. This problem is expected to go away in FC6. See bug 182177 for more details. (It was probably just luck that scim-qtimm wasn't crashing apps previously.)
*** Bug 189209 has been marked as a duplicate of this bug. ***
*** Bug 192471 has been marked as a duplicate of this bug. ***
Problem till exist at Devel version.
Created attachment 130382 [details] BackTrack for kate crash
The rawhide kate crash is bug 193855.
*** This bug has been marked as a duplicate of 192471 ***
(In reply to comment #7) > One odd thing is I've had the same version of scim-qtimm-0.9.4-2.1.1 since > installing FC5 from disk; it hasn't changed. And yet the problems with kde/qt > applications didn't start until ~1 week ago. It was probably triggered by the change of libstdc++so7 version somehow.