This bug appears to have been fixed in trusty. As I originally said, the
fix is to make sure virtualbox-dkms is installed; the extra command
which I did not give was to run "modprobe vboxdrv" (though running
"/etc/init.d/virtualbox start" should also work). (Running
/etc/init.d/virtualbox does not fix the problem, as it does not cause
the modules to be built.)
** Changed in: virtualbox (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972693
Title:
Error message for missing kernel modules gives wrong command
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/972693/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
