Custom Query (16363 matches)
Results (838 - 840 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #6248 | obsolete | sloppy mouse focus broken in e17 since 3.1.x | ||
| Description |
In virtualbox 3.0.x there's no problem, but in 3.1.x the problem exists: (sloppy focus with autoraise) If I have the mouse pointer over one window and do an ALT-TAB to switch window the focus switches, (the pointer doesn't move) and when I press any key the press-event goes to the focused window and then the focus switches to the window under the pointer. This makes ALT-TAB unusable if the pointer is on top of any window (if the pointer is on the desktop the focus does not switch). I'm attaching xev.txt which contains xev output from when I start xev (all new windows get focus) on 3.1.4 and press the letter 'a' while having the pointer on the terminal which starts xev. Xev only receives the keypress, not the keyrelease, and immediately a focus out event. Also attaching xev2.txt which contains the same procedure on VB version 3.0.12; here we can see that xev receives the keypress event, the release event and an ALT-TAB is required to get to the focusout event. This is on Debian unstable with e17 from svn, I've had this issue since the first 3.1 version came out, and I've tried all 3.1.x versions, but each time I've had to go back to virtualbox 3.0.x to have a functional alt-tab. Btw I've tested this in vmware too and there's no issue there. |
|||
| #12890 | obsolete | sleep in check_running in routines.sh is too short | ||
| Description |
I'm running Slackware 14.1 with kernel 3.10.17 and tried to upgrade to VirtualBox 4.3.10. The installer kept saying that VirtualBox was currently running and I needed to close it to continue. I confirmed no VMs were running and that the balloon and web services were stopped. I unloaded the kernel modules and confirmed that they were unloaded. I even commented out the start-up scripts and restarted. Still it would give this error. I unpacked the installer and looked things over. Ultimately I found that check_running() in routines.sh was not waiting long enough on the sleep. On my system, one second is not long enough for everything to clear before the if statement runs. I changed this to sleep 5 and the installer runs perfectly. Could the sleep command be changed to "sleep 5" instead of "sleep 1"? It might help others get VirtualBox installed on their Linux system. |
|||
| #4074 | fixed | slackware64 (64bit) guest hangs slackware (32bit) host during installation | ||
| Description |
Running Virtualbox 2.2.2 on slackware linux (32bit) and tried to install slackware64 (64bit) as guest. The Intel VT-x is enabled. I've read about the 64-bit guest section in the UserManual?.pdf. I've also tried to install RHEL5.2 (64bit) guest. Almost the same issue, the host become non-responsive (hang), some times the host auto-reboot, after the guest installation loaded initrd.img. The VBox.log file is located at <http://www.virtualbox.org/attachment/ticket/3927/VBox.slackware64.log> Thanks! |
|||

