Comment 20 for bug 738330

I think the actual issue needs investigations.

First of all I can confirm unity in my natty guest (with virtualbox-ose-guest-x11 installed) stopped working in my VirtualBox (4.0.4 on ubuntu 10.10 host) after the update to xserver 1.10 in guest. Instead compiz is still able to run in natty guest (maybe software rendering? see below)

## Issues in xorg launch ##

(II) AIGLX: Trying DRI driver /usr/lib/dri/vboxvideo_dri.so
(II) Next line is added to allow vboxvideo_drv.so to appear as whitelisted driver
(II) The file referenced, is *NOT* loaded
(II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
(II) AIGLX: vboxvideo does not export required DRI extension
(II) AIGLX: Trying DRI driver /usr/lib/dri-alternates/vboxvideo_dri.so
(II) AIGLX: dlopen of /usr/lib/dri-alternates/vboxvideo_dri.so failed (/usr/lib/dri-alternates/vboxvideo_dri.so: cannot open shared object file: No such file or directory)
(II) AIGLX: Trying DRI driver /usr/lib32/dri/vboxvideo_dri.so
(II) AIGLX: dlopen of /usr/lib32/dri/vboxvideo_dri.so failed (/usr/lib32/dri/vboxvideo_dri.so: cannot open shared object file: No such file or directory)
(II) AIGLX: Trying DRI driver /usr/lib32/dri-alternates/vboxvideo_dri.so
(II) AIGLX: dlopen of /usr/lib32/dri-alternates/vboxvideo_dri.so failed (/usr/lib32/dri-alternates/vboxvideo_dri.so: cannot open shared object file: No such file or directory)
(EE) AIGLX: reverting to software rendering
(II) AIGLX: Trying DRI driver /usr/lib/dri/swrast_dri.so
(II) AIGLX: Loaded and initialized swrast
(II) GLX: Initialized DRISWRAST GL provider for screen 0

So, it seems vboxvideo_dri has issues ("does not export required DRI extension"). I suspect the only option is wait from update from upstream, but of course "no bug, no fix" :) Someone could search for existing bug or maybe file a new one -- quick search on http://www.virtualbox.org/wiki/Bugtracker showed nothing related.

## Crash on unity startup ##

When I log in a "classic" session and I try to manually launch unity, I've

Backend : gconf
Integration : true
Profile : unity
Adding plugins
Initializing core options...done
Initializing bailer options...done
Initializing detection options...done
Initializing composite options...done
OpenGL Warning: No pincher, please call crStateSetCurrentPointers() in your SPU
Initializing opengl options...done
OpenGL Info: Using XSHM for GLX_EXT_texture_from_pixmap
Initializing decor options...done
Initializing mousepoll options...done
Initializing vpswitch options...done
Initializing animation options...done
Initializing snap options...done
Initializing expo options...done
Initializing move options...done
Initializing place options...done
Initializing grid options...done
Initializing gnomecompat options...done
Initializing wall options...done
Initializing ezoom options...done
Initializing workarounds options...done
Initializing staticswitcher options...done
Initializing resize options...done
Initializing fade options...done
Initializing scale options...done
Initializing session options...done
** (<unknown>:1671): DEBUG: Unity accessibility initialization
Initializing unityshell options...done
** (<unknown>:1671): DEBUG: MaximizeIfBigEnough: Gnome-terminal window size doesn't fit
** (<unknown>:1671): DEBUG: PlaceEntry: Applicazioni
** (<unknown>:1671): DEBUG: PlaceEntry: Comandi
** (<unknown>:1671): DEBUG: PlaceEntry: File e cartelle

(<unknown>:1671): libindicator-WARNING **: Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'.
terminate called after throwing an instance of 'std::bad_alloc'
  what(): std::bad_alloc
Aborted (core dumped)

A quick and dirty "gdb unity" showed me that /usr/bin/unity is not a binary file, so by now I stopped here. But the question is: is the process termination a direct consequence of previous vboxvideo_dri lacking?