VNC-Server Vino Mini Guide

[marcrblevins]

Can you focus on 192.168.123.100:3, the regular user first, get that working, then worry about root later. We usually don't login as root ideally.

[Blisk]

here is mine, but when I use your I have the same problem.
No mather if I use 192.168.123.100:3

#!/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 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" -e ./menu &
twm &

[marcrblevins]

Did you try for :3, same glitch?

[Blisk]

Originally Posted by marcrblevins

Did you try for :3, same glitch?

yes it is the same problem.

[marcrblevins]

Can you login to the console as damjan first? Don't do remote yet. Select your favorite DE, KDE or Gnome session. Log off. Go to your remote computer and give vnc a try.

[Blisk]

Originally Posted by marcrblevins

Can you login to the console as damjan first? Don't do remote yet. Select your favorite DE, KDE or Gnome session. Log off. Go to your remote computer and give vnc a try.

I did that with root login, and it works OK. But now I cannot test until I get home

I will

[briantan]

Originally Posted by Blisk

When I log in with vnc like 192.168.123.100:1 I get only xwindows there is only terminal windows and vnc setting window. Not like when I log in on server where in gnome desktop gui.
I can not click anything because there is no menu.

As indicated in the guide, F9/VNC-server/Gnome is still problematic. Slow, sluggish, unresponsive. Wait "a lot" longer and more stuff "may" kick in, such as gnome-panel, gnome window manager.

As suggested in the guide, use KDE or XFCE for F9.

For KDE, create/edit /etc/sysconfig/desktop:

DESKTOP=KDE

Procedure for XFCE is detailed in the guide.

@marcrblevins, please note that any lines after "exec" will not have any effect in the script, as "exec" replaces the current shell. Session will end when "exec" process exit.

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

# these lines will not have any effect after an exec.
[ -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" -e ./menu &
twm &

[briantan]

Blisk, come to think of it, since your vino is working, use that as interim solution for gnome.

[marcrblevins]

@marcrblevins, please note that any lines after "exec" will not have any effect in the script, as "exec" replaces the current shell. Session will end when "exec" process exit.

That is what I expected, it should stop at exec, but thinking Blisk is still running the twm & line.

Is Blisk issue solved?

[briantan]

Originally Posted by marcrblevins

Is Blisk issue solved?

Mystery to me.

We can just assume it is if nothing is heard.

[lovetide]

Is there a config file for Vino ?

[briantan]

Originally Posted by lovetide

Is there a config file for Vino ?

I'm not familiar with vino's anatomy. However

$ rpm -ql vino

reveals a vino-preferences dialog

/usr/share/applications/gnome-vino-preferences.desktop

and looking for changes after executing vino-preferences, configuration is probably stored somewhere in

~/.gconfd/saved_state
~/.gconf/desktop/gnome/remote_access/%gconf.xml
~/.gnome2/session

[lovetide]

Originally Posted by briantan

I'm not familiar with vino's anatomy. However

$ rpm -ql vino

reveals a vino-preferences dialog

/usr/share/applications/gnome-vino-preferences.desktop

and looking for changes after executing vino-preferences, configuration is probably stored somewhere in

~/.gconfd/saved_state
~/.gconf/desktop/gnome/remote_access/%gconf.xml
~/.gnome2/session

Thank you biantan, i think it could be ~/.gconf/desktop/gnome/remote_access/%gconf.xml

[root@YH4F-PRINTER2 ~]# cat ~/.gconf/desktop/gnome/remote_access/%gconf.xml

<?xml version="1.0"?>
<gconf>
        <entry name="prompt_enabled" mtime="1215595946" type="bool" value="false">
        </entry>
        <entry name="enabled" mtime="1215595945" type="bool" value="true">
        </entry>
</gconf>

xxxxxxxxxx

[tharizdun]

Thank you for the excellent guide. I've used this with F9/gdm with no problems with or without vino.

No one else had the following problem (which is now corrected), so I'll assume that everyone else has better reading skills than me

My version of vino had this default comment:
# VNCSERVERARGS[2]="-geometry 800x600 -nolisten tcp -nohttpd -localhost"

I edited that comment rather than retyping per your notes and silly me didn't notice the "-nolisten tcp" or "-localhost" which basically prevented remote systems from binding to 5901.

I'm only posting that in case anyone made the same mistake I did.



FYI - I get this strange message when attempting to determine the version of gdm:

[root@revanent ~]# /usr/sbin/gdm --version

** (gdm-binary:5805): WARNING **: Failed to acquire org.gnome.DisplayManager

** (gdm-binary:5805): WARNING **: Could not acquire name; bailing out
[root@revanent ~]#

so I'll include this instead for anyone also trying to run gdm/vnc

[root@revanent ~]# yum list | grep gdm
gdm.i386 1:2.22.0-10.fc9 installed
gdm-user-switch-applet.i386 1:2.22.0-10.fc9 installed
bluecurve-gdm-theme.noarch 1.0.0-1.fc8 fedora
fedorabubbles-gdm-theme.noarch 1.0.0-1.fc8 fedora
fedoradna-gdm-theme.noarch 1.0.0-1.fc8 fedora
fedoraflyinghigh-gdm-theme.noarch 1.0.0-1.fc8 fedora
fedorainfinity-gdm-theme.noarch 8.0.1-1.fc8 fedora
gdmap.i386 0.7.5-6.fc6 fedora
[root@revanent ~]#