Latest LQ Deal: Latest LQ Deals
Go Back > Forums > Linux Forums > Linux - Networking
User Name
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.


  Search this Thread
Old 08-22-2007, 04:24 PM   #1
LQ Newbie
Registered: Aug 2007
Posts: 9

Rep: Reputation: 0
need VNC help on CentOS 5

Hey All,

First post here but I desperately need some help.

On a new CentOS 5 install I am trying to get VNC working where it will allow users to access the login screen on the server using VNCViewer. I have ran into multiple problems but have it isolated down to one problem. Here is the steps that I took.

1. Edited /etc/sysconfig/vncservers to specify the 2 users that I am granting access to 1:user1 2:user2

2. set a password for each user using vncpasswd

3. Edited the /home/username/.vnc/xstartup file to set up a persistent desktop.

4. When I run service vncserver start I receive the following:

[root@hostname]# service vncserver restart
Shutting down VNC server: 1:user1 2:user2 [ OK ]
Starting VNC server: 1:user1 xauth: (stdin):1: bad display name "hostname:1" in "add" command

New 'hostname:1 (user1)' desktop is hostname:1

Starting applications specified in /home/user1/.vnc/xstartup
Log file is /home/user1/.vnc/hostname:1.log

2:user2 xauth: (stdin):1: bad display name "hostname:2" in "add" command

New 'hostname:2 (user2)' desktop is hostname:2

Starting applications specified in /home/user2/.vnc/xstartup
Log file is /home/user2/.vnc/hostname:2.log

[ OK ]

Hostname,user1, and user2 have been changed for security reasons.

Here is what the VNC log file for user1 has to say


** (gnome-session:14900): WARNING **: Host name lookup failure on localhost.
Window manager warning: Log level 32: could not find XKB extension.
Passkey agent registration failed: Passkey agent already exists
WARNING:root:Could not open log file (/tmp/sealert.log) - using stderr
Introspect error: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.DBus.Introspectable" member "Introspect" error name "(unset)" destination "edu.duke.linux.yum")
Unable to connect to yum-updatesd. Please ensure that the yum-updatesd
package is installed and that the service is running.

** (eggcups:14965): WARNING **: IPP request failed with status 1030

** (eggcups:14965): WARNING **: IPP request failed with status 1030
Initializing nautilus-open-terminal extension

** (nm-applet:14989): WARNING **: <WARNING> nma_dbus_init (): nma_dbus_init() could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.64" is not allowed to own the service "org.freedesktop.NetworkManagerInfo" due to security policies in the configuration file'

Any advise is greatly appreciated. Thanks.
Old 08-22-2007, 07:27 PM   #2
LQ Newbie
Registered: Aug 2007
Posts: 9

Original Poster
Rep: Reputation: 0
I can now VNC in(firewall problem before) however now when I am completely logged out of the system when I successfully authenticate through VNC it is nothing but a grey screen. Any ideas?
Old 05-30-2009, 03:55 PM   #3
LQ Newbie
Registered: May 2009
Location: Yonkers, NY
Distribution: Centos
Posts: 1

Rep: Reputation: 0
Hi this is an old thread, but for the sake of completing it, you can find the answers about how to get beyond the "gray vnc screen" here (ok the forum won't let me post a URL for security reasons, so go to the "virtuatopia" website and search for "Running and Connecting to VNC Servers on a Xen Guest (domainU) System" and there you will find a possible fix to get past grey screen.

What it says there is that you have to edit the /home/username/.vnc/xstartup file as follows: uncomment these two lines:

# exec /etc/X11/xinit/xinitrc

and add at the end of the file the line (for a gnome desktop on vnc):

gnome-session &


# Uncomment the following two lines for normal desktop:
# exec /etc/X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &

gnome-session &

then of course restart vnc on the server and reconnect from fresh session on the client. By the way, the "vncviewer" from the command line can be buggy. There are many free 3rd party vnc viewer type tools which work better/look better.

Last edited by streetbiker; 05-30-2009 at 03:57 PM.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
VNC Server on CentOS - Viewer on XP pdelassus Linux - Software 12 05-28-2011 04:45 AM
How do I make vnc work in CentOS 5? TheStupid Red Hat 16 08-22-2007 12:05 PM
LXer: CentOS announces CentOS 5 i386 Live CD LXer Syndicated Linux News 0 07-11-2007 07:01 AM
VNC on :0 Hangs Centos on connect mr_r Linux - Software 0 06-19-2006 07:15 AM
update centos 4 rc1 to centos 4 trou yum? maxut cAos 2 03-04-2005 02:36 AM > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 03:22 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration