Custom Query (16363 matches)
Results (1087 - 1089 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #356 | fixed | Last xserver-xorg-core makes X crash with VBoxVideo (fix will be in 1.4.2) | ||
| Description |
System: VirtualBox 1.3.8 on Ubuntu Feisty Fawn 7.04 Guest operating system: Ubuntu Gutsy Gibbon 7.10 with latest updates Problem: After the last update in Ubuntu 7.10 (Gutsy Gibbon) X doesn't start anymore with vboxvideo driver, need to use vesa. The update which created the problem is: xserver-xorg-core-2:1.3.0.0.dfsg-4ubuntu1 X crash with VBoxVideo but works with Vesa. xorg log of crash is here: http://img412.imageshack.us/img412/1032/vboxvideodj9.png |
|||
| #12166 | fixed | VBoxClient does not startup because of permissions in /opt/VBoxGuestAdditions-X.X.X directory (bug + fix found) -> fixed as of 22 October 2013 (4.1 branch and later) | ||
| Description |
My symptom was that I could not cut and paste between my host and guest, even though I selected bidirectional clipboard. I confirmed bidirectional clipboard was turned on correctly through VBox.log on the Windows host. My Linux client is Scientific Linux 6.4, which is nearly exactly RHEL 6.4 (up to date). VirtualBox version is 4.2.18 There were no VBoxClient processes running and /usr/bin/VboxClient pointed to an unreadable path. I found that the /opt/VBoxGuestAdditions-4.2.18/ did not have read or execute permissions open for unprivileged users. The problem persisted after I uninstalled the guest additions, deleted /opt/VBox*, rebooted, and reinstalled guest permissions. The problem was fixed when I changed the permissions on /opt/VBoxGuestAdditions-4.2.18/ to allow read+exec for general users. After a reboot, the VBoxClient processes were running normally and clipboard worked. Furthermore I no longer have to do "xrandr -s 0" every time I resize the guest window. This appears to be a regression from ticket #10832 which showed other problems from an /opt/ permissions problem which was supposedly fixed, but has reoccurred in my environment. It should be an easy fix in the installer, but this problem bugged me for weeks until I found the problem. cheers |
|||
| #5596 | fixed | Low resolution scaling in full screen mode | ||
| Description |
When running games such as starcraft (and very likely any game set to a lower resolution then the screen's potential), virtualbox fails to scale the image up to fullscreen in full screen mode. Game (or application at hand) remains in a smaller window (at it's running resolution) without scaling up to full screen as it should in these situations. The remaining space is occupied by black borders surrounding said application. |
|||

