VirtualBox

Ticket #2726 (closed defect: worksforme)

Opened 5 years ago

Last modified 5 years ago

crash VirtualBox 2.0.6 on Mac Intel 10.5.5

Reported by: bustervirtual Owned by:
Priority: critical Component: host support
Version: VirtualBox 2.0.6 Keywords:
Cc: Guest type: Windows
Host type: Mac OS X

Description

I can't open the soft. This is the error message :

"Effective UID is not root (euid=501 egid=2 uid=501 gid=20)(rc=10) It may help to reinstall VirtualBox."

I attach my log file.

Help me, i'll prefer not to resinstall, because too many installs inside the virtualmachine (windows xp and servicepack2 and IE7 and IE6).

Thanks for all and excuse my english (i'm french)

Attachments

VBox.log Download (39.1 KB) - added by bustervirtual 5 years ago.

Change History

Changed 5 years ago by bustervirtual

comment:1 Changed 5 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Please reopen if this crash persists with VirtualBox 2.2.2.

comment:2 Changed 5 years ago by ebonweaver

  • Status changed from closed to reopened
  • Resolution fixed deleted

This is occurring with VB 3.0.0

comment:3 Changed 5 years ago by frank

ebonweaver, you host is Mac OS X as well? How did you install the package?

comment:4 Changed 5 years ago by ebonweaver

3.0.0 was installed on a fresh system, 10.5.7. I believe this app broke when permissions from /Applications were propagated to correct some other installed software that had bad permissions. I'm guessing that VirtualBox refuses to run when "standard" permissions are in place. Deleting the app bundle and installing 3.0.2 has resolved the issue for now, but it seems there could be a problem if one does what I did to fix issues and instead causes them. I'm not sure why VB refuses to launch if permissions are not whatever special set it installs with or why they must be different than what is standard on /Applications. This may be intentional and expected but feels like a bug to the end user.

comment:5 Changed 5 years ago by frank

  • Status changed from reopened to closed
  • Resolution set to worksforme

The permissions are set by intension. VirtualBox is a user-level application which has to make use of restricted features. This can only be done using a special kernel driver. The permissions ensure that not every user application can access this driver. So I will close this ticket as it seems your problem was not a crash but a permission problem.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use