VirtualBox

Opened 17 years ago

Closed 16 years ago

#622 closed defect (fixed)

USB stopped working after upgrading from 1.4.0 -> 1.5.0

Reported by: Dominik Riebeling Owned by:
Component: other Version: VirtualBox 1.5.0
Keywords: Cc:
Guest type: other Host type: other

Description

I used VirtualBox 1.4.0 for a while without any real issues on a linux host (Fedora Core 5, using the "all distributions" binary, kernel 2.6.20-1.2319.fc5). I just updated to 1.5.0 (again using the "all distributions" binary) and USB stopped working: when trying to make changes to the USB settings for a machine I get a "failed to access the USB subsystem: Callee RC: 0x80004005" error message.

I also tried running VirtualBox as root to ensure there are no permission issues. It's always reproduceable, even when creating the configuration from scratch.

Change History (3)

comment:1 by Sander van Leeuwen, 17 years ago

You should never run VBox as root. That can cause all sorts of permission problems later on.

USB works again when you downgrade to 1.4.0?

comment:2 by Dominik Riebeling, 17 years ago

I'm gonna be a bit more detailed: I have a setup of VirualBox that is running fine as user. I can configure USB as expected (and if there are permission problems I get a notice once I plug in the usb device that has an appropriate filter active. This applies to 1.4.0.

Now I've updated to 1.5.0. In the configuration dialog I can't change any settings -- once I click the "usb" setting I get the mentioned error message. The configuration window pops up but it's greyed out. If I leave the window the current machine is displayed as "inaccessible". Restarting VirtualBox makes the entry accessible again. Running the machine also works. This happens regardless if I run VirtualBox as user or as root. I tried running it as root to make sure the issue isn't permission related. (I have a different setup for root).

When downgraded to 1.4.0 VirtualBox works again as expected. I can change usb settings and in case of permission problems I get a note about it. I just up- and re-downgraded once again to ensure the issue is still present and still reproduceable.

comment:3 by Sander van Leeuwen, 16 years ago

Resolution: fixed
Status: newclosed

Try again with 1.6.0 and report back if it's still relevant. Thanks.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use