Version: 1.10.4 (using KDE 4.1.4) OS: Linux Installed from: Debian stable Packages This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. (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 0x7fa9c77026f0 (LWP 6575)] (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) (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) (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) (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) 0x00007fa9c46726e1 in nanosleep () from /lib/libc.so.6 [Current thread is 0 (process 6575)] Thread 1 (Thread 0x7fa9c77026f0 (LWP 6575)): #0 0x00007fa9c46726e1 in nanosleep () from /lib/libc.so.6 #1 0x00007fa9c4672507 in sleep () from /lib/libc.so.6 #2 0x00007fa9c64c9b0f in ?? () from /usr/lib/libkdeui.so.5 #3 0x00007fa9c64ca44a in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5 #4 <signal handler called> #5 0x00007fa9c45fd015 in raise () from /lib/libc.so.6 #6 0x00007fa9c45feb83 in abort () from /lib/libc.so.6 #7 0x00007fa9c463e0c8 in ?? () from /lib/libc.so.6 #8 0x00007fa9c4643a58 in ?? () from /lib/libc.so.6 #9 0x00007fa9c46460a6 in free () from /lib/libc.so.6 #10 0x00007fa9bfc26806 in ?? () from /usr/lib/libQtDBus.so.4 #11 0x00007fa9bfc1c550 in ?? () from /usr/lib/libQtDBus.so.4 #12 0x00007fa9c46006ad in exit () from /lib/libc.so.6 #13 0x00007fa9c45e846d in __libc_start_main () from /lib/libc.so.6 #14 0x00000000004023a9 in _start () #0 0x00007fa9c46726e1 in nanosleep () from /lib/libc.so.6
If you install the "kdepim-dbg" package you can get more information about the crash. The current trace is not really useful. Thanks
No response. Marking as NEEDSINFO
I am having the same problem. Additionally, trying to install "kdepim-dbg", the package is not found in the Yum database for Fedora 10. If you can provide a location for this file, I'll gladly install it and provide the trace you are seeking, which may or may not help the original poster, as neither of us knows what's causing the individual problems. :-)
If you are using Fedora then the package name is "kdepim4-debuginfo". I though you were using Debian (as the report says that). Regards
Apologies for not specifying that I'm using Fedora. FWIW, though, Yum say "No package kdepim4-debuginfo available". I'm going to try and recompile the SRPM to get the deubginfo RPM.
Sorry... I didn't have the debug repo enabled. I have enabled it and had to do some digging around. In case anyone else with Fedora comes along, the proper file name for Fedora users is kdepim-debuginfo-<version>.<release>.<arch> I am installing it now.
Closing the old crash reports which don't have a useful backtrace. Thanks.