Custom Query (16363 matches)
Results (883 - 885 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #765 | obsolete | defect: mouse wheel behaves as if shift key is pressed | ||
| Description |
My configuration: virtual box 1.50 host: WinXP professional sp2 guest: Fedora Core 7 with vbox additions installed I noticed this unusual behavior when I was using firefox in guest OS. When I scroll up/down any webpage using mouse (middle) wheel, firefox will randomly jump to other page as if 'Forward' or 'Back' button were clicked. And this is very reproducible, especially when I quickly toggles between wheel up and wheel down (rub the wheel back and forth quickly). Now as a fact Firefox actually supports mouse shortcut for 'back' and 'forward' action as 'shift+mouse wheel down' and 'shift+mouse wheel up'. So it appears to me that while I do not press any keyboard key, and am very sure that shift key is not accidentally locked, something makes Firefox thinks shift key is pressed at the time. This phenomenon does not occur when vbox additions is not installed. AND, even if vbox does not capture keyboard, the problem still persists (I press right ctrl and the small icon in the right bottom corner of vbox window grayed indicating keyboard is not captured by guest OS). So I am pretty sure this is not a hardware keyboard problem. Also I do not have problem using firefox this way in host OS. So I come to create this ticket believing it is a defect of Virtual Box 1.50. I wanted to create a small movie recording this as proof, but can't find any handy software helpful so I gave up. |
|||
| #766 | wontfix | Documentation/Manual changes for host interfaces/6.5 | ||
| Description |
I'd suggest two fixes for the current (as of this writing) UserManual, both apply to section 6.5: The scripts should imo be changed to something similar to the examples below, because
TapUp script#!/bin/sh # Create an new TAP interface for the user .vbox. and remember its name. interface=`sudo /opt/VirtualBox/VBoxTunctl -u virtualbox -b` # If for some reason the interface could not be created, return 1 to # tell this to VirtualBox. if [ -z "$interface" ]; then exit 1 fi # Write the name of the interface to the standard output. echo $interface # Bring up the interface. sudo /sbin/ifconfig $interface up # And add it to the bridge. sudo /sbin/brctl addif br0 $interface TapDown script#!/bin/sh # Remove the interface from the bridge. The second script parameter is # the interface name. echo "Removing interface $2" sudo /sbin/brctl delif br0 $2 # And use VBoxTunctl to remove the interface. sudo /opt/VirtualBox/VBoxTunctl -u virtualbox -d $2 Sudoers configuration file# Permissions needed to create the vm interface virtualbox ALL=(ALL) NOPASSWD: /opt/VirtualBox/VBoxTunctl -u virtualbox -b virtualbox ALL=(ALL) NOPASSWD: /sbin/ifconfig tap? up virtualbox ALL=(ALL) NOPASSWD: /sbin/ifconfig tap?? up virtualbox ALL=(ALL) NOPASSWD: /sbin/brctl addif br0 tap? virtualbox ALL=(ALL) NOPASSWD: /sbin/brctl addif br0 tap?? # Permissions needed to destroy the vm interface virtualbox ALL=(ALL) NOPASSWD: /opt/VirtualBox/VBoxTunctl -u virtualbox -d tap? virtualbox ALL=(ALL) NOPASSWD: /opt/VirtualBox/VBoxTunctl -u virtualbox -d tap?? virtualbox ALL=(ALL) NOPASSWD: /sbin/brctl delif br0 tap? virtualbox ALL=(ALL) NOPASSWD: /sbin/brctl delif br0 tap?? |
|||
| #768 | fixed | Mouse driver conflict -> Fixed in 2.2.2 | ||
| Description |
I have tested this with the official 1.5.0 build (VirtualBox_1.5.0_Linux_amd64.run) and a build from today (http://virtualbox.org/download/testcase/VirtualBox-2007-10-11-12-32-37-lin64-rel.run), with their respective guest additions. My setup:
This setup works perfectly until I install the Logitech mouse driver software, "SetPoint", when running Windows XP natively (and after a reboot). After that, whenever I run winxp in virtualbox, the mouse shows the following behavior:
I have failed to correct this problem by uninstalling SetPoint or guest additions. The only way is to bring the mouse pointer back to a normal state in the VM is to re-install Windows. I have found few reports of this, except maybe the "mouse pointer stuck in left corners of the screen" kind of deal, except this:
relevant hardware/software:
|
|||

