[Pkg-virtualbox-devel] Bug#826303: closed by Gianfranco Costamagna <locutusofborg at debian.org> (Re: Bug#826303: virtualbox-dkms: Installation unsuccesfull)

[Gianfranco Costamagna]

Hi,

Il Sabato 4 Giugno 2016 16:15, Janusz S. Bień <jsbien at mimuw.edu.pl> ha scritto:
>Thank you very much for your quick reaction.



you are welcome
>I use Emacs; debian-el for reporting bugs and the instruction says:
>
>grave
>      *makes the package in question unuseable*
>
>and this is actually the case
>      or mostly so, or causes data
>      loss, or introduces a security hole allowing access to the accounts of
>      users who use the package.
>

>
>Is the instruction wrong or obsolete?

>

not sure, but usually grave means (in pratice, I never read that documentation TBH)
"my system is not starting up anymore, I lost all my data, my laptop is bricked"

:)

>dpkg -l linux-headers-4.1.0-1-amd64
>dpkg-query: no packages found matching linux-headers-4.1.0-1-amd64
>
>How to report officially this problem?


what about
sudo apt-get install linux-headers-4.1.0-1-amd64?

>I found the message misleading. In my opinion it may suggest that "the
>currently running kernel" is not 4.1.0-1-amd64.


AFAIK dkms tries to build the kernel module for *all* the kernels found

on /boot directory, and skips kernels when header files aren't installed.

So, just install them, and dpkg-reconfigure virtualbox-dkms is fine.

The message is not misleading, just people makes no difference
between linux-image (the file) and linux-headers (the header files to
build kernel modules).
They aren't the same, and you need them both for virtualbox!

G.