Hi,
I’m using, or rather trying to use, VirtualBox OSE from the build-service (version 3.0.2-4.3).
Everytime I try to run it though, I get a message stating:
“Effective UID is not root (euid=1000 egid=100 uid=1000 gid=100) (rc=-10).”
I can, sort of, be circumvented by making sure it’s run as root (using KDE’s kmenuedit) but I’d rather it would run as an ordinary user. And yes, the user is a member of the vboxusers group.
What can I do to fix this? (using openSUSE 11.1, 64-bit)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Out of curiosity does this file have the correct permissions set:
/usr/lib/virtualbox/VirtualBox
For example:
Good luck.
SauronXXX wrote:
> Hi,
>
> I’m using, or rather trying to use, VirtualBox OSE from the
> build-service (version 3.0.2-4.3).
>
> Everytime I try to run it though, I get a message stating:
>
> “Effective UID is not root (euid=1000 egid=100 uid=1000 gid=100)
> (rc=-10).”
>
> I can, sort of, be circumvented by making sure it’s run as root (using
> KDE’s kmenuedit) but I’d rather it would run as an ordinary user. And
> yes, the user is a member of the vboxusers group.
>
> What can I do to fix this? (using openSUSE 11.1, 64-bit)
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJKZmTeAAoJEF+XTK08PnB577oP/3hC1Zehzx1O9YIthu2tgIgT
O/Jd0Ajb2bboWdmLUpnEHPXK6a6oNzmElvONkm/gFLZAMCGngwptmaU5etTUi5mU
bvotZQ5+nIV3gPjE3u+Eoxe4wLCd6fHeWqGJpdpvyib+XXmhLlRMPPxZJKIJrmXE
nw4+WN5xD+7QJdLn59lo6dIpHxknzW3DIKYsWZqDXUddVXsF/rwwZ+eInE61sB8J
oStzI5XdkWAgqrCXM9PnvDEc6pmHDL6YnKZfd8fRd/8Ckp/sGr5buCnSzKme7kf7
okJ+ytZm/tTscjeXBRTrGqvEN2F7+uHvpC43/dmLb60ToswMAvj/luWwzQrR/mRH
aGjs/YR1p5WtEvYCBrFWllYqWTDnFSqhjGd32+QVHOGAwyRDVlq7yGpWJtyPZJCm
K9D0Bvm/eO6XsrfY24p+fF2h6iJao9z0ocm8MYCcdRIyw1RDt+0lhMoaS6k5tUEs
CzG64euoDP7rvypnzj0AtZEOoOYHUP7H8BbWkzaxvOhCalFr3+PTTEDUb9OfdiRI
t96TMht2CIry3Zx0420LgeeGwyV0b8SFHbnOKkDGSBl1TXxfNiSBAWUnydv5aFPj
ibH/KbMfFN2ypRBj+6wocyjWlbDB4y8j9EhJVyuT36TvRVzO6r5HGwlZrEm33gml
BbLVqCK9T1KFNXwXusDi
=nYaY
-----END PGP SIGNATURE-----
Those are not the ones I have, no. Shouldn’t the group be vboxusers??
Still, if the permissions you listed are what they should be like I can alter them myself. But won’t an upgrade, whenever vbox is upgraded in the repo, revert them back to whatever the permissions are in the .rpm file??
Mine are:
-rwxr-xr-x 1 root vboxusers 23096 2009-07-16 18:08 VirtualBox
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
That may be the issue. In my case my build is, I believe, from the
VirtualBox website directly. Whatever RPM they had that was closes to
SUSE is the one that I am using and it’s been good. I’d have to try yours
to see if it works. Which repo was it from? Have you tried the one
directly from VirtualBox/Sun?
Good luck.
SauronXXX wrote:
> ab@novell.com;2015574 Wrote:
>> For example:
>>
>> - -r-s–x–x 1 root root 23096 2009-07-10 10:47
>> /usr/lib/virtualbox/VirtualBox
>
> Those are not the ones I have, no. Shouldn’t the group be vboxusers??
>
> Still, if the permissions you listed are what they should be like I can
> alter them myself. But won’t an upgrade, whenever vbox is upgraded in
> the repo, revert them back to whatever the permissions are in the .rpm
> file??
>
> Mine are:
>
>
> Code:
> --------------------
>
> -rwxr-xr-x 1 root vboxusers 23096 2009-07-16 18:08 VirtualBox
>
> --------------------
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJKZoOZAAoJEF+XTK08PnB50YAP/1VWrDEDnq0GvBlYwvn9HddH
rMOtTlDqeBPyKSZkK1kuOKLd3oPL0mIogZ9R2oMedEPmYmDhpX/d18EK4664tSq4
nbE1c8JGuluC7tgHjdNcwoy2g1LMu1kPPxiAFVpFOrHBhRnHCAfQ5U/VJ8V599rA
51bWDVO9DMb4rpJA5xySuf6/83DNggaKRK+LrGqdmO4Z+UG3xj8f3vpAp5QO11j2
xAVohqZx4FIGVxo5smH+w66zr/23wyy7UMx24oJeqsvgIiTUlpCDUS8VkB+LBaBH
8VWbJ/uODdEr10PaR+qaKqLhDxlNUpweyGrPcHxtoc8VsnbZ1iwa3G9O81ndhjFF
Sa32j1qvEoA2holgLEMK30EHfQsoZ6GRD9nKfT1uPDOrbv6tY8QjPoXmi0j8fp6p
oKU9cBTiX/GDQthd7TSh2LcwY+95UBEo7Quwm43tyND1oO2oyxKe+d+rQYy2PcIJ
j8Q2VP2Hll0gTYK4jn2GoCrO0w0nmp0QM8h3hh7kHaf8NhO+NjRAhXeCq9hAISq8
X9zi9p2hU1qrnafXu+voyfX3JIlP1XpVnGHgokVR4vUnteoO49fM3gbFkiIRtDwS
JTLObYWPabPYg09QGv4uOtZH+1BvXmfCFl01iBH0EpWYnAtcMjna+9eIXw13VpAZ
wBdG3Tx9pRgPEE8+1fdL
=ITRB
-----END PGP SIGNATURE-----
Uninstall the virtual box you have.
Download it from here:
Linux_Downloads - VirtualBox
Then in dolphin navigate to where the file you downloaded is. Open the View - Panels - Terminal
Now switch to su
and in the location of the vbox file do this
rpm - ihv *Package name*
(If type the first few letters of the *Package name and then hit TAB it will auto complete)
Now hit enter and wait.
You need to be in vboxusers group: ( open YaST → Security and Users → UserManagement, and edit your user and add them to the vboxusers group. To do this, select your user name, click on Edit, switch to the Details tab and check the vboxusers check box.)
After kernel updates you will need to do this from su terminal:
/etc/init.d/vboxdrv setup
You may want to upgrade virtual box, so download the latest .rpm and do:
rpm - Uhv *Package name*
move the old .rpm out of that directory first.
I have now, and the one on their website works. I was just hoping I wouldn’t have to do that - I prefer to keep everything installed through the package-manager if at all possible.
The one I was using was from the following repo:
Index of /repositories/Virtualization:/VirtualBox/openSUSE_11.1
And so you can use Yast to install and upgrade the VBox rpm downloaded from the Sun website, or indeed any other third-party rpm.
Set up a local directory in say ~/home, give it any name you chose (e.g. local-rpm). Move/copy the VBox rpm into it.
Open YaST>Software Repositories>Add. Select “Local Directory…” and click “next”. Enter a Repository Name, give Path to Directory (you just setup in ~/home), and check option “Plain RPM Directory”. Continue through to the finish.
Just like any repo, you must enable and refresh to use it. To upgrade VBox just remove the rpm from the directory in ~/home, and replace it with the new version rpm. Remember to refresh the repo with Yast, and use Yast>Software Management to perform the update.
Well, sure. That method works. And I’m sure it’s a great solution for say a company with some in-house tools that needs to get pushed out to the clients on a regular basis (or the equivalent using nfs really).
For me as a home-user it’s not as helpful. Sure, it works. But I still need to download the rpm manually from time to time and put it in the correct directory which partially defeats the purpose of using repositories. It’s faster to just download the rpm and do a zypper in whatever.rpm in my opinion. At least if you, like me, only use one or two rpms that are not a part of any “ordinary” repository.
Edited to add: if the rpm always had the same filename on the remote server it would be a different story. Then I could just hack together a small bash-script (and run it as a root-cronjob) to do the download, move it to the right directory and do zypper ref && zypper up.
Hey, what’s with all the blah, blah. I am a home user too. I use that method. You have to download it anyway. Several here used that method because it avoided permission problems with starting VBox (PUEL version) a few releases ago. Never had a problem since, some others who just click on it to install have had.
The OSE version (no usb support) is available from the openSUSE distribution repo. I don’t think the VBox site provides an rpm based repo. That’s just tough.
Frankly, It takes less time to implement it and use it occasionally than it does to discuss it.
Hi consused! long time seen!
I think you’re overcomplicating the use of a local repo! I did too until I discovered how easy it really is. Don’t delete old rpm’s and there’s really no need to refresh the repo. Once you’re in the repo mark the software and click the version tab at the botttom of the dialog, there you have them all, you can probably roll back your software to an earlier version this way, although I haven’t tested that, I simply haven’t needed too! Go test it!
Btw, aren’t You too a little impressed over the lack of questions about usb and virtualbox? We really ironed that one out!
Hi there Hank. Haven’t seen you either. Since VBox has worked smoothly, I spent the extra time following 11.2 milestones. How about about you?? For me it’s been interesting to experience phase changes of the development cycle (as a non-dev myself). The 11.1 VBox releases have worked ootb on 11.2 and no mods so far on my few devices. I know you posted about the changes to 11.2 around M1. @upscope’s been posting on 11.2, but don’t know if he fiinally sorted out that all-in-one problem.
Thanks for the tips. It was pretty easy anyway, and that will make it even more so. The explanations will be a lot shorter for posting.
I do use version selection when sorting out Factory downloads for 11.2. I will give it a test, as I generally retain the previous version.
Btw, aren’t You too a little impressed over the lack of questions about usb and virtualbox? We really ironed that one out!
Indeed I am. I was thinking that only a couple of weeks back. We certainly ironed it, back and front. 
Also had the “Effective UID is not root” problem today after installing Virtual box 2 from openSUSE_BuildService_-Virtualisation(VirtualBox)
So I uninstalled it, went to the VirtualBox web site and downloaded the suse 11.1 64-bit rpm.
I installed it with rpm -ivh, it asked for a dependance: pam-devel. Installed pam-devel with yast then installed vbox3 with rpm -ivh and now everything’s fine.
I’m surprised Vbox3 retained all my preferences from vbox2 without a hitch!