soccerdudez8 "at" hotmail.com
Thu May 6 21:28:01 2004
----- Original Message -----
From: "Corni Beerse" <cbeerse "at" lycos.nl>
To: "Nate McMaster" <soccerdudez8 "at" hotmail.com>
Cc: <vnc-list "at" realvnc.com>
Sent: Thursday, May 06, 2004 2:15 AM
Subject: Re: KDE
> Have you searched the SuSE knowledge base?
No, but good suggestion.
> You should have started with the vnc from your distribution. It is
> pre-configured to your distro. Hence, remove what you have installed from
> sources and install from the distro. Best to install all vnc* packages and
> it all works, remove obsolete ones. After that you can update the binaries
> (`Xvnc` and `vncviewer`) and optionally the java stuff (...vnc/classes/*).
> Better not try to do it fancy the first time. What does `vncserver`
> option) give?
I have tried running plain old `vncserver`. That works okay, sort of, but
the screen dimensions are too small and I read that setting the color depth
below 16 has effects on KDE.
> Possible problems in your options:
> :1 you specify a display number, this uses port 5801, 5901 and 6001. If
> them is not free, it will fail. If you don't specify, the `vncserver`
> will find a free one and report what it uses.
The port here is not the problem. The networking and the access work well.
The problem is that after I open up a connection from a remote computer, the
KDE desktop is displaying an error, this signal 11.
> -name "...." I've seen not-so-well-written scripts that cannot handle
> characters in names like this. It is pure cosmetic hence try without. Once
> works, add a name.
Your probably right, I'll try leaving out the `name` command, but I doubt it
will have much effect on the performance
Thanks for your help CBee