On Mon, Mar 26, 2012 at 2:26 PM, Jeremy Wellner < [email protected]> wrote:
> I had occasion to try and VNC into my desktop over the weekend and needed > to get it setup after the SL 6.2 upgrade and what happens is that once the > VNC session is created it gives me white noise on one of my physical > monitors and the other one goes dark and the machine freezes requiring a > hard reboot since I can't even terminal into it to restart nicely. I > needed to get VNC on the local console working and was hard pressed to find > documentation for doing that on SL 6 or better. > > Never really used tigervnc. I used tightvnc from Repoforge, which seemed to work well. Can you test that? Also, there's a really useful tool called "NX" from www.nomachine.com, and some free-as-in-speech rebuilds of their odlder GPL source called freenx available at atrpms. The NoMachine vresion is really a quite good, much better than VNC, and handles reconnecting to the same session quite well. It's much more responsive on a slow connection, has much better security models than VNC, and I frankly wish that KVM over IP solutions used this instead of the obviously poorly concealed VNC most of them are built from. > Things I modified.... > gtk-vnc > 0.3.10-3.el6<http://127.0.0.1:10000/software/edit_pack.cgi?search=vnc&package=gtk%2Dvnc&version=0%2E3%2E10%2D3%2Eel6> > Development/LibrariesA GTK widget for VNC clients gtk-vnc-python > 0.3.10-3.el6<http://127.0.0.1:10000/software/edit_pack.cgi?search=vnc&package=gtk%2Dvnc%2Dpython&version=0%2E3%2E10%2D3%2Eel6> > Development/LibrariesPython bindings for the gtk-vnc library libvncserver > 0.9.7-4.el6<http://127.0.0.1:10000/software/edit_pack.cgi?search=vnc&package=libvncserver&version=0%2E9%2E7%2D4%2Eel6> > System > Environment/LibrariesLibrary to make writing a vnc server easy tigervnc > 1.0.90-0.17.20110314svn4359.el6<http://127.0.0.1:10000/software/edit_pack.cgi?search=vnc&package=tigervnc&version=1%2E0%2E90%2D0%2E17%2E20110314svn4359%2Eel6> > User > Interface/DesktopsA TigerVNC remote display system tigervnc-server > 1.0.90-0.17.20110314svn4359.el6<http://127.0.0.1:10000/software/edit_pack.cgi?search=vnc&package=tigervnc%2Dserver&version=1%2E0%2E90%2D0%2E17%2E20110314svn4359%2Eel6> > User > Interface/XA TigerVNC server tigervnc-server-applet > 1.0.90-0.17.20110314svn4359.el6<http://127.0.0.1:10000/software/edit_pack.cgi?search=vnc&package=tigervnc%2Dserver%2Dapplet&version=1%2E0%2E90%2D0%2E17%2E20110314svn4359%2Eel6> > User > Interface/XJava TigerVNC viewer applet for TigerVNC server > tigervnc-server-module > 1.0.90-0.17.20110314svn4359.el6<http://127.0.0.1:10000/software/edit_pack.cgi?search=vnc&package=tigervnc%2Dserver%2Dmodule&version=1%2E0%2E90%2D0%2E17%2E20110314svn4359%2Eel6> > User > Interface/XTigerVNC module to Xorg x11vnc > 0.9.13-1.el6<http://127.0.0.1:10000/software/edit_pack.cgi?search=vnc&package=x11vnc&version=0%2E9%2E13%2D1%2Eel6> > User > Interface/XVNC server for the current X11 session > > Does it blow up if you run it from a remote X server? Or if you back out that x11vnc, which looks like the out of date one on EPEL rather than the more recent one on Repoforge? > [root@cormorant ladmin]# cat /etc/X11/xorg.conf > Section "ServerLayout" > Identifier "aticonfig Layout" > Screen 0 "aticonfig-Screen[0]-0" 0 0 > EndSection > > Section "Files" > ModulePath "/usr/lib64/xorg/modules/extensions/fglrx" > ModulePath "/usr/lib64/xorg/modules" > EndSection > > Section "Module" > Load "vnc" > EndSection > > Section "Monitor" > Identifier "aticonfig-Monitor[0]-0" > Option "VendorName" "ATI Proprietary Driver" > Option "ModelName" "Generic Autodetecting Monitor" > Option "DPMS" "true" > EndSection > > Section "Monitor" > Identifier "0-DFP1" > Option "VendorName" "ATI Proprietary Driver" > Option "ModelName" "Generic Autodetecting Monitor" > Option "DPMS" "true" > Option "PreferredMode" "1920x1080" > Option "TargetRefresh" "60" > Option "Position" "0 0" > Option "Rotate" "normal" > Option "Disable" "false" > EndSection > > Section "Monitor" > Identifier "0-DFP2" > Option "VendorName" "ATI Proprietary Driver" > Option "ModelName" "Generic Autodetecting Monitor" > Option "DPMS" "true" > Option "PreferredMode" "1920x1080" > Option "TargetRefresh" "60" > Option "Position" "1920 0" > Option "Rotate" "normal" > Option "Disable" "false" > EndSection > > Section "Device" > Identifier "aticonfig-Device[0]-0" > Driver "fglrx" > Option "Monitor-DFP1" "0-DFP1" > Option "Monitor-DFP2" "0-DFP2" > BusID "PCI:2:0:0" > EndSection > > Section "Screen" > Identifier "aticonfig-Screen[0]-0" > Device "aticonfig-Device[0]-0" > DefaultDepth 24 > SubSection "Display" > Viewport 0 0 > Virtual 3840 1920 > Depth 24 > EndSubSection > Option "SecurityTypes" "VncAuth" > Option "UserPasswdVerifier" "VncAuth" > Option "PasswordFile" "/root/.vnc/passwd" > EndSection > > # The VNCSERVERS variable is a list of display:user pairs. > # > # Uncomment the lines below to start a VNC server on display :2 > # as my 'myusername' (adjust this to your own). You will also > # need to set a VNC password; run 'man vncpasswd' to see how > # to do that. > # > # DO NOT RUN THIS SERVICE if your local area network is > # untrusted! For a secure way of using VNC, see this URL: > # http://kbase.redhat.com/faq/docs/DOC-7028 > > # Use "-nolisten tcp" to prevent X connections to your VNC server via TCP. > > # Use "-localhost" to prevent remote VNC clients connecting except when > # doing so through a secure tunnel. See the "-via" option in the > # `man vncviewer' manual page. > > # VNCSERVERS="2:myusername" > # VNCSERVERARGS[2]="-geometry 800x600 -nolisten tcp -localhost" > > /var/log/messages from relevant time: > Mar 26 10:42:21 cormorant avahi-daemon[2010]: Invalid query packet. > Mar 26 10:42:25 cormorant kernel: [fglrx] IRQ 55 Disabled > Mar 26 10:42:25 cormorant gnome-keyring-daemon[3111]: dbus failure > unregistering from session: Connection is closed > Mar 26 10:42:25 cormorant gnome-keyring-daemon[3111]: dbus failure > unregistering from session: Connection is closed > Mar 26 10:42:25 cormorant NetworkManager[1998]: <error> > [1332783745.676479] [nm-manager.c:1360] user_proxy_init(): could not init > user settings proxy: (3) Could not get owner of name > 'org.freedesktop.NetworkManagerUserSettings': no such name > Mar 26 10:44:07 cormorant kernel: imklog 4.6.2, log source = /proc/kmsg > started. > > Any help would be appreciated! > -- > Jeremy Wellner > Technology Group > Stanwood-Camano School District > [email protected] > Internal: x4357 > External: 360-629-1205 > Cell: 425-418-4972 > >
