kded, DCOP and mysteries

[Kevin Krammer]

On Saturday 16 August 2008, Anne Wilson wrote:
> This started with a message that I must allow cookies in konqueror, in
> order to use a secure site, but cookies are already allowed.  When someone
> pointed me to it I discovered that the cookie jar is not running.  I have,
> from time to time, come across notices that DCOP could not be reached. 
> Now, after killing kded, when I try to restart it I get 'FATAL: DCOP
> communication problem!
> Aborted'
>
> What's going on, and what should I do about it?

kded could not be running, dcopserver could not be running or either of the 
two processes could be in a deadlock (though there are quite some guards 
against that in the code)

In a KDE4 setup it is similar, just using D-Bus instead of DCOP

If both processes are running (they should since they are started during KDE 
startup), the cookie module of kded might not be loaded.

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde/attachments/20080817/946f6167/attachment.sig>
-------------- next part --------------
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.