It's the interprocess server for KDE 2/3. If you want to get rid of these error messages then you should do this. Remove all KDE related files in /tmp Do this at a prompt.. rm -rf .DCOP* .mcop* .MCOP* then cd into your .kde2 or .kde (v3 went back to .kde) and delete the files called 'socket-zeus and tmp-zeus'. You should also make sure that if you have a reference to where QT and KDE are in your .bashrc or .zshrc that they are pointing to the correct versions for the software your trying to use. I forgot to change 2 to 3 when I upgrade to KDE3 and I got DCOP errors. An example of the entry in your .bashrc will be as follows... -- KDEDIR=/opt/kde3/ QTDIR=/usr/lib/qt3 export KDEDIR QTDIR -- If the above say kde2 and your trying to use kde3 then you might have weird errors such DCOP server error messages. If you need any further help just ask :) * Jon Doe (linuxgeek@woh.rr.com) [020407 13:34]: ::What is DCOP? I keep getting an error everytime I want to open konqueror or any KDE program: :: ::KLauncher could not be reached via DCOP :: ::This happens after a few hours of KDE being up, the only way to remidy it is to restart the X server as far as know. ::Anyone have any suggestions how to fix it or why its even happening? :: ::-- ::To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com ::For additional commands send e-mail to suse-linux-e-help@suse.com ::Also check the archives at http://lists.suse.com :: -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- "I've never been quarantined. But the more I look around the more I think it might not be a bad thing." -JC --=====-----=====--