Today's Natty update means no guest additions in virtualbox

Bug #738330 reported by Sam Illingworth
124
This bug affects 21 people
Affects Status Importance Assigned to Milestone
virtualbox-guest-additions (Ubuntu)
Invalid
High
Unassigned
virtualbox-ose (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

----
Summary: After the updates installed today on the guest machine, (3/19/11) the guest-additions in virtualbox-ose will not work on a natty guest install.
----

I'm running Ubuntu in Virtual Box on a Mac host and today's update has broken 3D. Normally every time there's an update I restart Ubuntu and see a 2D interface, but then I re-install the guest additions and restart and see a 3D interface, but no such look today.

I imagine you already know why this is (some config file listing supported hardware or something?), but if not I'm happy to grab you any diagnostic info I can (if you give me instructions).

Tags: natty
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

I'm running it in real hardware fully updated and everythings is ok.
Try to delete every compiz related files and folder in your /home then from synaptic mark all compiz related packages for reinstallation.
hope it works.
Fabio

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
RedSingularity (redsingularity) wrote :

I can confirm this on my system. After the update today, I can no longer use the guest-additions in the natty guest OS. Even after reinstalling the guest-additions, natty still wont recognize them and therefore there is no 3D, or any other feature that comes with the additions.

Sam, run the following command to get your vbox version info:

(Run these commands from your HOST machine)
apt-cache policy virtualbox-ose

Also run:

apport-collect 738330

affects: ubuntu → virtualbox-ose (Ubuntu)
Changed in virtualbox-ose (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Sam Illingworth (mazz0) wrote :

I can't run those commands, RedSingularity, am on an OS X host, but I'm using virtual box 4.0.4 r70112. Also, you're right - seamless and auto-resize aren't working either, so the problem is that Guest Additions don't work in the newest build.

Could the bug title be changed to reflect this?

Revision history for this message
RedSingularity (redsingularity) wrote : Re: Today's Natty update means no guest additions in virtual box

Title changed. Can you confirm what version of virtualbox and guest additions you are using? Thanks.

summary: - Today's Natty update means no 3D in virtual box
+ Today's Natty update means no guest additions in virtual box
Revision history for this message
RedSingularity (redsingularity) wrote :

Sorry Sam, I see you are using Vbox 4.0.4

Can you confirm you are using guest-additions 4.0.4 as well?

summary: - Today's Natty update means no guest additions in virtual box
+ Today's Natty update means no guest additions in virtualbox
Changed in virtualbox-guest-additions (Ubuntu):
status: New → Confirmed
description: updated
Revision history for this message
RedSingularity (redsingularity) wrote :

Attaching my xorg.0.log file from the guest machine.

Revision history for this message
Andreas Moog (ampelbein) wrote :

The problem is in the guest-additions, the video driver needs to be updated for the recent ABI change in X (9 -> 10):

[ 5.900] (EE) module ABI major version (9) doesn't match the server's version (10)
[ 5.900] (II) UnloadModule: "vboxvideo"
[ 5.900] (II) Unloading vboxvideo
[ 5.901] (EE) Failed to load module "vboxvideo" (module requirement mismatch, 0)

Changed in virtualbox-ose (Ubuntu):
status: Confirmed → Invalid
Changed in virtualbox-guest-additions (Ubuntu):
importance: Undecided → High
status: Confirmed → Triaged
Revision history for this message
Felix Geyer (debfx) wrote :

On an Ubuntu guest system you should always use the virtualbox-ose-guest-x11 package instead of installing the additions through the iso image.

Revision history for this message
Sam Illingworth (mazz0) wrote :

Yep, I am using 4.0.4 guest additions too.

@Felix - that in the repos is it?

Revision history for this message
Sam Illingworth (mazz0) wrote :

@Felix - I've found a package called virtualbox-guest-additions in the software center, but it doesn't sound like that's what you mean:

"This package provides an iso image which contains the guest additions for Linux, Solaris and Windows to be installed on the host system. The guest systems then can mount the iso and install the guest additions from there."

so that sounds like you're supposed to install it on the host. I can't find the package virtualbox-ose-guest-x11 in the software center but it installs from the command line (is there a reason that's not in the software center?).

So, after installing that, now I have the guest addition options like autoresize and seamless, but now my desktop has no launcher or panel, and if I try to start compiz from the terminal:

sam@sam-VirtualBox:~$ compiz --replace
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>:1758): DEBUG: Unity accessibility initialization
Initializing unityshell options...done
** (<unknown>:1758): DEBUG: MaximizeIfBigEnough: Gnome-terminal window size doesn't fit
** (<unknown>:1758): DEBUG: PlaceEntry: Applications
** (<unknown>:1758): DEBUG: PlaceEntry: Commands
** (<unknown>:1758): DEBUG: PlaceEntry: Files & Folders

** (<unknown>:1758): WARNING **: Failed to fetch view type at /org/ayatana/bamf/window71303205: Method "ViewType" with signature "" on interface "org.ayatana.bamf.view" doesn't exist

terminate called after throwing an instance of 'std::bad_alloc'
  what(): std::bad_alloc
Aborted (core dumped)

Revision history for this message
oli z (oliver-z) wrote :

same problem like Sam Illingworth here
also compiz died, no panels nor launcher.

Revision history for this message
Nimlar (nicolas-toromanoff) wrote :

same issue if i use the VBoxLinuxAdditions.run to install guest addition : seamless and auto-resize aren't working

Issue corrected after installing the packets :
virtualbox-ose-guest-dkms
virtualbox-ose-guest-utils
virtualbox-ose-guest-x11

(but I didn't test the 3D acceleration).

Revision history for this message
oli z (oliver-z) wrote :

@Nimlar
thanks, its working for me too

Revision history for this message
oli z (oliver-z) wrote :

but the rest is still broken, unable to commit compiz crash report because not enough space (wtf... more than 3gb left), compiz --replace did it for the terminal but the whole rest is gone (launcher, panels...)

Philip Muškovac (yofel)
tags: added: natty
Revision history for this message
Joe Areeda (areeda) wrote :

sudo apt-get install virtualbox-ose-guest-x11
seems to work for me with the default repositories in a new Natty 32 bit install.

Needs to be done INSIDE the VM. This is the only place I've seen that hint.

Revision history for this message
Joe Areeda (areeda) wrote :

Well I have to modify the last message. it sort of works but it doesn't enable 3D acceleration so I can work with Unity.

The error in the attached dialog mentions a version mismatch.

Revision history for this message
Alan Bell (alanbell) wrote :

here is my Xorg.0.log after installing Natty and virtualbox guest additions 4.0.4 http://paste.ubuntu.com/583935/
the crucial segment being this:
[ 8.454] (II) LoadModule: "vboxvideo"
[ 8.454] (II) Loading /usr/lib/xorg/modules/drivers/vboxvideo_drv.so
[ 8.456] (II) Module vboxvideo: vendor="Oracle Corporation"
[ 8.456] compiled for 1.5.99.901, module version = 1.0.1
[ 8.456] Module class: X.Org Video Driver
[ 8.456] ABI class: X.Org Video Driver, version 9.0
[ 8.456] (EE) module ABI major version (9) doesn't match the server's version (10)
[ 8.456] (II) UnloadModule: "vboxvideo"
[ 8.456] (II) Unloading vboxvideo
[ 8.456] (EE) Failed to load module "vboxvideo" (module requirement mismatch, 0)
[ 8.456] (EE) No drivers available.

I then edited my xorg.conf to add this:

Section "ServerFlags"
   Option "IgnoreABI" "True"
EndSection

which overrides the ABI check and downgrades it to a warning. Sadly this doesn't get much further as it ends in a segfault

http://paste.ubuntu.com/583984/

Revision history for this message
Alan Bell (alanbell) wrote :

installing virtualbox-ose-guest-x11 in the natty guest worked great for me, I have 3d accelerated 64bit Natty and Unity working within the 4.0.4 virtualbox on a 32bit Maverick host

Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :

I already was using virtualbox-ose-guest-x11 in my natty installation, but now I can't load Xorg with AiGLX or resizing support:
  (II) AIGLX: vboxvideo does not export required DRI extension

Revision history for this message
Luca Ferretti (elle.uca) wrote :
Download full text (3.8 KiB)

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-termina...

Read more...

Revision history for this message
Michael Thayer (michael-thayer) wrote :

Please see [ https://bugs.launchpad.net/ubuntu/+source/nux/+bug/737610 "Unity doesn't run in VirtualBox: compiz crashed with SIGABRT in __kernel_vsyscall()" ]

Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :

There's a strange issue by the way... I've just downgraded Xorg and Mesa to the version previous the latest working update and the problem persists... However it's quite strange: neither the auto screen resize is working :(

Revision history for this message
Sam Illingworth (mazz0) wrote :

Compiz is working, for me, but the panel and launcher only go transparent when I mouse over them, and the drop shadows are just opaque black boxes.

Revision history for this message
Sam Illingworth (mazz0) wrote :

Can somebody confirm what package we're supposed to install? A search in software centre for Guest Additions only returns the host package. Perhaps we should have a separate bug for something like

"it's totally not obvious what you're supposed to install to get Guest Additions working (there isn't even any indication that you shouldn't be using the standard Guest Additions that comes with VBox on your host)"?

What do you guys think?

Revision history for this message
Alan Bell (alanbell) wrote :

virtualbox-ose-guest-x11 is the answer, however I agree, this is totally non-obvious that it is the right package, or indeed that it is OK to install the ose guest additions in a non-ose host.

Revision history for this message
Sam Illingworth (mazz0) wrote :

Filed as bug 749602 - please lend your weight to it if you think it's worth fixing.

Revision history for this message
ludo33200 (ludo-cheron) wrote :

Just installed Ubuntu 11.4 on VirtualBox 4.0.8 + GuestAdditions 4.08
After the first reboot, natty says the graphic card is not the good one
After having installed GuestAdditions 4.0.8 + reboot it seems to works fine

Release notes for VirtualBox 4.0.8 says
http://www.virtualbox.org/wiki/Changelog
* 3D support: fixed GNOME 3 rendering under Ubuntu 11.04 and Fedora 15

Revision history for this message
ludo33200 (ludo-cheron) wrote :

Upgrading from VirtualBox ( Win7) 4.0.8 + Guest Additions 4.0.8 guest Ubuntu 10.10
To Ubuntu 11.04

The upgrade downloads, install reboot and .... then :
1) the vm graphication definition window no longer will be automatically be changed when the screen is resized
2) the desktop is fully empty, no even Any Applications/Shotcuts/System+ date-shutdown button
+ no more icon on the desktop

This make the system cannot even be properly shutdown

=> just decided to stay in Ubuntu 10.10 until bug has been fixed

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in virtualbox-guest-additions (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.