SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware 14.2 soon to be Slackware 15
Posts: 699
Rep:
VirtualBox won't start
Out of the blue, I can't get VirtualBox to start. I updated Slackware 14.2 to the current version via slackpkg, which didn't install much, and now I get this when trying to start VirtualBox:
/opt/VirtualBox/VirtualBox
VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
VirtualBox: dlopen("/opt/VirtualBox/VBoxRT.so",) failed: <NULL>
I have, of course, removed and reinstalled it. I also removed and reinstalled the video drivers (nVidia proprietary 375.39), but other than that I have no clue. A romp through Google has not revealed anything of use.
Anyone see this before, and have any ideas?
EDIT: I installed an older version of VirtualBox and it works. It appears this is something Oracle did to the current version of VirtualBox....
The current version is 5.1.22, and gives the above error. I backed off to 5.1.14, and that older version works as expected.
Distribution: Slackware 14.2 soon to be Slackware 15
Posts: 699
Original Poster
Rep:
Quote:
Originally Posted by glorsplitz
I just upgraded VirtualBox, Version 5.1.22 r115126 (Qt5.6.1) on slackware 64 14.2 all up to date.
I brought up and installed guest additions on 3 slackware vms and 3 windows vms without any issues.
You said this is with current?
I do see similar message here your <NULL> says "libGL.so.1: cannot open shared object" there.
What does
Code:
ldd /opt/VirtualBox/* | grep missing
say?
Can't do it until tonight, but I'll reload the current version then and report here....
This is with SlackWare 14.2
Edit:
So I tried the previous four versions, and they all work fine. The current version of VirutalBox, 5.1.22 now works. All I did was remove it, run an older version, and then try the current version again....is there a full moon? Increase in cosmic ray activity?
Distribution: Slackware 14.2 soon to be Slackware 15
Posts: 699
Original Poster
Rep:
Quote:
Originally Posted by bassmadrigal
Unless he installed it via SBo, which in that case, just rebuild the virtualbox-kernel package to build against the newer kernel that Slackware added.
I tried that to rebuild the kernel module, did not help. I installed VB from the installer from their website - didn't know there was a slackbuilds package for it...
I vote cosmic rays. It worked before, my kernel has not been touched for a while, and it's working fine now...
Distribution: Slackware 14.2 soon to be Slackware 15
Posts: 699
Original Poster
Rep:
Weird. The /opt/VirtualBox directory and all files underneath should be owned by root. If not, it should complain and tell you something like "Effective UID is not root...."...
I never saw this problem before, have not had this problem since. <shrug>
Distribution: Slackware 14.2 soon to be Slackware 15
Posts: 699
Original Poster
Rep:
BUT if root owns everything you can still get this error. I fixed it by removing all files under /opt/VirtualBox and, as root, run the installer downloaded from their website. Problem solved.
Try it:
chown root:root -Rc /opt/VirtualBox
You get nothing in the output because there is nothing to change. YET now you can't get VB to run! (can someone explain that for me?). Run the installer, which removes the files and reinstalls them, and now it works.
This might be the first time in all the years of using Linux where I've seen a reinstall actually fix a problem....
If you do a web search for VirtualBox: Error -610 in supR3HardenedMainInitRuntime!, you will find many discussions and posts about this error, far too many for me to recommend just one, as I have no experience with this error.
One of them may give you the information you need. (I suspect that the first error led to the second one.)
Distribution: Slackware 14.2 soon to be Slackware 15
Posts: 699
Original Poster
Rep:
It's a two part message. The first part tells you what spawned the supR3HardenedMainInitRuntime error, and apparently there are a lot of different causes...
got the same error and adding my observations. The access writes for /opt and /opt/VirtualBox are relevant too. If /opt/VirtualBox is writable for everyone, the init will fail:
Code:
VirtualBox: supR3HardenedVerifyDir: Cannot trust the directory "/opt/VirtualBox": group and/or other writable (st_mode=040757)
But if /opt is writable for everyone, the start will fail with:
Code:
VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
VirtualBox: dlopen("/opt/VirtualBox/VBoxRT.so",) failed: <NULL>
VirtualBox: Tip! It may help to reinstall VirtualBox.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.