Oh well, that was worth a try ;) The only other thing that I can think of is that you have some KDE configuration lying around that is possibly effecting how QT (the toolkit used in VirtualBox) is behaving...
Darren. Rich Teer wrote: > On Wed, 5 Mar 2008, Darren Kenny wrote: > >> That screenshot is very useful :) > > Good! > >> The last time I saw something like that was using Xsun or an old version of >> Xvnc. In both cases the issue was that I was running an Xserver that didn't >> support the XRENDER extension. >> >> Could you verify this by running: >> >> /usr/openwin/bin/xdpyinfo | grep RENDER > > Here it is: > > rich at marrakesh4150# /usr/openwin/bin/xdpyinfo | grep RENDER > RENDER > > In all the cases I've tried this, I'm directly logged into the local console. > >> If you are running on x86/amd64 it is usually much better to use the Xorg >> xserver since that is where the main focus is w.r.t. the latest X extensions. > > AFAIK, I'm using the Xorg server. I'm using a vanilla Nevada install. > I assume this means I'm running Xorg's server: > > rich at marrakesh4152# ps -ef | grep X > rich 1795 1400 1 Feb 10 ? 285:07 /usr/X11/bin/Xorg :0 > -depth 24 -nolisten tcp -nobanner [...] > > ? >
