Custom Query (16363 matches)
Results (214 - 216 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10583 | obsolete | Virtual Machine unresponsive after host returned from hiberation | ||
| Description |
I hibernated my host. When I resumed, the VirtualBox virtual machine was not responsive. To be precise, mouse inputs into the program with the focus were processed, but I was unable to click on any other programs, or use the keyboard at all. I managed to SSH into the machine to retrieve the kernel messages indicating something wrong with VBoxService. Host is Windows 7 64-bit, guest is Linux 3.2. |
|||
| #10584 | fixed | 3d acceleration does not work with 4.1.4 additions | ||
| Description |
When running VirtualBox 4.1.4 with Debian (Linux 3.2) and the 4.1.4 guest additions, no program is able to use OpenGL. e.g., $ glxinfo Error: couldn't find RGB GLX visual or fbconfig name of display: :0.0 Downgrading to the 4.1.12 guest additions (and Xorg 1.11) solves the problem. Host is Windows 7 64-bit. Graphics card is a Radeon HD 4890. Forwarded from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673437 since others cannot reproduce this bug in Debian. |
|||
| #10853 | invalid | Mouse position repeatedly reset to top and/or left of screen -> X.Org bug | ||
| Description |
The position of the mouse pointer, according to mouse integration, regularly warps to 0 on the X and/or Y axis. To reproduce, drag a window in circles. After a few seconds the window position will warp to the top and/or left of the screen. The position of the mouse pointer on screen is not affected. Continuing to move the mouse after this has happened will result in the window returning to its correct position.
If I reproduce this bug and then do not move the mouse, 2 classes : ButtonClass button[1]=up button[2]=up button[3]=up button[4]=up button[5]=up ValuatorClass Mode=Absolute Proximity=In valuator[0]=0 valuator[1]=2449
Note the value for motion a[0]=35390 motion a[1]=29287 motion a[1]=29225 motion a[0]=0 a[1]=0 motion a[0]=35468 motion a[1]=29163 motion a[1]=29100
If I run MotionNotify event, serial 38, synthetic NO, window 0x4e00001,
root 0x138, subw 0x0, time 1086667511, (68,100), root:(69,175),
state 0x0, is_hint 0, same_screen YES
LeaveNotify event, serial 38, synthetic NO, window 0x4e00001,
root 0x138, subw 0x0, time 1086667543, (-1,-75), root:(0,0),
mode NotifyNormal, detail NotifyNonlinear, same_screen YES,
focus YES, state 0
EnterNotify event, serial 38, synthetic NO, window 0x4e00001,
root 0x138, subw 0x0, time 1086667655, (70,99), root:(71,174),
mode NotifyNormal, detail NotifyNonlinear, same_screen YES,
focus YES, state 0
These motion events do not appear when I monitor the mouse devices directly. During the above pointer warp, Event: time 1345562934.153848, type 3 (EV_ABS), code 1 (ABS_Y), value 48074 Event: time 1345562934.153858, -------------- SYN_REPORT ------------ Event: time 1345562934.281761, type 3 (EV_ABS), code 1 (ABS_Y), value 48137 Event: time 1345562934.281770, -------------- SYN_REPORT ------------ Event: time 1345562934.321750, type 3 (EV_ABS), code 1 (ABS_Y), value 48199 Event: time 1345562934.321769, -------------- SYN_REPORT ------------ Event: time 1345562934.345782, type 3 (EV_ABS), code 1 (ABS_Y), value 48261 Event: time 1345562934.345788, -------------- SYN_REPORT ------------ Event: time 1345562934.521721, type 3 (EV_ABS), code 1 (ABS_Y), value 48324 Event: time 1345562934.521726, -------------- SYN_REPORT ------------ Event: time 1345562943.345890, type 3 (EV_ABS), code 0 (ABS_X), value 49824 Event: time 1345562943.345900, -------------- SYN_REPORT ------------ Event: time 1345562943.369481, type 3 (EV_ABS), code 0 (ABS_X), value 49863 Event: time 1345562943.369491, -------------- SYN_REPORT ------------
Note that the X/Y values adjust smoothly. I also ran This happens to me on two systems, both of which are Windows 7 64-bit hosts with Linux 3.2 and Xorg 1.12.3. I see this with both VirtualBox 4.1.18 and 4.1.20 on the host side. The guests both use the 4.1.18 additions. I also downgraded to the 4.1.16 additions but that didn't help. There is nothing out of the ordinary in the VM's log file, and the kernel doesn't log anything when this occurs either. It seems others have this problem too: |
|||

