Skip to main content
Topic: Virtualbox: Failed to create the VirtualBoxClient COM object. (Read 1001 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Virtualbox: Failed to create the VirtualBoxClient COM object.

Hi,
the current virtualbox-6.0.4-1-x86_64 is linked to the wrong libvpx (libvpx-1.8.0).
You get just the error message: Failed to create the VirtualBoxClient COM object.
Diagose: strace VBoxManage list vms 2>&1 | grep ENOENT

Quick solution until fixed upstream:
sudo ln -s /usr/lib/libvpx.so /usr/lib/virtualbox/libvpx.so.5

Btw. the virtualbox package is not respecting my config changes in /usr/lib/modules-load.d/virtualbox-host-modules-artix.conf
chattr +i virtualbox-host-modules-artix.conf
need to be done to protect my changes.

Re: Virtualbox: Failed to create the VirtualBoxClient COM object.

Reply #1
Thanks for the reports. Could you please share the output of
Code: [Select]
$ pacman -Qo /usr/lib/modules-load.d/virtualbox-host-modules-artix.conf
Normally, pacman wouldn't overwrite that file if there had been any change. Also, instead of chattr'ing it, you could instead instruct pacman not to touch it:
Code: [Select]
/etc/pacman.conf
NoUpgrade = usr/lib/modules-load.d/virtualbox-host-modules-artix.conf

Re: Virtualbox: Failed to create the VirtualBoxClient COM object.

Reply #2
pacman -Qo /usr/lib/modules-load.d/virtualbox-host-modules-artix.conf
Code: [Select]
/usr/lib/modules-load.d/virtualbox-host-modules-artix.conf is owned by virtualbox-host-modules-artix 6.0.4-9

I have once changed /usr/lib/modules-load.d/virtualbox-host-modules-artix.conf and it got overwritten from a update.
I changed it again with additional chmod 0400 and it got overwritten from a update. Again.
Thank you for fast acknowledging the bugs. The wrong libvpx bug is now fixed with the last update of virtualbox and thunderbird.

 

Re: Virtualbox: Failed to create the VirtualBoxClient COM object.

Reply #3
Yes, unfortunately r/o won't protect the file from pacman, only NoUpgrade.
For libvpx, you probably got caught in a slow mirror sync and only had a partial upgrade.