In SuSE 8.2, KDE 3.1, Konqueror crashes with signal 11. The backbrace is shown below. This originally worked, but I done an Online update from YAST, then this happened. Can someone tell what the problem is? Am I going to have to reinstall again? Art (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)...[New Thread 16384 (LWP 4027)] (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)...0x40f48cf7 in waitpid () from /lib/libpthread.so.0 #0 0x40f48cf7 in waitpid () from /lib/libpthread.so.0 #1 0x4064fc89 in KCrash::defaultCrashHandler(int) () from /opt/kde3/lib/libkdecore.so.4 #2 0x40f47895 in __pthread_sighandler () from /lib/libpthread.so.0 #3 <signal handler called>
check out this page, it gives some infor about signal 11 problem. Probably memory fault. http://www.bitwizard.nl/sig11/ Regards ,himba Dne petek 23. maja 2003 04:50 je Art Fore napisal(a):
In SuSE 8.2, KDE 3.1, Konqueror crashes with signal 11. The backbrace is shown below. This originally worked, but I done an Online update from YAST, then this happened. Can someone tell what the problem is? Am I going to have to reinstall again?
Art
(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)...[New Thread 16384 (LWP 4027)]
(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)...0x40f48cf7 in waitpid () from /lib/libpthread.so.0 #0 0x40f48cf7 in waitpid () from /lib/libpthread.so.0 #1 0x4064fc89 in KCrash::defaultCrashHandler(int) () from /opt/kde3/lib/libkdecore.so.4 #2 0x40f47895 in __pthread_sighandler () from /lib/libpthread.so.0 #3 <signal handler called>
-- This mail was Kmailed.
Memory problem did not seem reasonable since it had worked before the last SuSE update. I ended up renaming the .kde directory under user, logging out and back in, and this fixed it. Got the from a " [kde-linux] konqueror wont open in File Management View" on the KDE list.. Art himbA wrote:
check out this page, it gives some infor about signal 11 problem. Probably memory fault.
http://www.bitwizard.nl/sig11/
Regards ,himba
Dne petek 23. maja 2003 04:50 je Art Fore napisal(a):
In SuSE 8.2, KDE 3.1, Konqueror crashes with signal 11. The backbrace is shown below. This originally worked, but I done an Online update from YAST, then this happened. Can someone tell what the problem is? Am I going to have to reinstall again?
Art
(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)...[New Thread 16384 (LWP 4027)]
(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)...0x40f48cf7 in waitpid () from /lib/libpthread.so.0 #0 0x40f48cf7 in waitpid () from /lib/libpthread.so.0 #1 0x4064fc89 in KCrash::defaultCrashHandler(int) () from /opt/kde3/lib/libkdecore.so.4 #2 0x40f47895 in __pthread_sighandler () from /lib/libpthread.so.0 #3 <signal handler called>
participants (2)
-
Art Fore -
himbA