Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#61225 - [virtualbox] 6.0.0-1 Fails to start, missing opus dependency

Attached to Project: Community Packages
Opened by Leonid Bloch (blochl) - Monday, 31 December 2018, 17:45 GMT
Last edited by Christian Hesse (eworm) - Tuesday, 08 January 2019, 14:27 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

Immediately after updating to version 6.0.0 VirtualBox fails to start:

$ vboxmanage startvm myvm
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154) - Class not registered (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

Same messages appear in a GUI window when started using the `virtualbox` command.

All the VirtualBox drivers are loaded:

$ lsmod | grep vbox
vboxnetflt 32768 0
vboxnetadp 28672 0
vboxpci 28672 0
vboxdrv 499712 3 vboxpci,vboxnetadp,vboxnetflt

This occurs on a server with a minimal collection of packages (just what is needed for VirtualBox to work). This does not occur on a desktop system with many packages installed on it (even after upgrade to 6.0.0). Hence it feels like some new dependency for VirtualBox 6.0.0 is missing from the PKGBUILD, and on the desktop machine it is, by chance, installed.
This task depends upon

Closed by  Christian Hesse (eworm)
Tuesday, 08 January 2019, 14:27 GMT
Reason for closing:  Fixed
Additional comments about closing:  in SVN
Comment by Leonid Bloch (blochl) - Monday, 31 December 2018, 18:37 GMT
By comparing the outputs of `strace vboxmanage list vms` from the working and the non-working systems, I determined that installing the package "opus" solves the issue. Please make opus a dependency of VirtualBox (now it is a make-dependency only).

Loading...