Version: (using KDE KDE 3.1) Installed from: Debian stable Packages OS: Linux Konqueror crashed while viewing the following html page (HTML+CSS+JavaScript only): http://www.linux-fuer-alle.de/ Dr.Konqui said (no debugging symbols found)...0x40ed0a59 in wait4 () from /lib/libc.so.6 #0 0x40ed0a59 in wait4 () from /lib/libc.so.6 #1 0x40f47e48 in __check_rhosts_file () from /lib/libc.so.6 #2 0x40d93453 in waitpid () from /lib/libpthread.so.0 #3 0x4055d6ea in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #4 0x40d90f54 in pthread_sighandler () from /lib/libpthread.so.0 #5 0x40e596b8 in sigaction () from /lib/libc.so.6 #6 0x41abba1f in khtml::Loader::qt_invoke () from /usr/lib/libkhtml.so.4 #7 0x408a0ef9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #8 0x40b01a93 in QSignal::signal () from /usr/lib/libqt-mt.so.3 #9 0x408b65b5 in QSignal::activate () from /usr/lib/libqt-mt.so.3 #10 0x408bba63 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #11 0x4084eb53 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #12 0x4084e954 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #13 0x404fe48a in KApplication::notify () from /usr/lib/libkdecore.so.4 #14 0x40831383 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #15 0x4081337c in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #16 0x4086031e in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #17 0x4086027b in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #18 0x4084ecaa in QApplication::exec () from /usr/lib/libqt-mt.so.3 #19 0x416c2b4c in main () from /usr/lib/konqueror.so #20 0x0804d3fd in strcpy () #21 0x0804e0fb in strcpy () #22 0x0804e545 in strcpy () #23 0x0804f316 in strcpy () #24 0x40e4914f in __libc_start_main () from /lib/libc.so.6
hmm.... does not happen for me. do you use auto proxy code?
No, I don't use a proxy. I think Konqueror crashed only once - the crash is not reproducible. But it occured while visiting the specified website (see above).
Looks like a duplicate of #54515 to me; that was fixed by Dirk in 3.1.1. *** This bug has been marked as a duplicate of 54515 ***