Custom Query (16363 matches)
Results (439 - 441 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #4168 | obsolete | Grayed-Out USB Devices Require Cable Dance to Connect to Guest | ||
| Description |
I've been working with VirtualBox 2.2.2 and 2.2.4 with a Mac OSX (v. 10.5.7) Host and WinXP SP3 Guest. I have noticed a problem with a grayed-out USB device (a signature tablet HID in my case). To get the grayed-out device to show up in the USB Devices list for activation I can add a filter (either device specific or empty). The problem I've got now is that each time I start the VM the device is grayed-out in the USB Devices list. With a filter applied, the only way I can activate the device is by going through the unplug/replug the USB cable dance.
I'd like to see these sort of grayed-out USB devices just shows up in the device list each time the guest is started without going through the cable dance of unplugging & replugging cables.
Observations About Installing Grayed-Out USB Device (My Experiences) I thought some of my experiences might help you address this problem with grayed-out USB devices.
Failed to attach the USB device "X" to the virtual machine
|
|||
| #4169 | obsolete | Xorg crash when going to S3 suspend with Virtualbox on fullscreen | ||
| Description |
I have using VirtualBox on Kubuntu Jaunty KDE 4.2.2 with NVidia 180 drivers. The system go to S3 suspend and resume normally when I don't using VirtualBox and when I use VirtualBox with WinXP guest at window. But when I try go S3 sleep when VirtualBox with WinXP was opened at fullscreen, it goes to sleep normally, but resume with empty KDM session (Xorg crashed and restarted). At this time in /var/log/kdm.log I see: Backtrace: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4f1b66] 1: /usr/bin/X(xf86SigHandler+0x41) [0x485a61] 2: /lib/libc.so.6 [0x7f0f70b36040] 3: /usr/bin/X [0x4b77f7] 4: /usr/bin/X [0x4b7b95] 5: /usr/bin/X(xf86Wakeup+0x46d) [0x48629d] 6: /usr/bin/X(WakeupHandler+0x4b) [0x451e6b] 7: /usr/bin/X(WaitForSomething+0x1ef) [0x4ef5ef] 8: /usr/bin/X(Dispatch+0x80) [0x44e020] 9: /usr/bin/X(main+0x3bd) [0x433d8d] 10: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f0f70b215a6] 11: /usr/bin/X [0x433219] Saw signal 11. Server aborting. ddxSigGiveUp: Closing log ddxSigGiveUp: re-raising 11 The bug in Ubuntu described here: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/381162 |
|||
| #4174 | obsolete | Install problem in Vista x64 | ||
| Description |
I've been using Virtualbox 2.2.2. I've upgraded several times before, and it work just fine. Doday I tried to upgrade to version 2.2.4 and the installation doesn't finishes. It roolbacks to initial state. I attached the log files |
|||

