Bug 199835 - trying to access browse history in konqueror, KDE daemon crashed
Summary: trying to access browse history in konqueror, KDE daemon crashed
Status: RESOLVED DUPLICATE of bug 190394
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kded (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-12 07:26 UTC by andrew
Modified: 2009-07-14 16:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description andrew 2009-07-12 07:26:20 UTC
Application that crashed: kded4
Version of the application: $Id: kded.cpp 944898 2009-03-26 13:01:25Z dfaure $
KDE Version: 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2))
Qt Version: 4.5.2
Operating System: Linux 2.6.30-ARCH i686

What I was doing when the application crashed:
I wasn't actually doing anything manual with the cookie settings but at the same time as this crash occured I was trying to open the browse history in konqueror.   The history was blank, perhaps because of a restart?  Either way, at the time of the kded crash, konqueror popped an error message: (Cookies Disabled - Konqueror)
"Cookies could not be enabled, because the cookie daemon could not be started."

Cause or symptom, I don't know, but extra information.

 -- Backtrace:
Application: KDE Daemon (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  KCookieJar::setDomainAdvice (this=0x965bc98, _domain=@0x9591fec, _advice=KCookieAccept) at /usr/include/QtCore/qatomic_i386.h:120
#7  0xb2d510c9 in KCookieServer::setDomainAdvice (this=0x968e7b8, url=@0x9660810, advice=@0x96ad8e8)
    at /home/jan/kdemod/testing/kdelibs/src/kdelibs-4.2.96/kioslave/http/kcookiejar/kcookieserver.cpp:509
#8  0xb2d5bf4a in KCookieServerAdaptor::qt_metacall (this=0x969cf48, _c=QMetaObject::InvokeMetaMethod, _id=15, _a=0xbff2a57c)
    at /home/jan/kdemod/testing/kdelibs/src/build/kioslave/http/kcookiejar/kcookieserveradaptor.cpp:129
#9  0xb6467667 in QDBusConnectionPrivate::deliverCall (this=0x94ea630, object=0x969cf48, msg=@0x96d44e0, metaTypes=@0xbff2a6cc, slotIdx=19) at qdbusintegrator.cpp:891
#10 0xb646870d in QDBusConnectionPrivate::activateCall (this=0x94ea630, object=0x969cf48, flags=497, msg=@0x96d44e0) at qdbusintegrator.cpp:796
#11 0xb6468fd4 in QDBusConnectionPrivate::activateObject (this=0x94ea630, node=@0x96d44cc, msg=@0x96d44e0, pathStartPos=19) at qdbusintegrator.cpp:1347
#12 0xb646926a in QDBusActivateObjectEvent::placeMetaCall (this=0x96d44a0) at qdbusintegrator.cpp:1464
#13 0xb7e6ccae in QObject::event (this=0x968e7b8, e=0x96d44a0) at kernel/qobject.cpp:1110
#14 0xb6a39674 in QApplicationPrivate::notify_helper (this=0x94e6c48, receiver=0x968e7b8, e=0x96d44a0) at kernel/qapplication.cpp:4056
#15 0xb6a40d5c in QApplication::notify (this=0xbff2af60, receiver=0x968e7b8, e=0x96d44a0) at kernel/qapplication.cpp:3603
#16 0xb7479f0a in KApplication::notify (this=0xbff2af60, receiver=0x968e7b8, event=0x96d44a0) at /home/jan/kdemod/testing/kdelibs/src/kdelibs-4.2.96/kdeui/kernel/kapplication.cpp:302
#17 0xb7e5cedb in QCoreApplication::notifyInternal (this=0xbff2af60, receiver=0x968e7b8, event=0x96d44a0) at kernel/qcoreapplication.cpp:610
#18 0xb7e5dac2 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x947abc8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#19 0xb7e5dc8d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#20 0xb7e8794f in postEventSourceDispatch (s=0x94e8f10) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#21 0xb6643d98 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb66473e0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#23 0xb6647513 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0xb7e8757c in QEventDispatcherGlib::processEvents (this=0x947a610, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:327
#25 0xb6ad7475 in QGuiEventDispatcherGlib::processEvents (this=0x947a610, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202
#26 0xb7e5b489 in QEventLoop::processEvents (this=0xbff2aeb4, flags=) at kernel/qeventloop.cpp:149
#27 0xb7e5b8da in QEventLoop::exec (this=0xbff2aeb4, flags={i = 0}) at kernel/qeventloop.cpp:201
#28 0xb7e5dd4f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#29 0xb6a394f7 in QApplication::exec () at kernel/qapplication.cpp:3525
#30 0xb59f2be7 in kdemain (argc=1, argv=0x94d20b8) at /home/jan/kdemod/testing/kdelibs/src/kdelibs-4.2.96/kded/kded.cpp:938
#31 0x0804de42 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=0x8050f4b "0") at /home/jan/kdemod/testing/kdelibs/src/kdelibs-4.2.96/kinit/kinit.cpp:676
#32 0x0804fa38 in main (argc=2, argv=0xbff2b564, envp=0xbff2b570) at /home/jan/kdemod/testing/kdelibs/src/kdelibs-4.2.96/kinit/kinit.cpp:1735

This bug may be a duplicate of or related to bug 190394

Reported using DrKonqi
Comment 1 Dario Andres 2009-07-14 16:05:55 UTC
Indeed, this is related to bug 190394. Thanks

*** This bug has been marked as a duplicate of bug 190394 ***