Version: (using KDE KDE 3.4.3) Installed from: Debian testing/unstable Packages OS: Linux * Open http://www.rodehof.de/ * Choose "In Ihrer Nähe" in the main menu (third bottom item) * In the opening page there is a link list at the end of the page. Click "Besuch der Krippana in Losheim". => Konqueror crashes. I can reproduce this using konqueror 3.4.2 from debian/unstable. For testing this I have upgraded kde/konqueror to debian/experimental and tried it with konqueror 3.4.3, too. This version does also crash. If you open the link in a new tab or copy the link to clipboard, opening it in a new konqueror window manually, konqueror does not crash (in most cases). I have asked in a newsgroup if someone can reproduce this. Here are the answers: *) one with debian/sid does not have the problem. *) Konqueror 3.5 Beta 1 (3.4.91) does work (also with javascript activated) *) Scientific Linux 4.1; Konqueror 3.3.1-5.5 does work *) SuSE 9.3 Qt: 3.3.4; KDE: 3.4.2 Level "a"; Konqueror: 3.4.2 crashes *) SuSE Linux 9.3; qt3-3.3.4-23; kdeaddons3-konqueror-3.4.2-3; does work *) FreeBSD 5.4-STABLE; Konqueror 3.4.2 with javascript activated does work. *) debian sarge; konqueror 3.3.2 crashes. *) Kubuntu, Konqueror 3.4.3 does work *) Konqueror 3.4.2; SuSE 9.3 *) Konqueror 3.4.1 does work *) Konqueror 3.4.2; SUSE 10 does work *) one reports that deactivating javascript does help. But I can not confirm this. Here konqueror crashes with and without javascript. => It seems not to be the konqueror itself that is having a problem. But it might be configuration dependend somehow!?
My sid 3.4.2 won't crash and either 3.5beta2. Could you paste backtrace here?
Created attachment 13039 [details] Backtrace Konqueror 3.4.3 debian/sid Here is the backtrace as attachment. But it says: "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. ..."
I can't reproduce either. Pasting the backtrace (which, despite the message, isn't useless): (no debugging symbols found) 0xb7ccbb41 in waitpid () from /lib/tls/libc.so.6 #0 0xb7ccbb41 in waitpid () from /lib/tls/libc.so.6 #1 0xb7445d0c in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #2 <signal handler called> #3 0xb686cd94 in pthread_mutex_lock () from /lib/tls/libpthread.so.0 #4 0xb7d18c76 in pthread_mutex_lock () from /lib/tls/libc.so.6 #5 0xb68ea52e in _XUnregisterFilter () from /usr/X11R6/lib/libX11.so.6 #6 0xb68d4afb in XrmEnumerateDatabase () from /usr/X11R6/lib/libX11.so.6 #7 0xb68bcd89 in XKeysymToString () from /usr/X11R6/lib/libX11.so.6 #8 0xb7447e47 in KKeyServer::Sym::toString () from /usr/lib/libkdecore.so.4 #9 0xb7448461 in KKeyServer::Sym::toStringInternal () from /usr/lib/libkdecore.so.4 #10 0xb7448503 in KKey::toStringInternal () from /usr/lib/libkdecore.so.4 #11 0xb74491c9 in KKeySequence::toStringInternal () from /usr/lib/libkdecore.so.4 #12 0xb744ab26 in KShortcut::toStringInternal () from /usr/lib/libkdecore.so.4 #13 0xb7743b4a in KAction::initPrivate () from /usr/lib/libkdeui.so.4 #14 0xb774700c in KAction::KAction () from /usr/lib/libkdeui.so.4 #15 0xb7747183 in KToolBarPopupAction::KToolBarPopupAction () from /usr/lib/libkdeui.so.4 #16 0xb7f04d35 in KonqMainWindow::initActions () from /usr/lib/libkdeinit_konqueror.so #17 0xb7f17d5a in KonqMainWindow::KonqMainWindow () from /usr/lib/libkdeinit_konqueror.so #18 0xb7f1da24 in KonqMisc::createBrowserWindowFromProfile () from /usr/lib/libkdeinit_konqueror.so #19 0xb7f1e89b in KonqMisc::createNewWindow () from /usr/lib/libkdeinit_konqueror.so #20 0xb7f266b7 in KonqMainWindow::slotCreateNewWindow () from /usr/lib/libkdeinit_konqueror.so #21 0xb7f28d7d in KonqMainWindow::qt_invoke () from /usr/lib/libkdeinit_konqueror.so #22 0xb6c8ec5f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #23 0xb7b3db46 in KParts::BrowserExtension::createNewWindow () from /usr/lib/libkparts.so.2 #24 0xb6029f19 in KHTMLPart::slotChildURLRequest () from /usr/lib/libkhtml.so.4 #25 0xb6030e15 in KHTMLPart::qt_invoke () from /usr/lib/libkhtml.so.4 #26 0xb6c8ec5f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #27 0xb7b3d9a6 in KParts::BrowserExtension::openURLRequestDelayed () from /usr/lib/libkparts.so.2 #28 0xb7b4aa61 in KParts::BrowserExtension::slotEmitOpenURLRequestDelayed () from /usr/lib/libkparts.so.2 #29 0xb7b4abfc in KParts::BrowserExtension::qt_invoke () from /usr/lib/libkparts.so.2 #30 0xb603159c in KHTMLPartBrowserExtension::qt_invoke () from /usr/lib/libkhtml.so.4 #31 0xb6c8ec5f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #32 0xb701f5a5 in QSignal::signal () from /usr/lib/libqt-mt.so.3 #33 0xb6cacb30 in QSignal::activate () from /usr/lib/libqt-mt.so.3 #34 0xb6cb4444 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #35 0xb6c24778 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #36 0xb6c24996 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #37 0xb746a9fc in KApplication::notify () from /usr/lib/libkdecore.so.4 #38 0xb6bb4665 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #39 0xb6c15a44 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #40 0xb6bc83f8 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #41 0xb6c3cea2 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #42 0xb6c3cdcb in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #43 0xb6c23305 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #44 0xb7f232ac in kdemain () from /usr/lib/libkdeinit_konqueror.so #45 0xb7c4eec0 in __libc_start_main () from /lib/tls/libc.so.6 #46 0x080483d1 in ?? ()
Same backtrace as bug #102344 (kontact) and other konqueror crashes related to kaffeine. Do you have kaffeine installed? Does removing/disabling it make the problem go away?
Yes, I have kaffeine installed (kaffeine debian version 0.7.1-1.1). After removing kaffeine the crash disappears. Should I move the bug to kaffeine or are you taking over?
see e.g. http://sourceforge.net/forum/forum.php?thread_id=1344351&forum_id=297802 Maybe you'd have better luck with kplayer/kmplayer. *** This bug has been marked as a duplicate of 109498 ***