Fedora 11 and TigerVNC configuration

[tringate]

Let me star off by saying I do not have a clue what I might have done following so many different explanations on how to get this working.

My goal is to allow me to login using "TightVNC" on windows to my Fedora 11 machine. I actually had this working just fine the first time I installed Fedora 11 but after the third yum update I was no longer able to boot the system, so started over.

My problem now is that I must start the VNC server on the machine to get it to work rather than letting it activate during boot.

In the GUI services panel I am not able to "Enable" the service. It just stays red "disabled"

I am not sure what I have done to the system because I followed several different install guides which use different ways I guess to start this service. It fairly well matches what I did the original time I had this working.

The set up works just fine on Fedora 9.

I have edited or added the following files:

/etc/gdm/custom.conf

# GDM configuration storage

[xdmcp]
Enable=true
[chooser]

[security]
DisallowTCP=false
[debug]

/etc/xinetd.d/vnc-server

service vnc-server
{
disable = no
socket_type = stream
protocol = tcp
group = tty
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -geometry 1024x768 -depth 16 -once -fp /usr/share/X11/fonts/misc -securitytypes=none
}

/etc/sysconfig/vncservers

VNCSERVERS="1:root 2:tringate"
VNCSERVERARGS[1]="-geometry 1024x768 -depth 16"
VNCSERVERARGS[2]="-geometry 1024x768 -depth 16"

/root/.vnc/xstartup (No modifications made to this file)

#!/bin/sh

vncconfig -iconic &
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
OS=`uname -s`
if [ $OS = 'Linux' ]; then
case "$WINDOWMANAGER" in
*gnome*)
if [ -e /etc/SuSE-release ]; then
PATH=$PATH:/opt/gnome/bin
export PATH
fi
;;
esac
fi
if [ -x /etc/X11/xinit/xinitrc ]; then
exec /etc/X11/xinit/xinitrc
fi
if [ -f /etc/X11/xinit/xinitrc ]; then
exec sh /etc/X11/xinit/xinitrc
fi
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &


If I log in as root and issue the following command, I am able to use VNC just like I want to.

service vncserver start

The odd thing is on my original Fedora 11 system this server did start at boot which is apparently my only problem.

How do I find my bug on why I can't "enable" this service?

Oh yes, in the process of trying to fix this I have erased vino as one guide says to do, and installed a couple of other modules for tigerVNC as the guide directed. That guide is here on this forum. It made no difference at all at getting the service to automatically start at boot.

Once I start the server, I am able to login from windows perfectly just like I do on my Fedora 9 system.

Tom

[marcrblevins]

I prefer you to have root last in your /etc/sysconfig/vncservers file for now, can't remember why I did that.

Here is my list:

su -
yum install tigervnc-server
chkconfig vncserver on
service vncserver start

Have each normal user login and type:

vncpasswd

[tringate]

Thanks for the information. I have success.

Your instructions were so very simple, nothing like the other install guides.

The only difference I can see are placing root last, and adding the "chkconfig". line.

Thank you very much for solving my problem. My updated Fedora 11 is now almost ready for prime time.

[choudharypranay]

I tried the same in FC-14.
When i execute 3-rd step mentioned above
#service vncserver start
I get the following message:
Starting VNC Server: no displays configured [FAILED]

How should i configure the displays?

Thanks in advance.

[hyperplus]

I am starting on this myself... Try the following:

How you setup your:
/etc/sysconfig/vncservers

I will expect something like below: "display:username"
VNCSERVERS="1:theuser"

When you use: vncpasswd
You need to do it with "the user" account

[jimerman]

I prefer you to have root last in your /etc/sysconfig/vncservers file for now, can't remember why I did that.

Here is my list:

su -
yum install tigervnc-server
chkconfig vncserver on
service vncserver start

Have each normal user login and type:

vncpasswd


I have Fedora 17. When I run the chkconfig command, I get:

error reading information on service vncserver: no such file or directory

I am probably missing a config file?

---------- Post added at 07:12 PM ---------- Previous post was at 07:09 PM ----------

I should add, I am running Fedora / KDE. First, I tried going to Desktop Sharing, enabling that with a password (allowing uninvited incoming connections), but that doesn't seem to respond when I connect via TightVNC client using IP address. Perhaps I need to specify a display port?

Then, I came across this post, tried the yum install, but hit a brick wall there.

[smr54]

Tigervnc now works completely differently. I have a page about it at

http://home.roadrunner.com/~computertaijutsu/rhvnc.html

which goes through the changes and has a link to the thread about it these forums.