Custom Query (16363 matches)
Results (940 - 942 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5764 | fixed | Arrow and other keys not working when starting with VBoxSDL => Fixed in SVN | ||
| Description |
Host: Ubuntu 9.10 32bit i386 After upgrading the Host OS (from Ubuntu 8.04) the arrow keys, Home, End, Insert, PgUp, PgDwn, and / on the numeric keypad no longer work when starting the virtual machine with VBoxSDL. The upgrade was an export VBox virtual machine, format hard drive, clean install new OS and then import the vbox Virtual machine. I use the following command to start VirtualBox: /usr/bin/gksudo -u fred 'VBoxSDL --startvm freds_VM --nofstoggle --termacpi' After the upgrade mentioned above, the keyboard keys stopped working (sometimes the Start menu will open, other times it's like a right mouse click is pressed.) If I start Virtual box like this: /usr/bin/gksudo -u fred VBoxManage startvm freds_VM all keys work as expected and as they always have, no matter which of these two methods I use to start the VM. So this appears to be specific to VBoxSDL. |
|||
| #16427 | invalid | As a guest, must hold keyboard key a second or more | ||
| Description |
VBox 5.1.14 installed on Windows 10 with Linux 6 Guest. When working with the guest any key must be held down approximately a second or more to be recognized. |
|||
| #10634 | obsolete | Assert (server_simpleget.c:689) Windows XP when running Premiere Elements with Guest Additions only | ||
| Description |
I have a Windows XP Professional guest running on a CentOS 6.2 host, VB version 4.1.16. If and only if the Guest Additions are installed, Adobe Premiere Elements 10 is partially functional (the main preview window doesn't work) and will reliably crash Windows itself (not the application, Windows disappears and VB reports its status as "Aborted") if I try to use certain features, such as double-clicking a clip in the palette in order to preview it. I tried everything I could think of (turning off hardware acceleration, etc.) and the instability and partial functionality continue. If I uninstall the Guest Additions, Premiere Elements works perfectly. But the default driver doesn't let me make proper use of my 24" monitor, even in full screen. At the very least, I'd like to be able to keep the mouse driver and network driver that are part of Guest Additions installed, but I can't--you either install all or nothing. This means I can't use shared folders, which is quite annoying. If Oracle can't quickly fix the video driver bug, can you split out the network and mouse drivers from the unusable (for me) video one? The core dump attached shows a crash caused by double-clicking an item in the media list of Premiere Elements 10. |
|||

