With Fedora 16 and KDE, or Ubuntu 11.10 and Unity, and Parallels Tools installed, everything works right on current Lion in full screen mode. You fire up the VM, it pops up on a Lion full screen window, and voila. You log in, and it fills the screen with your X11 stuff.
With Fedora 16 *or* Ubuntu 11.10 while running Gnome 3 (Gnome Shell), on the other hand, it basically creates a little 640x480 subset of the screen once you log in and draws everything there. If you pop out of full screen mode then back in, *then* it fills the screen with your desktop.
My guess is a race condition wherein Gnome Shell is asking for the screen geometry from X11 before Parallels Tools has determined it (thus why it works *after* Gnome Shell is up and going when the screen-size-change notification system via DBUS is being used instead), but that's just a guess. The work around is pretty easy -- just pop out of full screen, pop back into full screen -- but annoying.
Anybody else seeing this behavior? Note that I have a *very* fast Macbook Pro -- 750gb 7200 rpm drive, 2.4ghz Core I7, 16GB RAM, etc. -- so it may be that my system is simply fast enough to expose a race condition that doesn't occur on slower computers?
With Fedora 16 *or* Ubuntu 11.10 while running Gnome 3 (Gnome Shell), on the other hand, it basically creates a little 640x480 subset of the screen once you log in and draws everything there. If you pop out of full screen mode then back in, *then* it fills the screen with your desktop.
My guess is a race condition wherein Gnome Shell is asking for the screen geometry from X11 before Parallels Tools has determined it (thus why it works *after* Gnome Shell is up and going when the screen-size-change notification system via DBUS is being used instead), but that's just a guess. The work around is pretty easy -- just pop out of full screen, pop back into full screen -- but annoying.
Anybody else seeing this behavior? Note that I have a *very* fast Macbook Pro -- 750gb 7200 rpm drive, 2.4ghz Core I7, 16GB RAM, etc. -- so it may be that my system is simply fast enough to expose a race condition that doesn't occur on slower computers?