You are not logged in.

Dear visitor, welcome to If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.


Friday, March 21st 2003, 1:50pm

DCOP error related to use of x-server

I'm new to linux, and recently moved my linux system from elxlinux to RH8, using KDE as my primary desktop there. I consistantly prior to this switch was connecting to my linux box from my windows box using Exceed (an x-server), and had no problems with this until the switch. Apparently Red Hat 8 comes with kde3 and my linux box is also now the lan server for a system of 5 computers. Since the switch, however, I have had a problem where if I access my linux box (Selene) using exceed at all, it causes an error in DCOP that does two things: 1) I am no longer able to save my local profile when rebooting the windows machine, and 2) I must reboot Selene before I can access any programs on her directly. I discovered that this was all related after some testing, and the error message when attempting to activate programs like netscape directly from Selene's desktop (not via exceed) is thus: KLauncher could not be Reached via DCOP. Does anyone have a solution to this problem?



Sunday, May 11th 2003, 12:48am

i too am having this problem. it happens after a certain amount of time. i am surfing the web then just out of no where, i cant anymore, it will say that it couldnt talk to KLauncher. Then I try to open another program (i.e. shell, or another konq window), and i get an error that pops up saying: "KLauncher couldn't be reached via DCOP". I am so stumped and no one seems to have the answer for it.

i am using KDE 3.0.5 and XFree86 4.2.0


Sunday, May 11th 2003, 2:49pm

Loks like a problem with your acces rights to your own home directory.
As root perform a
chown -R /home/username to solve this.

this usually happens when you change to root while your logged in as a user.

To avoid this in the future, pleas add to /etc/profile or similar file this option:
export KDE_HOME=~/.kde
(if ~/.kde is de place of your own configuration, could also be ~/.kde3)

Help mee om KDE 3.5.5 in het Nederlands te vertalen