Custom Query (16363 matches)
Results (1903 - 1905 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1951 | fixed | Ubuntu 8.04 host, Windows XP guest, video screen gets corrupted | ||
| Description |
For no apparent, repeatable reason, the video screen turns mostly black with colored sprinkles (kind of pretty, actually, but useless ;-{) The result is that VB is locked and a reboot is required. Usually the corruption occured as I was moving the mouse over a window boundary in the XP guest, say from Outlook to Firefox. This happens within the first 15 minutes of trying to use the virtual XP guest. Host: roberts@igor:~$ uname -a Linux igor 2.6.24-19-generic #1 SMP Fri Jul 11 21:01:46 UTC 2008 x86_64 GNU/Linux roberts@igor:~$ --Doug |
|||
| #1952 | fixed | Starting a VM turns DPMS off in X. | ||
| Description |
This is in VB-OSE 1.6.2, Debian sid package (1.6.2-dfsg-4).
Before a VM starts, DPMS (Energy Star): Standby: 0 Suspend: 0 Off: 600 DPMS is Enabled Monitor is On Once the VM is started: DPMS (Energy Star): Standby: 0 Suspend: 0 Off: 600 DPMS is Disabled This is the same whether the VM starts (was last stopped) in seamless mode or not. Then once the VM is stopped, DPMS comes back. I can also re-enable it manually after the VM starts, so this is only an issue when I forget and the screen stays on without reason. |
|||
| #1953 | fixed | Segmentation fault on Ubuntu AMD64 with VRDP external authentication -> Fixed in 1.6.6 | ||
| Description |
I'm running VBox 1.6.4 on Ubuntu desktop 8.04.1 AMD64 updated @ Aug 13 2008. I've enabled auth logging with export VRDP_AUTH_DEBUG_FILENAME=/home/vbox/log I started VM with VBoxHeadless -s dev & and in log I obtained: u[vbox], d[dev2.lan], p[4] vrdpauth_pam_init: dlopen libpam.so failed vrdpauth_pam_init failed 4 I made ln -s /lib/libpam.so.0 /lib/libpam.so, and it worked u[vbox], d[dev2.lan], p[4] init ok Using PAM service: vrdpauth start ok conv: num 1 u[vbox] p[4] conv: 0 returning password [4] auth ok access granted vrdpauth_pam_close completed After this I tried unhautorized userid/pwd, and I got segmentation faults [1]+ Segmentation fault VBoxHeadless -s dev in all casese below: u[leo], d[], p[0] init ok Using PAM service: vrdpauth start ok conv: num 1 u[leo] p[0] conv: 0 returning password [0] u[leo], d[], p[6] init ok Using PAM service: vrdpauth start ok conv: num 1 u[leo] p[6] conv: 0 returning password [6] u[vbox], d[], p[0] init ok Using PAM service: vrdpauth start ok conv: num 1 u[vbox] p[0] conv: 0 returning password [0] In other words , if user is allowed, all is ok, but if user si NOT allowed the VM crashes with segmenattion fault. It looks a Virtualbox bug. p.s. I rebooted whole system, and now I get segfault even for authorized userid/passwords. |
|||

