VirtualBox - out of the blue (probably not) error

virtualbox

#1
[fh@thinkstation ~]$ virtualbox
VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
VirtualBox: dlopen("/usr/lib/virtualbox/VBoxRT.so",) failed: <NULL>

VirtualBox: Tip! It may help to reinstall VirtualBox.

Well - I can do that :slight_smile:

$ sudo pacman -Rns virtualbox virtualbox-guest-iso virtualbox-ext-oracle linux49-virtualbox-host-modules
reboot

Back after reboot

[fh@thinkstation ~]$ sudo pacman -Syu virtualbox virtualbox-guest-iso linux49-virtualbox-host-modules
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 zorglub is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (4) qt5-x11extras-5.9.1-2  linux49-virtualbox-host-modules-5.1.28-4
             virtualbox-5.1.28-1  virtualbox-guest-iso-5.1.28-1

Total Download Size:    58,77 MiB
Total Installed Size:  157,07 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 qt5-x11extras-5.9.1...    12,4 KiB  0,00B/s 00:00 [######################] 100%
 linux49-virtualbox-...   199,4 KiB  12,2M/s 00:00 [######################] 100%
 virtualbox-5.1.28-1...    20,6 MiB  11,3M/s 00:02 [######################] 100%
 virtualbox-guest-is...    38,0 MiB  11,2M/s 00:03 [######################] 100%
(4/4) checking keys in keyring                     [######################] 100%
(4/4) checking package integrity                   [######################] 100%
(4/4) loading package files                        [######################] 100%
(4/4) checking for file conflicts                  [######################] 100%
(4/4) checking available disk space                [######################] 100%
:: Processing package changes...
(1/4) installing qt5-x11extras                     [######################] 100%
(2/4) installing linux49-virtualbox-host-modules   [######################] 100%
===> You must load vboxdrv module before starting VirtualBox:
===> # modprobe vboxdrv
(3/4) installing virtualbox                        [######################] 100%
Optional dependencies for virtualbox
    vde2: Virtual Distributed Ethernet support
    virtualbox-guest-iso: Guest Additions CD image [pending]
    virtualbox-ext-vnc: VNC server support
    virtualbox-sdk: Developer kit
(4/4) installing virtualbox-guest-iso              [######################] 100%

===> virtualbox-guest-iso post install message:
===>
===> Redistribution of VBoxGuestAdditions.iso from the binary packages
===> on www.virtualbox.org with Arch Linux has been granted by
===> InnoTek Systemberatung GmbH.
===>
===> By using this package you accept
===> the VirtualBox Personal Use and Evaluation License (PUEL)
===> which can be found here: http://virtualbox.org/wiki/VirtualBox_PUEL
===>
===> If you do not accept this license, you must remove the package immediately.
===>

:: Running post-transaction hooks...
(1/5) Updating icon theme caches...
(2/5) Updating system user accounts...
(3/5) Arming ConditionNeedsUpdate...
(4/5) Updating the desktop file MIME type cache...
(5/5) Updating the MIME type database...
[fh@thinkstation ~]$ sudo vboxdrv
sudo: vboxdrv: command not found
[fh@thinkstation ~]$ sudo vboxreload
Unloading modules: vboxnetadp vboxnetflt vboxpci vboxdrv 
Loading modules: vboxnetadp vboxnetflt vboxpci vboxdrv 
[fh@thinkstation ~]$ virtualbox
VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
VirtualBox: dlopen("/usr/lib/virtualbox/VBoxRT.so",) failed: <NULL>

VirtualBox: Tip! It may help to reinstall VirtualBox.

No errors during install or reloading of drivers alas the error repeats and I have no clue.

I have scoured for the phrase Error -610 in supR3HardenedMainInitRuntime! and all points to a mismatch of files. But where?


#2

A bright moment occurred: Why don’t I check the ownership of the filesystem - where did I get that?

As it came out - I have some scripts - not packaged - which I copy to /usr/bin /usr/lib /usr/share.

Those are copied using sudo but this time - to my surprise the ownership of the files was fh:users after changing the user:group relation on those files to root:root - the problem disappeared.