Arch Linux

homayoon

Member

Registered: 2012-04-11

Posts: 16

[SOLVED] Installing VirtualBox extensions: error getting authority

When I try installing VirtualBox extensions pack I get this error message:

Failed to install the Extension Pack /home/mostafa/Downloads/Oracle_VM_VirtualBox_Extension_Pack-4.1.12-77245.vbox-extpack.
The installer failed with exit code 127: Error getting authority: Error initializing authority: Could not connect: No such file or directory.

Details:

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ExtPackManager
Interface: IExtPackManager {3295e6ce-b051-47b2-9514-2c588bfe7554}

Does anybode knows what this means? (And, if it's relevant, I have added my user to vboxusers group.)

Last edited by homayoon (2012-04-12 18:03:35)

Gcool

Member

Registered: 2011-08-16

Posts: 1,456

Re: [SOLVED] Installing VirtualBox extensions: error getting authority

How are you installing it exactly? Try with:

# vboxmanage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.1.12-77245.vbox-extpack

---

Burninate!

homayoon

Member

Registered: 2012-04-11

Posts: 16

Re: [SOLVED] Installing VirtualBox extensions: error getting authority

I was installing it from the GUI, but the the result from command-line is the same:

0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to install "/home/mostafa/Downloads/Oracle_VM_VirtualBox_Extension_Pack-4.1.12-77245.vbox-extpack": The installer failed with exit code 127: Error getting authority: Error initializing authority: Could not connect: No such file or directory

Gcool

Member

Registered: 2011-08-16

Posts: 1,456

Re: [SOLVED] Installing VirtualBox extensions: error getting authority

Maybe a silly question, but you're trying to install it with the correct privileges, right (using sudo or as root)?

---

Burninate!

homayoon

Member

Registered: 2012-04-11

Posts: 16

Re: [SOLVED] Installing VirtualBox extensions: error getting authority

Not a silly question, apparently. I swear I didn't need to do it as root in Ubuntu. Anyway, sudo did the trick. Thanks.

As a matter of interest, don't you think it's a little bit illogical? Since VirtualBox needs the users to be in a special group, stands to to reason that members of that group should be able to manipulate it (unless there was another group like "vboxadmins" or something).