Error -610 in supR3HardenedMainInitRuntime : /usr/lib/virtualbox/VBoxRT.so

[Jason Straight]

On KDE Neon updated to Ubuntu 18.04. Something updated between yesterday and today that broke vbox. Not sure what.

junfan@V:~$ virtualbox 
VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
VirtualBox: dlopen("/usr/lib/virtualbox/VBoxRT.so",) failed: <NULL>

VirtualBox: Tip! It may help to reinstall VirtualBox.

junfan@V:~$ ldd -r /usr/lib/virtualbox/VBoxRT.so
        linux-vdso.so.1 (0x00007fff0d76e000)
        libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007f63e9f88000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f63e9d6b000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f63e9b4c000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f63e9944000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f63e9740000)
        libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 (0x00007f63e937f000)
        libcurl.so.4 => /usr/lib/x86_64-linux-gnu/libcurl.so.4 (0x00007f63e9100000)
        libssl.so.1.1 => /usr/lib/x86_64-linux-gnu/libssl.so.1.1 (0x00007f63e8e96000)
        libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007f63e8a1e000)
        libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f63e8690000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f63e8478000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f63e8087000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f63ea69b000)
        libicuuc.so.60 => /usr/lib/x86_64-linux-gnu/libicuuc.so.60 (0x00007f63e7cd0000)
        liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f63e7aaa000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f63e770c000)
        libnghttp2.so.14 => /usr/lib/x86_64-linux-gnu/libnghttp2.so.14 (0x00007f63e74e7000)
        libidn2.so.0 => /usr/lib/x86_64-linux-gnu/libidn2.so.0 (0x00007f63e72ca000)
        librtmp.so.1 => /usr/lib/x86_64-linux-gnu/librtmp.so.1 (0x00007f63e70ae000)
        libpsl.so.5 => /usr/lib/x86_64-linux-gnu/libpsl.so.5 (0x00007f63e6ea0000)
        libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x00007f63e6c55000)
        libldap_r-2.4.so.2 => /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 (0x00007f63e6a03000)
        liblber-2.4.so.2 => /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2 (0x00007f63e67f5000)
        libicudata.so.60 => /usr/lib/x86_64-linux-gnu/libicudata.so.60 (0x00007f63e4c4c000)
        libunistring.so.2 => /usr/lib/x86_64-linux-gnu/libunistring.so.2 (0x00007f63e48ce000)
        libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x00007f63e4569000)
        libhogweed.so.4 => /usr/lib/x86_64-linux-gnu/libhogweed.so.4 (0x00007f63e4335000)
        libnettle.so.6 => /usr/lib/x86_64-linux-gnu/libnettle.so.6 (0x00007f63e40ff000)
        libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x00007f63e3e7e000)
        libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x00007f63e3ba8000)
        libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x00007f63e3976000)
        libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x00007f63e3772000)
        libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x00007f63e3567000)
        libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f63e334c000)
        libsasl2.so.2 => /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (0x00007f63e3131000)
        libgssapi.so.3 => /usr/lib/x86_64-linux-gnu/libgssapi.so.3 (0x00007f63e2ef0000)
        libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 (0x00007f63e2bc1000)
        libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x00007f63e29ae000)
        libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x00007f63e27aa000)
        libheimntlm.so.0 => /usr/lib/x86_64-linux-gnu/libheimntlm.so.0 (0x00007f63e25a1000)
        libkrb5.so.26 => /usr/lib/x86_64-linux-gnu/libkrb5.so.26 (0x00007f63e2314000)
        libasn1.so.8 => /usr/lib/x86_64-linux-gnu/libasn1.so.8 (0x00007f63e2072000)
        libhcrypto.so.4 => /usr/lib/x86_64-linux-gnu/libhcrypto.so.4 (0x00007f63e1e3c000)
        libroken.so.18 => /usr/lib/x86_64-linux-gnu/libroken.so.18 (0x00007f63e1c26000)
        libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007f63e1a1e000)
        libwind.so.0 => /usr/lib/x86_64-linux-gnu/libwind.so.0 (0x00007f63e17f5000)
        libheimbase.so.1 => /usr/lib/x86_64-linux-gnu/libheimbase.so.1 (0x00007f63e15e6000)
        libhx509.so.5 => /usr/lib/x86_64-linux-gnu/libhx509.so.5 (0x00007f63e139c000)
        libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007f63e1093000)
junfan@V:~$

junfan@V:~$ apt policy virtualbox-5.2
virtualbox-5.2:
  Installed: 5.2.18-124319~Ubuntu~bionic
  Candidate: 5.2.18-124319~Ubuntu~bionic
  Version table:
 *** 5.2.18-124319~Ubuntu~bionic 500
        500 https://download.virtualbox.org/virtualbox/debian bionic/contrib amd64 Packages
        100 /var/lib/dpkg/status

[Jason Straight]

Fixed - thanks to [eventually] finding another bug in the tracker with the same issue.

I had stupidly used cp -a to copy yesterday, instead of -R, and it changed ownership on some stuff in /usr

Might be worth putting in some error handling for that.

[Socratis]

There is an error handling; you just stumbled upon it. ;)

It's called hardening check and tries to make sure that key system directories have the proper permissions. Yours didn't...

BTW, it's usually better and faster, if issues get first addressed in the ​VirtualBox forums, a lot more eyes. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is not a bug and someone from the developers has to deal with it and close it as "Invalid".

You could have also searched for this. Searching for, and restricting it to the VirtualBox forums, should return plenty of results:

​dlopen "/usr/lib/virtualbox/VBoxRT.so" failed site:virtualbox.org

Your first result, for example, would have been ticket #16759, which yours is a duplicate of.

@Admins: Since you're here, you might as well close #16759 as [Invalid].

[Jason Straight]

Better than Microsoft Error messages would be nice though. Something like "ERROR: Permissions on [insert path] are insecure. [path] not owned by root."

[janitor]

#16759