Results 1 to 4 of 4
Hello,
I recently decided to try tight vnc server and installed 1.3.9 on a remote machine. The gnome desktop manager does not start. I was successfull to start twm though.
...
- 06-03-2008 #1Just Joined!
- Join Date
- Jun 2008
- Posts
- 4
Window Manager Problem with VNC
Hello,
I recently decided to try tight vnc server and installed 1.3.9 on a remote machine. The gnome desktop manager does not start. I was successfull to start twm though.
For reference, below are the various ~/.vnc/xstartup configurations I tried:
The following one starts twm without a problem:
When I remove the two lines at the top I only get a grey screen with a cross shaped pointer. This is as follows:Code:#!/bin/sh # Uncomment the following two lines for normal desktop: # unset SESSION_MANAGER # 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 80x60+1+1 -ls -title "$VNCDESKTOP Desktop" & twm &
I alsı tried to put gnome-session & at the end instead of twm, it does not work either (i.e. the same grey screen)Code:#!/bin/sh # Uncomment the following two lines for normal desktop: unset SESSION_MANAGER 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 80x60+1+1 -ls -title "$VNCDESKTOP Desktop" & twm &
Note that I did configure & make of the Xvnc and tightvncserver as a normal user because I don't have root rigts. I'm sure that Xvnc and tightvnc that I installed are in the path.Code:#!/bin/sh # Uncomment the following two lines for normal desktop: unset SESSION_MANAGER 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 80x60+1+1 -ls -title "$VNCDESKTOP Desktop" & gnome-session &
The interesting part is that before installing tightvnc server, I was using the realvnc that is already installed in the server and I didn't have any problems like that.
I would appreciate any help on this matter.
Thanks in advance
Amac
- 06-03-2008 #2Just Joined!
- Join Date
- Jun 2008
- Posts
- 4
Well, I tried to revert back to the old vncserver (by removing ~/local/bin from PATH where the new tighvncserver was installed). I see gnome is not loaded also in this case. It seems like the problem is not with vnc but I broke something with gnome. The log of the vnc is as follows:
Any ideas?Code:Xvnc Free Edition 4.1.2 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Underlying X server release 70101000, The X.Org Foundation Tue Jun 3 17:47:04 2008 vncext: VNC extension running! vncext: Listening for VNC connections on port 7302 vncext: Listening for HTTP connections on port 7202 vncext: created VNC server for screen 0 Could not init font path element /usr/share/X11/fonts/OTF, removing from list! Could not init font path element /usr/share/X11/fonts/CID/, removing from list! localuser:amac.herdagdelen being added to access control list No profile for user 'amac.herdagdelen' found SESSION_MANAGER=local/remoteserver:/tmp/.ICE-unix/31504
- 06-03-2008 #3Just Joined!
- Join Date
- Jun 2008
- Posts
- 4
Additional info:
Although with the gnome configuration I get the grey screen with cross pointer, when I run "top -b | grep gnome" in the command shell, I get the following output:
Gnome starts but somehow it is not bound to my display...Code:32420 myuser 18 0 22316 6160 5244 S 0 0.2 0:00.03 gnome-session 32456 myuser 15 0 2536 580 476 S 0 0.0 0:00.00 gnome-keyring-d 32458 myuser 18 0 33380 6656 5504 S 0 0.2 0:00.03 gnome-settings- 32476 myuser 18 0 15912 2024 1256 S 0 0.1 0:00.00 gnome-screensav
- 06-03-2008 #4Just Joined!
- Join Date
- Jun 2008
- Posts
- 4
I kind of saved the day but still I really don't the nature of the problem.
There was a process named "Bonobo activation", I killed it. I deleted .Xauthority file, killed all gnome process. Then started anew. Now it works.
Could anybody tell us what was going on here?
Amac


Reply With Quote