Results 1 to 2 of 2

Thread: Upgrade to 11.1 broke VirtualBox

  1. #1
    sgharp NNTP User

    Default Upgrade to 11.1 broke VirtualBox

    Hi All,

    I upgraded from 11.0 to 11.1, uninstalled VirtualBox from
    the rpm and reinstalled with
    VirtualBox-2.1.2_41885_openSUSE111-1.i586.rpm. I then started getting
    permission denied errors. I followed instructions from another post on
    the problem to chmod 755 and now I'm getting this error.
    VirtualBox: Error -10 in SUPR3HardenedMain!
    VirtualBox: Effective UID is not root (euid=1000 egid=100 uid=1000

    VirtualBox: Tip! It may help to reinstall VirtualBox.
    Reinstalling VirtualBox doesn't fix it. I can run VB as root but not
    as my regular user. My user is a member of the vboxusers group.

    What can I try?

    sgharp's Profile:
    View this thread:

  2. #2
    consused NNTP User

    Default Re: Upgrade to 11.1 broke VirtualBox


    My 11.1 was a clean install from the dvd iso, but I had a permissions
    problem when I installed that same version of VirtualBox today, and
    could only run as root. I had overlooked installing kernel-source and
    kernel-syms packages (probably not the problem), so i installed those.
    Then I got this error: Failed to Create the VirtualBox COM Object

    The VirtualBox FAQ suggested reinstalling - so I did, but could still
    *only run as root*. Running in Konsole as normal user, it failed with an
    error that pointed me at the executable
    */usr/lib/virtualbox/VirtualBox*, and on inspection it didn't have
    permissions for non-root user (i.e. Others). As root, I gave read and
    execute permissions to Others. It still failed to run from command line
    as normal user, this time with the error: Wrong owner (0) of
    '/tmp/.vbox--username--ipc'. This file was probably left there when I
    ran VirtualBox as root.

    So, I went to */tmp* as root and deleted the hidden vbox file (its name
    will include your -user name-). I made sure there was nothing else left
    there to do with VirtualBox. Then it worked! Maybe not exactly the same
    as your problem - but worth a look.

    consused's Profile:
    View this thread:

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts