Hi Walter, let's answer:
>Added system-image-cli and dpkg reconfigured the initial machine and no luck.
>Additionally no luck with adding the ppa and >fresher virtualbox. Got all the
>qt depends added, but there's still some python depends that don't seem so
>easily resolved. >FWIW:
>
>---
>The following packages have unmet dependencies:
> virtualbox:amd64 : Depends: python:amd64 (< 2.8) but it is not going to be
> installed
> Depends: python2.7:amd64 but it is not going to be
> installed
> Depends: python:amd64 (>= 2.7~) but it is not going to be
> installed
> Depends: virtualbox-dkms:amd64 (>=
> 5.0.12-dfsg-3ubuntu1~trusty1) but it is not installable or
> virtualbox-source:amd64 (>=
> 5.0.12-dfsg-3ubuntu1~trusty1) but it is not installable or
> virtualbox-modules:amd64 but it is not installable
> Recommends: virtualbox-qt:amd64 (=
> 5.0.12-dfsg-3ubuntu1~trusty1) but it is not going to be installed
>---
>
this seems to be a python issue, can you install python:amd64? or
python2.7:amd64?
I wouldn't blame virtualbox for a python issue, maybe python/trusty isn't
multiarch?
>Different errors this time, though:
I don't care about the errors this time :)
you didn't build the dkms module, so the errors will be about a version
mismatch.
>---
>Result Code: NS_ERROR_FAILURE (0x80004005)
>Component: MachineWrap
>Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
>---
>RTR3InitEx failed with rc=-1912 (rc=-1912)
>
>The VirtualBox kernel modules do not match this version of VirtualBox. The
>installation of VirtualBox was apparently not >successful. Executing
>
>'modprobe vboxdrv'
>
>may correct this. Make sure that you do not mix the OSE version and the PUEL
>version of VirtualBox.
>
>where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH
>(-1912) - The installed support driver >doesn't match the version of the user.
>---
>
>Of course, loading vboxdrv is not going to help. I tried purging and
>reinstalling to no avail.
>
nope, until the dkms builds it, it won't help
>Noticing the OSE/PUEL issue, I started searching for licenses.
>
>$ for thing in "$(lsmod | grep vbox | awk '{print $1}')"; do
>> modinfo $thing | grep license; done
>
>produces nothing but GPL. That's more or less the case with all of my modules.
>And besides, my most recent version besides all >this changes was 4-something
>and PUEL is only applicable to earlier versions… except for the Extension Pack.
>
>So I grabbed the latest from the VBox website. Installed fine. Same problems.
>I'm at a loss.
no, please don't mix vbox from website with the ubuntu one, because if
you don't purge it, you won't have a working state.
so, please purge everything called virtualbox, specially virtualbox-5.0
(I really mean purge, not remove), try to install python2.7:amd64, and
then install virtualbox-dkms.
If you can't install python2.7 you won't be able to fix this issue, it
seems to be the culprit, regardless of who did build virtualbox.
cheers!
Gianfranco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533479
Title:
virtualbox-dkms 4.3.34-dfsg-1+deb8u1ubuntu1.14.04.1: virtualbox kernel
module failed to build [scripts/genksyms/genksyms: 1:
scripts/genksyms/genksyms: Syntax error: "(" unexpected]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1533479/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
