Application that crashed: konqueror Version of the application: 4.3.00 (KDE 4.3.0) KDE Version: 4.3.00 (KDE 4.3.0) Qt Version: 4.5.2 Operating System: Linux 2.6.30-1-686 i686 Distribution: Debian GNU/Linux unstable (sid) What I was doing when the application crashed: I wrote some reply to a bug report on bugs.kde.org and switched applications. An hour or two later, I realized that there had been a timeout while trying to submit the update. I clicked the "back" button and konqui crashed. -- Backtrace: Application: Konqueror (kdeinit4), signal: Segmentation fault [KCrash Handler] #6 0xb29b55e8 in qobject_cast<KHTMLPart*> (this=0xb13fc48) at /usr/include/qt4/QtCore/qobject.h:443 #7 KHTMLPart::parentPart (this=0xb13fc48) at ../../khtml/khtml_part.cpp:5196 #8 0xb29b5642 in KHTMLPart::toplevelURL (this=0xb13fc48) at ../../khtml/khtml_part.cpp:7170 #9 0xb2baf5de in khtml::Loader::servePendingRequests (this=0x9aedc98) at ../../khtml/misc/loader.cpp:1404 #10 0xb2bb821b in khtml::Loader::qt_metacall (this=0x9aedc98, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbffea568) at ./loader.moc:134 #11 0xb7df2ad3 in QMetaObject::activate (sender=0x9aedcac, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112 #12 0xb7df3722 in QMetaObject::activate (sender=0x9aedcac, m=0xb7eced84, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186 #13 0xb7e2e117 in QTimer::timeout (this=0x9aedcac) at .moc/release-shared/moc_qtimer.cpp:128 #14 0xb7df8e3e in QTimer::timerEvent (this=0x9aedcac, e=0xbffea9ec) at kernel/qtimer.cpp:261 #15 0xb7dedb6f in QObject::event (this=0x9aedcac, e=0xbffea9ec) at kernel/qobject.cpp:1074 #16 0xb6a897d4 in QApplicationPrivate::notify_helper (this=0x972d4e0, receiver=0x9aedcac, e=0xbffea9ec) at kernel/qapplication.cpp:4056 #17 0xb6a9193e in QApplication::notify (this=0xbffeae28, receiver=0x9aedcac, e=0xbffea9ec) at kernel/qapplication.cpp:3603 #18 0xb74d200d in KApplication::notify (this=0xbffeae28, receiver=0x9aedcac, event=0xbffea9ec) at ../../kdeui/kernel/kapplication.cpp:302 #19 0xb7ddd96b in QCoreApplication::notifyInternal (this=0xbffeae28, receiver=0x9aedcac, event=0xbffea9ec) at kernel/qcoreapplication.cpp:610 #20 0xb7e0c301 in QCoreApplication::sendEvent (this=0x973377c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #21 QTimerInfoList::activateTimers (this=0x973377c) at kernel/qeventdispatcher_unix.cpp:572 #22 0xb7e088a0 in timerSourceDispatch (source=0x9733748) at kernel/qeventdispatcher_glib.cpp:165 #23 0xb6658368 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0xb665b8c3 in ?? () from /usr/lib/libglib-2.0.so.0 #25 0xb665ba48 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0xb7e087f8 in QEventDispatcherGlib::processEvents (this=0x96b2500, flags=...) at kernel/qeventdispatcher_glib.cpp:327 #27 0xb6b28f85 in QGuiEventDispatcherGlib::processEvents (this=0x96b2500, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #28 0xb7ddbfba in QEventLoop::processEvents (this=0xbffeac10, flags=...) at kernel/qeventloop.cpp:149 #29 0xb7ddc402 in QEventLoop::exec (this=0xbffeac10, flags=...) at kernel/qeventloop.cpp:201 #30 0xb7dde859 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #31 0xb6a89657 in QApplication::exec () at kernel/qapplication.cpp:3525 #32 0xb4a06c1f in kdemain () from /usr/lib/libkdeinit4_konqueror.so #33 0x0804e291 in launch (argc=4, _name=0x96dee44 "konqueror", args=0x96deebb "", cwd=0x96deebc "/home/richih", envc=30, envs=0x96deecd "SSH_AGENT_PID=3588", reset_env=true, tty=0x0, avoid_loops=false, startup_id_str=0x96df346 "roadwarrior;1250372919;727126;3911_TIME33025737") at ../../kinit/kinit.cpp:676 #34 0x0804ea15 in handle_launcher_request (sock=27, who=<value optimized out>) at ../../kinit/kinit.cpp:1168 #35 0x0804ef1c in handle_requests (waitForPid=0) at ../../kinit/kinit.cpp:1352 #36 0x0804f6c9 in main (argc=2, argv=0xbffeb874, envp=0xbffeb880) at ../../kinit/kinit.cpp:1788 Reported using DrKonqi
Hmm, seems it was another konqui instance. I replied to https://bugs.kde.org/show_bug.cgi?id=188539 yesterday and apparently did not close that tab. When (re)starting KDE, I was not connected to the net so I got a timeout when loading the update page. Then I pressed back and got the crash.
The backtrace is like the one on bug 200717. Thanks
*** This bug has been marked as a duplicate of bug 200717 ***