Problem installing Virtualbox 4.1.4 extension pack

Just upgraded to new Virtualbox and when I try to install the extension pack I get the following error:

Failed to install the Extension Pack /home/hgm/Downloads/Oracle_VM_VirtualBox_Extension_Pack-4.1.4-74291 (3).vbox-extpack.

The installer failed with exit code 127: Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty’): No such device or address.

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

I’m stumped by that, any advice most gratefully received!

Did you put quotes around the extpack path when you tried to install it?

I didn’t use the CLI, just double-clicked on the filename. I was asked to read and confirm licence, and then the error.

On 2011-10-26 12:16, gminnerup wrote:
>
> I didn’t use the CLI, just double-clicked on the filename. I was asked
> to read and confirm licence, and then the error.

Root? su? su -?


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Every time Virtualbox comes in a new version, the extensions need to be installed for that particular version. I’ve done it lots of times, and always the same way. No command line, just double-click on the file which launches an installation script. This is the first time that error came up.

Finally done it. As it didn’t work with the usual GUI method, I fired up terminal and used the “VBoxManage install” command, as root. Still don’t understand why it was necessary though…

It is not necessary to reinstall the extension pack every time (AFAIK) - but it’s nice.

I have a script to do that - it uses vboxmanage though.
Update VirtualBox-4.0 Extension Pack.

The latest version of the script is included in the vmscripts package, available on my repo. I think the version posted in the thread is up do date but not 100% sure.

  • I just ran the script on a 11.4 system, and it still works:

# **VBoxExtensionPack **
- Downloading http://download.virtualbox.org/virtualbox/4.1.4/Oracle_VM_VirtualBox_Extension_Pack-4.1.4-74291.vbox-extpack ...
asking libproxy about url 'http://download.virtualbox.org/virtualbox/4.1.4/Oracle_VM_VirtualBox_Extension_Pack-4.1.4-74291.vbox-extpack'
libproxy suggest to use 'direct://'
--2011-10-26 14:17:24--  http://download.virtualbox.org/virtualbox/4.1.4/Oracle_VM_VirtualBox_Extension_Pack-4.1.4-74291.vbox-extpack
Resolving download.virtualbox.org... 137.254.16.69
Connecting to download.virtualbox.org|137.254.16.69|:80... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: http://dlc.sun.com.edgesuite.net/virtualbox/4.1.4/Oracle_VM_VirtualBox_Extension_Pack-4.1.4-74291.vbox-extpack [following]
asking libproxy about url 'http://dlc.sun.com.edgesuite.net/virtualbox/4.1.4/Oracle_VM_VirtualBox_Extension_Pack-4.1.4-74291.vbox-extpack'
libproxy suggest to use 'direct://'
--2011-10-26 14:17:25--  http://dlc.sun.com.edgesuite.net/virtualbox/4.1.4/Oracle_VM_VirtualBox_Extension_Pack-4.1.4-74291.vbox-extpack
Resolving dlc.sun.com.edgesuite.net... 24.244.17.113, 24.244.17.82
Connecting to dlc.sun.com.edgesuite.net|24.244.17.113|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 9566803 (9.1M) [application/x-virtualbox-vbox-extpack]
Saving to: "Oracle_VM_VirtualBox_Extension_Pack.tgz"

100%=====================================================================================================================>] 9,566,803   2.53M/s   in 3.5s    

2011-10-26 14:17:28 (2.59 MB/s) - "Oracle_VM_VirtualBox_Extension_Pack.tgz" saved [9566803/9566803]

- installing Oracle VM VirtualBox Extension Pack 4.1.4r74291
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
**Successfully installed "Oracle VM VirtualBox Extension Pack".**

So if I just downloaded a more recent Extension Pack, I would start the script called VirtualBox, from where you can start your virtual machines and select:

File / Preferences / Extensions and then select the Add Package button and browse to where the new package exists and allow it to be installed (or added).

Thank You,

Neat script, will try it for the next version of Virtualbox. The fact that the extension packs carry the same version numbers as Virtualbox itself suggests to me that it is necessary to update both together. Also, in practice, every time I’ve updated Virtualbox recently (since 4.0) and forgot to update the extension pack, I received an error message concerning the USB 2.0 driver.

If you run it and the VirtualBox and extension pack versions match, the script will simply tell you that the (latest) extension pack is already installed and do nothing. So it is safe to run it at any time.

I didn’t notice - but maybe I didn’t pay attention.