VirtualBox asks me to run vboxconfig each time

jsbjsb001 · 03-09-2017, 03:48 AM

Quote:

Originally Posted by Stéphane Ascoët

No changes, and I can't see how the sticky bit could be linked to it.

Try removing the sticky bit, and let us know, how it goes.

Stéphane Ascoët · 03-09-2017, 05:51 AM

Theses files appears only after sucessful '/sbin/vboxconfig'

jsbjsb001 · 03-09-2017, 05:53 AM

Quote:

Originally Posted by Stéphane Ascoët

Theses files appears only after sucessful '/sbin/vboxconfig'

Are you saying that it's, working now?

Stéphane Ascoët · 03-09-2017, 05:59 AM

Things are still exactly the same since my original post.

jsbjsb001 · 03-09-2017, 06:05 AM

Quote:

Originally Posted by Stéphane Ascoët

Things are still exactly the same since my original post.

Have you removed the sticky bit?
If not, do that and then;

run the command in your original post.

As I do not understand why else, it would keep asking you to run the command (or why the sticky bit is even there, in the first place). Failing all of the above (and a re-install, FROM official repo's for your distro), I do not know what else to suggest. As it looks to me like a permission problem.

Stéphane Ascoët · 03-09-2017, 06:20 AM

I can't remove the sticky bit since the file is created by '/sbin/vboxconfig'!

I think that vboxconfig installs something when launched that is not kept in Debian starting process.

jsbjsb001 · 03-09-2017, 06:22 AM

Quote:

Originally Posted by Stéphane Ascoët

I can't remove the sticky bit since the file is created by '/sbin/vboxconfig'!

I think that vboxconfig installs something when launched that is not kept in Debian starting process.

Did you try changing it as root/superuser??

Stéphane Ascoët · 03-09-2017, 06:33 AM

Yes, even in root the file doesn't exist

jsbjsb001 · 03-09-2017, 06:38 AM

Quote:

Originally Posted by Stéphane Ascoët

Yes, even in root the file doesn't exist

Try running (AS root/superuser) the following command;

Code:

chmod g-s a /dev/vboxdrvu

Let us know how it goes...

hydrurga · 03-09-2017, 11:22 AM

That behaviour is certainly strange. My /dev/vboxdrv, vboxdrvu and vboxnetctl are all root-owned and persistent after Virtualbox has been closed.

Let's go back to first principles, if you're ok with that.

Can you let us know what exactly is installed on your system using:

dpkg -l *virtualb* | grep -v "^.n"

Also, how did you install VirtualBox?

Stéphane Ascoët · 03-14-2017, 07:43 AM

chmod g-s a /dev/vboxdrvu

This chmod line assumes that "a" is a file... and tell me, without surprise, that /dev/vboxdrvu doesn't exist.

dpkg -l *virtualb* | grep -v "^.n"
rc virtualbox 4.1.42-dfsg-1+deb7u1 amd64 x86 virtualization solution - base binaries
ii virtualbox-5.1 5.1.14-112924~Debian~wheezy amd64 Oracle VM VirtualBox
rc virtualbox-qt 4.1.42-dfsg-1+deb7u1 amd64 x86 virtualization solution - Qt based user interface

jsbjsb001 · 03-22-2017, 01:19 AM

Quote:

Originally Posted by Stéphane Ascoët

chmod g-s a /dev/vboxdrvu

This chmod line assumes that "a" is a file... and tell me, without surprise, that /dev/vboxdrvu doesn't exist.

dpkg -l *virtualb* | grep -v "^.n"
rc virtualbox 4.1.42-dfsg-1+deb7u1 amd64 x86 virtualization solution - base binaries
ii virtualbox-5.1 5.1.14-112924~Debian~wheezy amd64 Oracle VM VirtualBox
rc virtualbox-qt 4.1.42-dfsg-1+deb7u1 amd64 x86 virtualization solution - Qt based user interface

I would suggest you re-install Virtualbox from official repo's for your distro. Make sure you uninstall your current Virtualbox first.

Stéphane Ascoët · 04-07-2017, 03:21 AM

I've done it but there is no /usr/bin/virtualbox anymore, I can't launch it. I can't find any executable in the package that has been installed: https://packages.debian.org/wheezy/a...albox/filelist

jsbjsb001 · 04-08-2017, 06:56 AM

Quote:

Originally Posted by Stéphane Ascoët

I've done it but there is no /usr/bin/virtualbox anymore, I can't launch it. I can't find any executable in the package that has been installed: https://packages.debian.org/wheezy/a...albox/filelist

I don't know what else to suggest to you at this point, as at least in terms of your original problem, I'm sure it was the sticky bit being set (why it was, I don't know - and should not have been there, in the first place) that was causing it.

The only other thing I can think of trying would be to reinstall your distro (backup anything you would like to keep, that is not a part of it) and see if that helps.

Emerson · 04-08-2017, 07:12 AM

Looking at your problem the modules are not loaded. Have you tried to load them by hand? (Rebuilding works because the last step is to load the modules.)