ERROR: Couldn't attach to DCOP server!

[edkb]

Interesting.  As I recall, dcopserver would simply die after being started
through applications within the new KDE 4+ environment.  Running
/usr/bin/kdeinit as noted in the blog resolved the issue.  I'm curious, what
do you mean by botched permissions then?

Thanks,
EdKB


Bugzilla from rdieter at math.unl.edu wrote:
> 
> edkb wrote:
> 
>> Yes.  Lot's of apps that relied on DCOP displayed this error in the
>> latest
>> KDE release (4+) so ended up seeing this all over the place after
>> upgrading.
>> Konsole was one of them.  App developers may have caught up with KDE by
>> now but not sure.
>> 
>> Anyway, I've managed to reenable DCOP following these steps
>> http://www.microdevsys.com/WordPress/2008/12/04/fedora-9-kde-4x-error-
> couldnt-attach-to-dcop-server/
>> but your mileage may wary.
> 
> dcopserver will launch on-demand.  That blog simply highlights failures
> due 
> to botched permissions... once those are fixed, everything should "just 
> work" again.
> 
> -- Rex
> 
> _______________________________________________
> Amarok mailing list
> Amarok at kde.org
> https://mail.kde.org/mailman/listinfo/amarok
> 
> 

-- 
View this message in context: http://www.nabble.com/ERROR%3A-Couldn%27t-attach-to-DCOP-server%21-tp23455529p24750367.html
Sent from the Amarok - Main mailing list archive at Nabble.com.