vncconfig is started automatically by 'vnc4server', but if a custom startup script exists in '$HOME/.vnc/xstartup' that script will be executed. If 'xstartup' has been altered to start an X server (rather than just xterm), vncconfig doesn't get a chance to run:
#!/bin/bash # Uncomment the following two lines for normal desktop: unset SESSION_MANAGER exec sh /etc/X11/xinit/xinitrc # # Statements below never get executed # [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources xsetroot -solid grey vncconfig -iconic & #x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & x-window-manager & I've been running vncserver for a couple of years and just noticed this is why I could never get clipboard access to work even though the options in the viewer (F8) have all the items pertaining to clipboard checked. I just thought clipboard functionality was broken. >From 'man vncconfig': "Note that without a running instance of vncconfig there will be no clipboard support." So, while it is documented, in certain instances the user would have to be thinking about manually running it to know it was needed. In my case, since after executing 'xinitrc' I no longer have control, I added 'vncconfig -nowin &' to the GDM startup applications. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
