karmic to lucid upgrade: virtualbox modules fail to built and cause upgrade to fail

Bug #513529 reported by Alexander Sack
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
virtualbox-ose (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: virtualbox-ose

Just upgraded from karmic to lucid ...

Loading new virtualbox-ose-3.1.2 DKMS files...
First Installation: checking all kernels...
Building for 2.6.31-17-generic and 2.6.32-rc4
Building initial module for 2.6.31-17-generic

Error! Bad return status for module build on kernel: 2.6.31-17-generic (i686)
Consult the make.log in the build directory
/var/lib/dkms/virtualbox-ose/3.1.2/build/ for more information.
dpkg: error processing virtualbox-ose-dkms (--configure):
 subprocess installed post-installation script returned error exit status 10
dpkg: dependency problems prevent configuration of virtualbox-ose-source:
 virtualbox-ose-source depends on virtualbox-ose-dkms (>= 3.1.2-dfsg-1ubuntu1); however:
  Package virtualbox-ose-dkms is not configured yet.
dpkg: error processing virtualbox-ose-source (--configure):
 dependency problems - leaving unconfigured

Tags: karmic2lucid
Revision history for this message
Alexander Sack (asac) wrote :

guess this should be targetted for lucid as it breaks upgrades.

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

Could you please attach the make.log file from /var/lib/dkms/virtualbox-ose/3.1.2/build/

Daniel Hahler (blueyed)
Changed in virtualbox-ose (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
hexion (hexium) wrote :

$ cat /var/lib/dkms/virtualbox-ose/3.1.2/build/make.log

DKMS make.log for virtualbox-ose-3.1.2 for kernel 2.6.33-020633rc8-generic (x86_64)
mar feb 16 01:46:43 GMT 2010
make: se ingresa al directorio `/usr/src/linux-headers-2.6.33-020633rc8-generic'
  LD /var/lib/dkms/virtualbox-ose/3.1.2/build/vboxdrv/built-in.o
  CC [M] /var/lib/dkms/virtualbox-ose/3.1.2/build/vboxdrv/linux/SUPDrv-linux.o
In file included from /var/lib/dkms/virtualbox-ose/3.1.2/build/include/VBox/types.h:34,
                 from /var/lib/dkms/virtualbox-ose/3.1.2/build/vboxdrv/linux/../SUPDrvInternal.h:39,
                 from /var/lib/dkms/virtualbox-ose/3.1.2/build/vboxdrv/linux/SUPDrv-linux.c:37:
/var/lib/dkms/virtualbox-ose/3.1.2/build/include/iprt/types.h:100:30: error: linux/autoconf.h: No existe el fichero ó directorio
make[2]: *** [/var/lib/dkms/virtualbox-ose/3.1.2/build/vboxdrv/linux/SUPDrv-linux.o] Error 1
make[1]: *** [/var/lib/dkms/virtualbox-ose/3.1.2/build/vboxdrv] Error 2
make: *** [_module_/var/lib/dkms/virtualbox-ose/3.1.2/build] Error 2
make: se sale del directorio `/usr/src/linux-headers-2.6.33-020633rc8-generic'

The problem is explained here:
http://vbox.innotek.de/pipermail/vbox-dev/2009-December/002162.html

Although they clarify in a newer email that the final fix was different.

Changed in virtualbox-ose (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
hexion (hexium) wrote :
Revision history for this message
Felix Geyer (debfx) wrote :

The original bug report was about kernel 2.6.31-17-generic.
For kernel 2.6.33: bug #520168

Changed in virtualbox-ose (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jan Gutter (ubuntu-jangutter) wrote :

Wow, and I had such high hopes for my first upgrade (Karmic->Lucid)!

It seems the Ubuntu developers are not really interested in fixing this problem, or the many other open bugs. The workaround obviously appears to uninstall virtualbox before upgrading, yet nobody seemed to mention it on the Lucid upgrade site...

Ah well.

tags: added: karmic2lucid
Revision history for this message
rusivi2 (rusivi2-deactivatedaccount) wrote :

Thank you for posting this bug.

As per bug 52016 this issues is resolved. Marking as such.

Changed in virtualbox-ose (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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