On Thu, Apr 09, 2009 at 11:25:25AM -0500, Mike Hinz wrote: > All, > > > > I spent some time this am, doing some more testing on what exactly is > happening with regards to desktop switching and with client side problems. > > > > I think I've determined the following: > > > > The new xstartup seems to work correctly, with the following comment: In > order to get this to work within a VM, I had to install and use the > switchdesk utility and then had to reboot the VM. It is not sufficient to > log out and log back in, while selecting the user's desktop environment at > that time. I suspect that the same result could be done by using switchdesk > and then restarting X, but within a VM, that is tricky as what happened when > I tried that, is that I killed X on the physical machine and restarted it. > I think the only way is to reboot the VM to force the change. Using > switchdesk and rebooting between changes, I was able to utilize the gnome, > kde, and icewm desktops. I also tried the method suggested and commented > out the new code and added the lines to startup icewm as we've done in the > past. This also worked, so it appears that either approach works. However, > users need to understand that just changing the desktop selection at login > is not sufficient.
Hm, odd. Could you please send me off-list your xstartup file? (I'm affraid that mailing list will discard all attachments). I have this in my xstartup and startup of light-weight desktop is OK. #!/bin/sh vncconfig -iconic & [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources xsetroot -solid grey twm & > Secondly, I've determined that there seems to be a problem now when > accessing the tigervnc server from the latest tightvnc client, which I think > is v1.3.10. There is very odd screen corruption using that version. I did > successfully use the older vncview that is installed with Fedora 10. That > is identified as vnc viewr free edition 4.13. build Jan 26, 2009 by RealVNC. > I also installed the latest tigervnc viewer in Fedora 10, identified as > tigervnc viewer v0.0.90 Build April 7, 2009 16:01:28. Both of these clients > worked successfully. The latest tightvnc viewer works fine on my machine. Could you please tell us which architecture are you running Xvnc on? Also attach Xvnc log file (from $HOME/.vnc/*log) when you connect via tightvnc client. > So there now appears to be some compatibility issues between clients. In > the earlier build of tigervnc server, the tightvnc client did work ok. > > > > I'm assuming that you're planning to release a windows based client for > tighervnc?? Definitely. Regards, Adam -- Adam Tkac, Red Hat, Inc. ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Tigervnc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tigervnc-users
