ERROR: Couldn't attach to DCOP server!

[edkb]

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://http://www.microdevsys.com/WordPress/2008/12/04/fedora-9-kde-4x-error-couldnt-attach-to-dcop-server/
http://www.microdevsys.com/WordPress/2008/12/04/fedora-9-kde-4x-error-couldnt-attach-to-dcop-server/ 
but your mileage may wary.

This would essentially give you two messaging systems for a while.  Maybe
that can work for you until everyone switches to DBus completely.

Regards,
Ed KB


Bugzilla from lfranchi at kde.org wrote:
> 
> On Saturday 09 May 2009 01:03:07 Bill Moseley wrote:
>> A year ago I setup a client-server using Perl to remotely run Amarok.
>> Worked perfectly.  Now I'm running Amarok 2.0.2 on Ubuntu and when the
>> script tries to connect to Amarok via DCOP I get:
>>
>>     ERROR: Couldn't attach to DCOP server!
>>
>> I'm using the DCOP::Amarok::Player Perl module.
>>
>> This sound familiar to anyone?
> 
> Yes. Amarok 2.x no longer uses DCOP. Along with the rest of KDE, Amarok
> has 
> switched to the DBus interprocess communicaton protocol. Amarok implements
> the 
> MPRIS spec for media players, it can be seen  here:
> 
> http://wiki.xmms2.xmms.se/wiki/MPRIS
> 
> cheers,
> leo
> 
> -----
> lfranchi at kde.org		Tufts  University 2010
> leonardo.franchi at tufts.edu                 The KDE Project
> _______________________________________________
> 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-tp23455529p24731708.html
Sent from the Amarok - Main mailing list archive at Nabble.com.