I'm not sure if I understand the problem. You are correct that there is no .Xclients or .Xclients-default in /root by default, but the default xstartup will still work. It will simply load the default window manager (Gnome.) If you run switchdesk, then .Xclients and .Xclients-default are created, allowing you to select KDE or ICE WM. I just tried this, and it works fine for me.
[email protected] wrote: > OK gents, I've pretty thoroughly looked at this and can report the following: > > The issue I was having was that one of the vnc sessions I was creating was > for root, so i had the following in /etc/sysconfig/vncservers > 'VNCSERVERS="1:root". The issue with this appears to be that there is no > .Xclients or .Xclients-default created in /root, although a .vnc directory is > created with all the requisite bits in it. > > If you create something like this in /etc/sysconfig/vncservers > 'VNCSERVERS="2:mike" then in /home/mike, the requisite .Xclients and > .Xclients-default files are created and everything works just fine. > > So one issue is to either document that you shouldn't attempt to create a vnc > session for root (probably a bad idea anyway) or change the behavior so that > a vnc session for root can be supported. > > Note that for the normal user I'm using the completely standard default > xstartup configuration and it now just works, PROVIDED that you use the > switchdesk utility. DRC's explanation of why this works appears to be > exactly correct. I am heavily in favor of using EXACTLY this behavior as > it's very handy for us to have a full KDE desktop while at the physical > console, but to have lean desktop, such as icewm, when working remotely on > the same machine. This is particularly nice with all the VMs we run. > > I still note one issue though, although it doesn't appear to affect the > behavior of vnc. Please note the following when I restart the server: > > [r...@vmhost3 .vnc]# service vncserver restart > Shutting down VNC server: 2:mike [ OK ] > Starting VNC server: 2:mike xauth: (stdin):1: bad display name "vmhost3:2" > in "add" command > > New 'vmhost3:2 (mike)' desktop is vmhost3:2 > > Starting applications specified in /home/mike/.vnc/xstartup > Log file is /home/mike/.vnc/vmhost3:2.log > > [ OK ] > [r...@vmhost3 .vnc]# > > The below is the log file contents. Sorry in advance for the length: > > o...@vmhost3 .vnc]# cat vmhost3:1.log > > Xvnc TigerVNC 0.0.90 - built Apr 30 2009 05:02:28 > Copyright (C) 2002-2005 RealVNC Ltd. > Copyright (C) 2000-2006 Constantin Kaplinsky > Copyright (C) 2004-2009 Peter Astrand for Cendio AB > See http://www.tigervnc.org for information on TigerVNC. > Underlying X server release 10601000, > > > Thu May 14 10:42:31 2009 > vncext: VNC extension running! > vncext: Listening for VNC connections on port 5901 > vncext: created VNC server for screen 0 > imsettings information > ========================== > Is DBus enabled: yes > Is imsettings enabled: yes > Is GTK+ supported: no > Is Qt supported: no > DESKTOP_SESSION: > DISABLE_IMSETTINGS: > IMSETTINGS_DISABLE_DESKTOP_CHECK: > DBUS_SESSION_BUS_ADDRESS: > unix:abstract=/tmp/dbus-jb34MS65Qz,guid=a0641c34cdb8cc238237af0d4a0c3bea > > GTK_IM_MODULE: gtk-im-context-simple > > QT_IM_MODULE: xim > > XMODIFIERS: @im=none > > IMSETTINGS_MODULE: none > > IMSETTINGS_INTEGRATE_DESKTOP: yes > > > gnome-session[5779]: WARNING: keycode1 not existant > gnome-session[5779]: WARNING: keycode2 not existant > GNOME_KEYRING_SOCKET=/tmp/keyring-jymY0d/socket > SSH_AUTH_SOCK=/tmp/keyring-jymY0d/socket.ssh > GNOME_KEYRING_PID=5813 > > ** (gnome-settings-daemon:5812): WARNING **: Connection failed > > ** (gnome-settings-daemon:5812): WARNING **: XKB extension not available > > ** (gnome-settings-daemon:5812): WARNING **: Neither XKeyboard not Xfree86's > keyboard extensions are available, > > no way to support keyboard autorepeat rate settings > > Window manager warning: Failed to read saved session file > /root/.config/metacity/sessions/108d6b216cd3bc127c12423157553146500000057790023.ms: > Failed to open file > '/root/.config/metacity/sessions/108d6b216cd3bc127c12423157553146500000057790023.ms': > No such file or directory > Window manager warning: Log level 32: could not find XKB extension. > The program 'gnome-settings-daemon' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadWindow (invalid Window parameter)'. > (Details: serial 313 error_code 3 request_code 20 minor_code 0) > (Note to programmers: normally, X errors are reported asynchronously; > that is, you will receive the error a while after causing it. > To debug your program, run it with the --sync command line > option to change this behavior. You can then get a meaningful > backtrace from your debugger if you break on the gdk_x_error() function.) > Failed to play sound: Not available > > ** (gnome-volume-control-applet:5847): WARNING **: Connection failed > > ** (gnome-user-share:5853): WARNING **: gnome-user-share cannot be started as > root for security reasons. > > ** (nm-applet:5857): WARNING **: <WARN> applet_dbus_manager_start_service(): > Could not acquire the NetworkManagerUserSettings service as it is already > taken. Return: 3 > > W: main.c: This program is not intended to be run as root (unless --system is > specified). > Initializing nautilus-gdu extension > Xlib: extension "DPMS" missing on display ":1.0". > > ** (nautilus:5831): WARNING **: Unable to add monitor: Not supported > > Thu May 14 10:44:17 2009 > Connections: accepted: 192.168.3.111::54836 > SConnection: Client needs protocol version 3.8 > SConnection: Client requests security type VncAuth(2) > > Thu May 14 10:44:20 2009 > VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian > rgb888 > VNCSConnST: Client pixel format depth 24 (32bpp) little-endian rgb888 > > Thu May 14 10:44:26 2009 > Connections: closed: 192.168.3.111::54836 (Clean disconnection) > SMsgWriter: framebuffer updates 7 > SMsgWriter: Tight rects 36, bytes 334669 > SMsgWriter: raw bytes equivalent 5212312, compression ratio 15.574529 > [r...@vmhost3 .vnc]# > > > Please let me know if you need any more info on this. Thanks very much! > > > > Regards, > > > > Mike Hinz > President > YR20 > 1718 Fry Road, Suite 440 > Houston, TX 77084 > [email protected] > 832-225-1293 (o) > 713-594-3095 (m) > 832-550-2657 (f) > > > -----Original Message----- > From: "DRC" <[email protected]> > Sent: Tuesday, May 12, 2009 2:21pm > To: "Adam Tkac" <[email protected]> > Cc: [email protected], [email protected] > Subject: Re: [Tigervnc-users] tigervnc 0.90-0.7 issues > > Doing 'switchdesk icewm' and then restarting the VNC session seems to > work fine for me. The portion of the vncserver code that creates the > xstartup script shouldn't have changed between 0.90-0.7 and the previous > release. > > As Mike observed, choosing a new session in KDM or GDM doesn't affect > the type of session TigerVNC chooses. That's because KDM and GDM in > Fedora 11 store the session preference in $HOME/.dmrc, whereas TigerVNC > and SwitchDesk use $HOME/.Xclients-default instead. A possible > enhancement to TigerVNC would be to make the default xstartup script > parse $HOME/.dmrc, if it exists. However, I'm with Mike-- I like the > accidental feature of being able to specify the local and VNC desktops > separately. > > Mike, > I'm not sure why it's not working on your system. Do the > $HOME/.Xclients and $HOME/.Xclients-default scripts look OK? > > Adam Tkac wrote: > >> Hm, have you tried if same xstartup worked with older version of >> tigervnc? I think it didn't work as well. >> >> AFAIK you have to run icewm via "icewm-session" command: >> >> $ cat ~/.vnc/xstartup >> ... >> #xsetroot -solid grey >> #xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & >> #twm & >> icewm-session & >> >> After that everything should work fine. >> >> Regards, Adam >> >> > > > ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Tigervnc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tigervnc-users
