package virtualbox-ose-guest-dkms 3.2.8-dfsg-2ubuntu1~lucid1 failed to install/upgrade: virtualbox-ose-guest kernel module failed to build (/build/include/iprt/types.h:...: error: linux/autoconf.h: No such file or directory)

[klausner]

Binary package hint: virtualbox-ose

Install from synaptic failed

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: virtualbox-ose-guest-dkms 3.2.8-dfsg-2ubuntu1~lucid1
ProcVersionSignature: Ubuntu 2.6.38-8.42~lucid1-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Fri Apr 22 16:22:02 2011
ErrorMessage: virtualbox-ose-guest kernel module failed to build
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
PackageArchitecture: all
PackageVersion: 3.2.8-dfsg-2ubuntu1~lucid1
SourcePackage: virtualbox-ose
Title: package virtualbox-ose-guest-dkms 3.2.8-dfsg-2ubuntu1~lucid1 failed to install/upgrade: virtualbox-ose-guest kernel module failed to build
VirtualBoxOse.ModInfo:

[Felix Geyer (debfx)]

Kernel 2.6.38 isn't supported on lucid.

[Daniel van Vugt (vanvugt)]

There are many bugs relating to DKMS build failures on LTS releases where users have upgraded their kernels. And quite a few of them do get fixed.

[Phearret (phearret)]

ok .. so what I have to downgrade the kernel to be able to run VBox ?? That doesn't sound right. I got the newest VBox build from their site and had all updates already applied in Ubuntu fom the update manager. then I got that error. so the issue is due to which conflict? the kernel not being supported by the rest of Ubuntu or with VBox?

[Jan de Haan (jdehaan)]

A couple of posibilities:

1) did you install the corresponding "linux-header*" package? The
missing linux/autoconf.h:
does seem to point that way.
2) I _assume_ that oracle/vbox create their packages on the LTS versions
of Ubuntu. Maybe you get into trouble if you try to install it on a more
recent
version.

Sincerely,

Jan.

On Tue, Dec 6, 2011 at 8:53 PM, Phearret <email address hidden> wrote:

> ok .. so what I have to downgrade the kernel to be able to run VBox ??
> That doesn't sound right. I got the newest VBox build from their site
> and had all updates already applied in Ubuntu fom the update manager.
> then I got that error. so the issue is due to which conflict? the kernel
> not being supported by the rest of Ubuntu or with VBox?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (830140).
> https://bugs.launchpad.net/bugs/769265
>
> Title:
> package virtualbox-ose-guest-dkms 3.2.8-dfsg-2ubuntu1~lucid1 failed to
> install/upgrade: virtualbox-ose-guest kernel module failed to build
> (/build/include/iprt/types.h:...: error: linux/autoconf.h: No such
> file or directory)
>
> Status in Virtualbox:
> Fix Released
> Status in “virtualbox-ose” package in Ubuntu:
> Confirmed
>
> Bug description:
> Binary package hint: virtualbox-ose
>
> Install from synaptic failed
>
> ProblemType: Package
> DistroRelease: Ubuntu 10.04
> Package: virtualbox-ose-guest-dkms 3.2.8-dfsg-2ubuntu1~lucid1
> ProcVersionSignature: Ubuntu 2.6.38-8.42~lucid1-generic 2.6.38.2
> Uname: Linux 2.6.38-8-generic x86_64
> NonfreeKernelModules: nvidia
> Architecture: amd64
> Date: Fri Apr 22 16:22:02 2011
> ErrorMessage: virtualbox-ose-guest kernel module failed to build
> InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64
> (20100816.1)
> PackageArchitecture: all
> PackageVersion: 3.2.8-dfsg-2ubuntu1~lucid1
> SourcePackage: virtualbox-ose
> Title: package virtualbox-ose-guest-dkms 3.2.8-dfsg-2ubuntu1~lucid1
> failed to install/upgrade: virtualbox-ose-guest kernel module failed to
> build
> VirtualBoxOse.ModInfo:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/virtualbox/+bug/769265/+subscriptions
>

--
"Piracy is simply demand where supply does not exist."

[Daniel van Vugt (vanvugt)]

@Phearret, it is a VBox bug whereby the VBox code did not support any linux kernel above 2.6.37. So it was triggered by upgrading your kernel to a version higher than your version of Ubuntu ships with, which was higher than older versions of VBox support. The bug is fixed in VBox 4.0.4 according to their web site. But you can also work around the bug by using the kernel version that Ubuntu came with.

It's really not a bug in Ubuntu at all, although sometimes we do release Ubuntu updates to avoid such conflicts between proprietary drivers (usually graphics) and new kernels.

[Rolf Leggewie (r0lf)]

not a Ubuntu bug (what do you expect by installing random software from all over the place? phew!)

[Michael Thayer (michael-thayer)]

Given that the Linux kernel doesn't maintain a stable ABI for modules I don't think it can really be considered a VirtualBox bug that a given version doesn't support Linux kernels which weren't written at the time of its release. I would say it is more a sad fact of life.

[Daniel van Vugt (vanvugt)]

Indeed it is a sad fact of life that any software can't guarantee compatibility with other software written after it.

However, people see this particular issue as a package failing to install. An error is reported and their software doesn't work. So it is most definitely a bug worthy of discussion.

[Michael Thayer (michael-thayer)]

True, but casting this as an upstream VirtualBox bug is a bit hard, particularly as Ubuntu packages version 3.2.8 whereas we are already at version 3.2.14 upstream which should support all kernels currently released.

[Daniel van Vugt (vanvugt)]

I think it's safe to class this as a duplicate of bug 705593.