Version: 4.1 beta 2 (using KDE 4.0.83) Installed from: Ubuntu Packages OS: Linux I had a konqueror open and I logged out from KDE Stack trace: Application: Konqueror (konqueror), signal SIGSEGV (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 0xb610e940 (LWP 14192)] [KCrash handler] #6 0xb7464f5e in QString::lastIndexOf () from /usr/lib/libQtCore.so.4 #7 0xb76f54e2 in KStandardDirs::locateLocal (type=0xb7fc5af3 "appdata", filename=@0xbf8e1568, createDir=true, cData=@0x8095578) at /build/buildd/kde4libs-4.0.83/kdecore/kernel/kstandarddirs.cpp:1862 #8 0xb76f564f in KStandardDirs::locateLocal (type=0xb7fc5af3 "appdata", filename=@0xbf8e1568, cData=@0x8095578) at /build/buildd/kde4libs-4.0.83/kdecore/kernel/kstandarddirs.cpp:1853 #9 0xb7fad5c5 in ?? () from /usr/lib/kde4/lib/libkdeinit4_konqueror.so #10 0xb7fad67d in ?? () from /usr/lib/kde4/lib/libkdeinit4_konqueror.so #11 0xb7f5f37b in ?? () from /usr/lib/kde4/lib/libkdeinit4_konqueror.so #12 0xb7dc6084 in exit () from /lib/tls/i686/cmov/libc.so.6 #13 0xb7dae458 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #14 0x080484f1 in _start () #0 0xb7fd8410 in __kernel_vsyscall ()
"no debugging symbols found" means that the backtrace is not useful. If you can reproduce the crash, you should install the debug enabled packages before providing the backtrace. Read this page for the instructions: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports P.S: Does it happens every time? P.P.S: What happens if you use a clean user account?
Yes it happens every time. I'm sorry but I can't find any debugging package for libkdeinit4_konqueror.so so I don't have the symbols. I just open a KDE4 session with a folderview applet, pidgin, thunderbird, a clock applet and konqueror showing the standard KDE start page, then I logout and I have a crash.
Do you still experience this crash ? kdelibs-dbg and kdebase-dbg (or something close) are the packages to install to get a full backtrace.
No response, closing. p.s. An upgrade probably fixes this if it is the bug I'm thinking of.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!