RH9 and VNCSERVER

[mcanada]

I'm having a problem running vncserver on my RedHat 9 system.

I manually startup the server using the following command:

vncserver :5

On my windows system, I run the vnc client and connect. I get the desktop and everything works fine.

Back on my RH system desktop, I click on an icon and get the error message:

KLauncher could not be reached via DCOP

Does anyone know what this means? Any possible solutions?

Thanks in advance!

[madcompnerd]

Use Gnome.

[mcanada]

Originally posted by madcompnerd
Use Gnome.


Thanks madcompnerd for the response, however I don't think that is a valid explaination. I would prefer to use KDE instead of Gnome.

[mrBen]

Are you sure that it is related to VNC?

Plus, check whether there are any known issues for Klauncher

[mcanada]

Originally posted by mrBen
Are you sure that it is related to VNC?

Plus, check whether there are any known issues for Klauncher

Thanks mrBen

This only occurs when I have started vncserver. I may have not explained myself very well in the first post.

I have a console which is running the KDE desktop. From a terminal window I manually start the vncserver with the command 'vncserver :5'. I run the vnc client on a windows machine and connect 192.168.1.107:5, enter the password and the kde desktop comes up. I can run my applications from the desktop and everything looks great.

While the vncserver is running I go back to the console and click on Mozilla, for example. It displays the message 'KLauncher could not be reached via DCOP'. It seems that just about any icon I click on gives me that same message. If I logout completely and login again on the console, everything is back to normal. If I start the vncserver again and login from the windows machine, the problem starts up again.

Could it be something with the number of "virtual desktops" I have configured? I have 4 virtual desktops that are available from the panel.

[mrBen]

Hmmm - could be something to do with the way that vnc and kde are interacting - I know that when I have vnc running I can't run certain apps on the both machines (eg Evolution). It may be that the launcher is having problems with being run twice by the same user.

[mcanada]

Originally posted by mrBen
Hmmm - could be something to do with the way that vnc and kde are interacting - I know that when I have vnc running I can't run certain apps on the both machines (eg Evolution). It may be that the launcher is having problems with being run twice by the same user.

Yes, sounds logical. My goal is to not have a console and just connect to the RH box via VNC. So if there is only 1 version of KDE running (via VNC) things will probably be fine. I was just doing this in the interum.

Thanks mrBen for you help!

[techwise]

it would be solved if you just connected to the currently running x session.

That is the way I have allways done it and never had the problem you have stated.

Mike

[fe2o3]

There has been discussions in the past about environment variables creating side-effects in your vncserver instance. I *used* to hit a text console to start my vncserver.

However, I now have a ~/.vnc/xstartup which starts my kde instance. I set the KDEHOME because I autofs-nfs mount my home directory around to lots of machines. I fire up vncservers on these machines sometimes. This way, the kde instances don't conflict with each other.


~/.vnc/xstartup
#!/bin/sh
export KDEHOME=${HOME}/.kdevnc-$(hostname)
exec startkde