Originally Posted: 2010-12-15
Reprint to CU at: 2012-07-21
In the environment of the safety test, the ubuntu10.10 was installed on VMware (used by the university when it was first used as if it was a 6 series). After installation, you want to use Remote Desktop control, after all, see the interface on VMware is relatively small, not very convenient.
Using VNC, please see http://www.realvnc.com/for more information.
After installing VNC and doing some configuration (VNC using gnome-seeion boot), two questions were used:
1. From the remote use Vncviewer connection, there is only one terminal, no graphical interface, there is "could not acquire name on session bus" words;
2. The above problem is resolved, after VNC, the key "D" cannot be used.
Find a solution from the Internet and record it for later use.
1. Install on Ubuntu:
sudo apt-get install Vnc4server
2. Start Vncserver:
Vncserver
The first boot will require a password, which can be modified later using VNCPASSWD;
See New ' ****:1 ' Desktop is ****:1 (* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * on behalf of host name
At this time can be remotely connected, note the above number "1", the terminal number, using the Web Landing is http://ip:5901, using vncviewer namely ip:1;
3. Turn off VNC:
Vncserver-kill:1
Notice that there are spaces after kill.
4. The graphical interface called Gnome-session that modifies the VNC startup in CentOS would have been done, but unfortunately it happened, as described in the question. The workaround is as follows (from the network) to modify the VNC boot file:
To back up the original Xstartup file:
MV ~/.vnc/xstartup ~/.vnc/xstartup.bak
Copy a new Xstartup file:
Cp/etc/x11/xsession ~/.vnc/xstartup
(There is one more way to do the above two steps:
sudo gedit ~/.vnc/xstartup
Original file content:
#!/bin/sh
# Uncomment the following-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
vnccon**-iconic &
X-terminal-emulator-geometry 80x24+10+10-ls-title "$VNCDESKTOP Desktop" &
X-window-manager &
After modification:
#!/bin/sh
# Uncomment the following-lines for normal desktop:
Unset Session_manager
EXEC/ETC/X11/XINIT/XINITRC (can also be modified to/etc/x11/xsession, XINITRC Remote Desktop may be a snowflake if no permissions are modified)
[-x/etc/vnc/xstartup] && Exec/etc/vnc/xstartup
[-R $HOME/. Xresources] && Xrdb $HOME/. Xresources
#xsetroot-solid Grey
#vnccon * *-iconic &
#x-terminal-emulator-geometry 80x24+10+10-ls-title "$VNCDESKTOP Desktop" &
#x-window-manager &
Modify the/etc/x11/xinit/xinitrc file permissions to enable the executable:
sudo chmod 755/etc/x11/xinit/xinitrc
)
5. The first problem is resolved after the above configuration, the second problem:
Ubuntu 10.10 has a definition of the Windows key, in which is defined as Super key, when the user in the VNC under the letter "D", will be wrong to return to the desktop as a shortcut to the "D" can not be entered, at this time to modify the shortcut key mode to avoid this bug, a new terminal opened, In the inside input:
Gconf-editor
Pop Up the dialog box, go to "Show desktop" in "Apps->metacity->global keybingdings", and change its default value <super>d to <ctl>d.
ubuntu10.10 installation using VNC