USB dialogs non-functional in 3.2.4 -> duplicate of #6983

Description

USB Devices dialog box first appears with incorrect listing, then disappears when mouse moves into box, and will not appear again. End result is that I cannot connect to USB devices within the Guest. Device appears just fine in the host.

Only began occurring after update to Oracle VirtualBox 3.2.4, 3.2.2 was fine.

(Virtual Machine status never gets updated in VirtualBox, either. After vm shuts down, status still shows as "running" unless I close VirtualBox and restart it.)

I am getting the same errors as above while running 3.2.4 in Ubuntu Jaunty i386. The USB devices that used to show up with their correct names now appear as Unknown Devices and give the following errors when I try to attach them:
Failed to attach the hard disk (/media/disk/Virtual Machines/Vista 32 Bit Virtual.vdi) to slot IDE Primary Master of the machine .

I generally update VirtualBox within a few days of an update notice, so I'm reasonably certain I was running 3.2.2 prior to the 3.2.4 update, but I did have to roll back all the way to 3.1.4 to get USB working again after the 3.2.4 update. Rolling back one version didn't help.

Hope this gets found and fixed soon! (Also wish I could get VirtualBox to stop nagging me to update to 3.2.4, given that it doesn't work for me)

I'm having similar problems on Ubuntu Hardy, running an XP host. USB devices worked in 3.2.2, but in 3.2.4 and 3.2.6 the USB menu shows 'Unknown' devices at first menu activation; but here after the menu will never show again. NS_ERROR_FAILURE (0x80004005) events are generated in the log while attempting to access the USB menu's.

When going back into look again, there are no devices. Right clicking on VM shows all options greyed out besides "show log"

When the VM is powered on, I click the USB icon and note the devices. Clicking on them subsequently disables icons. Restarting VM and trying again, I hover over the USB icon and receive "no devices attached". Clicking on an "unknown device" I receive the following:

I will mark this ticket a duplicate of #6983, as the issue is handled there. The original fix was indeed a partial one which only worked with some setups. I believe we have now fixed the remaining cases.