Application that crashed: kded4 Version of the application: $Id: kded.cpp 944898 2009-03-26 13:01:25Z dfaure $ KDE Version: 4.2.88 (KDE 4.2.88 (KDE 4.3 >= 20090527)) Qt Version: 4.6.0 Operating System: Linux 2.6.27.21-0.1-default i686 What I was doing when the application crashed: Just browsing the menus. Hovering over the Tools/HTML Settings menu, it crashed before the menu was shown. It opened a "Could not start cookies" message shortly before. -- Backtrace: Application: KDE Daemon (kdeinit), signal: Aborted [KCrash Handler] #6 0xffffe430 in __kernel_vsyscall () #7 0xb6555990 in raise () from /lib/libc.so.6 #8 0xb65572c8 in abort () from /lib/libc.so.6 #9 0xb7ec5574 in qt_message_output (msgType=QtFatalMsg, buf=0x814a658 "ASSERT failure in QList<T>::operator[]: \"index out of range\", file /local/qt4/include/QtCore/qlist.h, line 403") at /local/git/Qt/qt/src/corelib/global/qglobal.cpp:2017 #10 0xb7ec565e in qFatal (msg=0xb80219ec "ASSERT failure in %s: \"%s\", file %s, line %d") at /local/git/Qt/qt/src/corelib/global/qglobal.cpp:2216 #11 0xb7ec570c in qt_assert_x (where=0xb41eb0ef "QList<T>::operator[]", what=0xb41eb0cd "index out of range", file=0xb41eae28 "/local/qt4/include/QtCore/qlist.h", line=403) at /local/git/Qt/qt/src/corelib/global/qglobal.cpp:1794 #12 0xb41df4ea in QList<QString>::operator[] (this=0xbf8ee9e4, i=0) at /local/qt4/include/QtCore/qlist.h:403 #13 0xb41dfd9c in KCookieServer::setDomainAdvice (this=0x80ec620, url=..., advice=...) at /local/svn/kde/trunk/KDE/kdelibs/kioslave/http/kcookiejar/kcookieserver.cpp:509 #14 0xb41ea423 in KCookieServerAdaptor::setDomainAdvice (this=0x812e9b8, url=..., advice=...) at /local/build/KDE/kdelibs/kioslave/http/kcookiejar/kcookieserveradaptor.cpp:129 #15 0xb41eabd4 in KCookieServerAdaptor::qt_metacall (this=0x812e9b8, _c=QMetaObject::InvokeMetaMethod, _id=15, _a=0xbf8eeb14) at /local/build/KDE/kdelibs/kioslave/http/kcookiejar/kcookieserveradaptor.moc:171 #16 0xb71ebcc9 in QDBusConnectionPrivate::deliverCall (this=0x808a028, object=0x812e9b8, msg=..., metaTypes=..., slotIdx=19) at /local/git/Qt/qt/src/dbus/qdbusintegrator.cpp:891 #17 0xb71ecd2d in QDBusConnectionPrivate::activateCall (this=0x808a028, object=0x812e9b8, flags=497, msg=...) at /local/git/Qt/qt/src/dbus/qdbusintegrator.cpp:796 #18 0xb71ed614 in QDBusConnectionPrivate::activateObject (this=0x808a028, node=..., msg=..., pathStartPos=19) at /local/git/Qt/qt/src/dbus/qdbusintegrator.cpp:1347 #19 0xb71ed8da in QDBusActivateObjectEvent::placeMetaCall (this=0x8127a50) at /local/git/Qt/qt/src/dbus/qdbusintegrator.cpp:1464 #20 0xb7fcc3ce in QObject::event (this=0x80ec620, e=0x8127a50) at /local/git/Qt/qt/src/corelib/kernel/qobject.cpp:1087 #21 0xb68e0afc in QApplicationPrivate::notify_helper (this=0x808fae0, receiver=0x80ec620, e=0x8127a50) at /local/git/Qt/qt/src/gui/kernel/qapplication.cpp:4053 #22 0xb68e7fb4 in QApplication::notify (this=0xbf8ef4a8, receiver=0x80ec620, e=0x8127a50) at /local/git/Qt/qt/src/gui/kernel/qapplication.cpp:3600 #23 0xb740180b in KApplication::notify (this=0xbf8ef4a8, receiver=0x80ec620, event=0x8127a50) at /local/svn/kde/trunk/KDE/kdelibs/kdeui/kernel/kapplication.cpp:302 #24 0xb7fbc43b in QCoreApplication::notifyInternal (this=0xbf8ef4a8, receiver=0x80ec620, event=0x8127a50) at /local/git/Qt/qt/src/corelib/kernel/qcoreapplication.cpp:624 #25 0xb7fbd072 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x805d618) at ../../include/QtCore/../../../../git/Qt/qt/src/corelib/kernel/qcoreapplication.h:213 #26 0xb7fbd23d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at /local/git/Qt/qt/src/corelib/kernel/qcoreapplication.cpp:1154 #27 0xb7fe75cf in postEventSourceDispatch (s=0x8091710) at ../../include/QtCore/../../../../git/Qt/qt/src/corelib/kernel/qcoreapplication.h:218 #28 0xb647a9c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #29 0xb647e083 in ?? () from /usr/lib/libglib-2.0.so.0 #30 0xb647e241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #31 0xb7fe71fc in QEventDispatcherGlib::processEvents (this=0x805f0a0, flags=...) at /local/git/Qt/qt/src/corelib/kernel/qeventdispatcher_glib.cpp:327 #32 0xb697f6b5 in QGuiEventDispatcherGlib::processEvents (this=0x805f0a0, flags=...) at /local/git/Qt/qt/src/gui/kernel/qguieventdispatcher_glib.cpp:202 #33 0xb7fbaa09 in QEventLoop::processEvents (this=0xbf8ef3f4, flags=...) at /local/git/Qt/qt/src/corelib/kernel/qeventloop.cpp:149 #34 0xb7fbae5a in QEventLoop::exec (this=0xbf8ef3f4, flags=...) at /local/git/Qt/qt/src/corelib/kernel/qeventloop.cpp:201 #35 0xb7fbd2ff in QCoreApplication::exec () at /local/git/Qt/qt/src/corelib/kernel/qcoreapplication.cpp:902 #36 0xb68e0977 in QApplication::exec () at /local/git/Qt/qt/src/gui/kernel/qapplication.cpp:3522 #37 0xb5cd61dd in kdemain (argc=1, argv=0x80843d8) at /local/svn/kde/trunk/KDE/kdelibs/kded/kded.cpp:938 #38 0x0804e383 in launch (argc=<value optimized out>, _name=<value optimized out>, args=<value optimized out>, cwd=0x0, envc=0, envs=0x0, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x8051e80 "0") at /local/svn/kde/trunk/KDE/kdelibs/kinit/kinit.cpp:671 #39 0x0804f8a6 in main (argc=2, argv=0xbf8ef7f4, envp=0xbf8ef800) at /local/svn/kde/trunk/KDE/kdelibs/kinit/kinit.cpp:1730 Reported using DrKonqi
Looks related to bug 192963 / bug 190394. BTW: I wonder if using the yet unsupported Qt4.6 would bring more issues (there are several people already using it). Thanks
I'm having the same problem, but without the crash - using OpenSUSE RPMs for 4.2.4 (r2), x86_64. I got a message about the cookies daemon. Once the problem has occurred, there is no obvious way of making Konqueror work properly again until the next login, which is very annoying. It refuses to talk to any web servers; local file access still works though. Steps to reproduce are as above: Open the menu Tools->HTML Settings. Steve
I take that back: after logging out and in, Konqueror still won't talk to any HTTP servers; kio HTTP connections are also affected. This is quite serious. Workaround: rename "Tools->HTML Settings" to "Tools->Completely bork Konqueror". :-) Steve
It turns out that the HTML settings thing seems to have changed or corrupted the proxy settings, hence no connections. Upon testing, it seems I was wrong about it not crashing - it's just that it's not Konqueror that crashes. The change in proxy settings is reproducible. I had it set to use preset env vars ($http_proxy et al), and after opening Tools->HTML Settings I got the crash, the cookies daemon message and the proxy settings were changed to manual (which was empty). It is only necessary to open the menu - you don't need to click any entries in it. Subsequent attempts to open the menu don't cause a crash or pop up a message, but they do silently change the proxy settings - giving the appearance of a borked konqueror. Steve
*** Bug 198938 has been marked as a duplicate of this bug. ***
*** Bug 200655 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 190394 ***