RH9 and vncserver

mcanada · 10-27-2004, 09:19 AM

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!

Lleb_KCir · 10-27-2004, 09:57 AM

what icon are you talking about?

when you want to use vncviewer you need to tell the system both the IP and the :1 screen name if you are going to a linux box, but if going to a windows box, i dont think you need the screen #

i have only gone from windows to linux boxes with vnc, or windows to windows. windows to windows you just need the IP address and the p/w for the server to authenticate you.

mcanada · 10-27-2004, 10:05 AM

Quote:

Originally posted by Lleb_KCir
what icon are you talking about?

when you want to use vncviewer you need to tell the system both the IP and the :1 screen name if you are going to a linux box, but if going to a windows box, i dont think you need the screen #

i have only gone from windows to linux boxes with vnc, or windows to windows. windows to windows you just need the IP address and the p/w for the server to authenticate you.

Thanks for the response!

Yes, since I started vncserver :5 on RH, when I run the client from windows I connect 192.168.1.107:5, then enter the password and the desktop comes up fine. I can run applications perfectly.

While the vncserver is running and I go back to the console (which is running KDE) I click on Mozilla to bring up the browser, and I get the message "KLauncher could not be reached via DCOP". It seems that just about any icon on the KDE desktop I click on gives me that message. If I logout completely and log in again on the console, everything is fine. Once I start the vncserver, it starts acting up again.

Lleb_KCir · 10-27-2004, 11:01 AM

hmm, sorry that is out of my league. i have been lucky to not have that issue with either RH9, or debain.

Lleb_KCir · 10-28-2004, 12:16 AM

just some FYI, i just had the exact same error on my debian box after doing a 8hr transcode from VOB to AVI using dvd::rip.

when i got home and touched the box directly i could not get access to anything and had to reboot the system remotely using ssh.

there is something going on with vncserver that causes that kind of issue. id love to hear from a guru around here as to what is going on.

Lleb_KCir · 10-29-2004, 01:58 PM

here is a little script that should help give KDE a swift kick in the butt when vncserver does not release the icons for you:... got this from my LUG

Code:

########### Start of 'klean' script ##########
#!/bin/sh
# A big hammer to kick KDE in the head

id=$(whoami)
files="/tmp/kde-${id}
/tmp/ksocket-${id}
/tmp/mcop-${id}
/tmp/orbit-${id}
/home/${id}/.kde/socket-*
/home/${id}/.kde/tmp-*
/home/${id}/.DCOP*
/home/${id}/.mcop*"

killall kdeinit 1>&2 2>/dev/null
for i in $files;do 
    rm -rf $i
done
##############################################

thank you Mark from Leap

build that in your favorite editor (i use vim), save it as a .sh then chmod +x /path/to/file.sh and you should then be able to run it to give KDE a boot to da head.