Troubleshooting RealVNC on Slackware

JockVSJock · 11-20-2006, 10:08 PM

Got to thinking, does it matter what user starts the vncserver?

I have a user called media, but I'm trying to user the vncviewer as my regular user, cmmiller.

Maybe this is the problem?

JockVSJock · 12-02-2006, 08:52 PM

UPDATE

Ok, I'm still working on this...I still have vnc failure on my server.

When I go to start the vncserver on my server this is the output.

Code:

cmmiller@lambda:/usr/share/realvnc/vnc-4_1_2-x86_linux$ ./vncserver

New 'lambda:1 (cmmiller)' desktop is lambda:1

Starting applications specified in /home/cmmiller/.vnc/xstartup
Log file is /home/cmmiller/.vnc/lambda:1.log

cmmiller@lambda:/usr/share/realvnc/vnc-4_1_2-x86_linux$ ps aux | grep vnc
cmmiller  9285  0.3  0.1   2448  1232 pts/2    S    20:49   0:00 /bin/sh /home/cmmiller/.vnc/xstartup

It tells me that vncserver is starting, but ps aux isn't finding it...So long story short, the vncserver can't even start...what the hell is causing this?!??

Here is the output from the vnc log

Code:

cmmiller@lambda:~/.vnc$ cat lambda:1.log
sh: Xvnc: command not found
xsetroot:  unable to open display 'lambda:1'
xterm Xt error: Can't open display: lambda:1
xsetroot:  unable to open display 'lambda:1'
xset:  unable to open display "lambda:1"
xset:  unable to open display "lambda:1"
xset:  unable to open display "lambda:1"
xsetroot:  unable to open display 'lambda:1'
startkde: Starting up...
ksplash: cannot connect to X server lambda:1
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
kded: cannot connect to X server lambda:1
DCOP aborting call from 'anonymous-9384' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
kcminit_startup: cannot connect to X server lambda:1
ksmserver: cannot connect to X server lambda:1
startkde: Shutting down...
klauncher: Exiting on signal 1
startkde: Running shutdown scripts...
startkde: Done.

If anyone can post any ideas to troubleshoot, I would be greatful...

thanks

EDIT: For some reason the output log has an error for Xvnc, but I see that it is installed, is there any way to check and see if the vnc install went ok?

ryanoa · 12-02-2006, 09:20 PM

According to their documentation vncserver is just a perl script that starts Xvnc. According to your log, it can't find the command. Is Xvnc installed? It should be in /usr/bin. Try:

Code:

which Xvnc

Regards,
Ryan

JockVSJock · 12-03-2006, 08:05 AM

As I was thinking, there is no Xvnc...

Code:

cmmiller@lambda:/usr/bin$ whereis Xvnc
Xvnc:
cmmiller@lambda:/usr/bin$ ls -al | grep Xvnc
cmmiller@lambda:/usr/bin$

What would be the best way to troubleshoot from here? Reinstall VNC?

thanks

UPDATE:

Ya!!! Got it to work...I am happy!

This is where I made the error.

It been along time since I've worked with RealVNC under Linux, 2004. Its funny cause you get something up and running, and you often forget how you got it up and running.

Anyways, I didn't run vncinstall...And the last time I was using realvnc, I don't remember running this...

thanks to everyone who helped