Custom Query (16363 matches)
Results (1330 - 1332 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7849 | obsolete | typo in German localisation | ||
| Description |
In the German localisation the mandatory comma closing the "Erweiterter Infinitiv" is missing, when creating a VM: Wählen Sie Weiter, um auf die nächste Seite zu gelangen [ PLACE THE COMMA HERE ] oder Zurück, um .... |
|||
| #7851 | obsolete | VM resolution reported incorrectly on asymmetric multihead system | ||
| Description |
Ubuntu maverick host, with three physical desktops (ie, non-Xinerama) on two adapters. Desktops #1 and #3 are 1280x1024, but desktop #2 is 1920x1200. Windows 7 guest running on the large desktop #2 reports maximum resolution of 1280x1024 when resized or fullscreened. Interestingly, it resizes properly when the VM window is maximized. |
|||
| #7852 | obsolete | Ignored session becomes unresponsive white window | ||
| Description |
Preliminaries: Vbox 3.2.12 on Vista64 host, Solaris 11 Express build 151a + Guest Additions, HP w/AMD quad processor, 8GB RAM. Once again I've encountered a white screen of silence on my Solaris 11 Express guest. The attached files are the VBox.log, Solaris 11 messages, a screen capture of the Vista64 Task Manager showing the VirtualBox process hogging one of my four processors, and (just for grins) a screen capture of part of the white screen of silence... I also have an SSH session into the guest, which is not hung as previously thought and not busy at all. Although Vista64 shows the VirtualBox process consuming an entire processor, Solaris in the guest is idle. Wreckdangle:/export/home/aimone [root] (774)> prstat -c -n 5 1 3 Please wait...
Total: 111 processes, 639 lwps, load averages: 0.06, 0.06, 0.06
Total: 111 processes, 639 lwps, load averages: 0.06, 0.06, 0.06
Total: 111 processes, 639 lwps, load averages: 0.06, 0.06, 0.06 Wreckdangle:/export/home/aimone [root] (775)> If this were a /normal/ Xorg issue as I've seen in the past, then killing Xorg would have recovered the display. In this case killing Xorg does show some activity, the guest window changes size indicating what would normally be a reversion to a text console while Xorg is restarted, but actually this completely hangs the guest. The SSH session hangs implying that the guest itself is now hung. What other things can I do to help debug this problem? It has persisted across the last three VBox updates and several Solaris builds. |
|||

