On Thu, 2015-09-10 at 15:28 +0530, shirish शिरीष wrote: > Package: virtualbox > Version: 5.0.4-dfsg-1 > Severity: important > > Dear Maintainer, > I installed virtualbox and it complains :- > > $ sudo aptitude install virtualbox=5.0.4-dfsg-1 > The following NEW packages will be installed: > virtualbox > 0 packages upgraded, 1 newly installed, 0 to remove and 0 not > upgraded. > Need to get 0 B/13.7 MB of archives. After unpacking 62.1 MB will be > used. > Retrieving bug reports... Done > Parsing Found/Fixed information... Done > Selecting previously unselected package virtualbox. > (Reading database ... 260153 files and directories currently > installed.) > Preparing to unpack .../virtualbox_5.0.4-dfsg-1_amd64.deb ... > Unpacking virtualbox (5.0.4-dfsg-1) ... > Processing triggers for systemd (225-1) ... > Processing triggers for man-db (2.7.3-1) ... > Setting up virtualbox (5.0.4-dfsg-1) ... > Job for virtualbox.service failed because the control process exited > with error code. See "systemctl status virtualbox.service" and > "journalctl -xe" for details. > invoke-rc.d: initscript virtualbox, action "restart" failed. > Processing triggers for systemd (225-1) ... > Scanning processes... > Scanning candidates... > Scanning linux images... > Running kernel seems to be up-to-date. > Restarting services using systemd... > No containers need to be restarted. >
Your bug report made me go look into my logs and indeed, vbox does
fail. But I'm not sure if I understand the flow of your console log.
Setting up libqt4-test:amd64 (4:4.8.7+dfsg-3) ...
Setting up virtualbox (5.0.2-dfsg-2) ...
Job for virtualbox.service failed because the control process exited
with error code. See "systemctl status virtualbox.service" and
"journalctl -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
Setting up virtualbox-qt (5.0.2-dfsg-2) ...
Setting up virtualbox-dkms (5.0.2-dfsg-2) ...
Loading new virtualbox-5.0.2 DKMS files...
Building only for 4.1.6+
Building initial module for 4.1.6+
Done.
vboxdrv:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.1.6+/updates/dkms/
vboxnetadp.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.1.6+/updates/dkms/
vboxnetflt.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.1.6+/updates/dkms/
vboxpci.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.1.6+/updates/dkms/
depmod....
DKMS: install completed.
Setting up libapt-inst1.7:amd64 (1.0.10.2) ...
Setting up apt-utils (1.0.10.2) ...
Setting up libkeyutils1:amd64 (1.5.9-7) ...
This is from my console logs. Now VBox fails because it got
installed/upgraded prior to the dkms package, which was supposed to
roll in the new drivers.
In your logs, there's no mention of the dkms package.
@Gianfranco: What is your opinion?
I think we should add a, Depends: virtualbox-dkms (=
${binary:Version}), so that virtualbox can pick it up. Currently, it is
a Recommends.
If you ask my opinion, I think we should promote it to Pre-Depends:
virtualbox-dkms | virtualbox-source
Is VBox useful without the kernel modules loaded ?
> Also, the recommends are not installed, they should get in the action
> right ?
>
> virtualbox-dkms and virtualbox-qt I mean by those.
>
>
It may have to do with your APT Policy settings. virtualbox currently
Recommends: virtualbox-dkms
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
