Extreme screen corruption with latest updates in VirtualBox under Quantal

[Logan Rosen]

I just installed new updates earlier, and, after restarting the VM in VirtualBox, I am experiencing extreme screen corruption and general issues with windows/buttons popping in front/behind of each other. I'll attach screenshots.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic x86_64
.tmp.unity.support.test.1:

ApportVersion: 2.4-0ubuntu8
Architecture: amd64
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
Date: Sat Aug 18 15:22:57 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus: virtualbox-guest, 4.1.18, 3.5.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller])
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-10-generic root=UUID=e93afda7-8594-451c-9115-0a7b6d6d2c6a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz 1:0.9.8+bzr3249-0ubuntu4
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.38-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.904-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1

[Logan Rosen (logan)]

I just reported Bug 1038499 based on a crash report of compiz that came up.

[Logan Rosen (logan)]

...and Bug 1038500 for colord.

[Logan Rosen (logan)]

Screenshots: http://i.imgur.com/UYqrA.jpg http://i.imgur.com/QGyHD.jpg

[Logan Rosen (logan)]

Also, this is only happening in Unity. Not happening in Gnome Classic.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Anders Nor Berle (berle)]

This happens for me as well with VMware Fusion 4. With or without acceleration enabled.

[Omer Akram (om26er)]

adding a milestone in unity just for tracking this bug. Not sure if unity is where it needs fixing.

@Logan, in gnome classic if you start compiz (without unity) what's the situation then?

[Daniel van Vugt (vanvugt)]

If your VMs are falling back to LLVMpipe (no guest extensions/graphics driver) then this is bug 1021104.

To confirm, please run:
    glxinfo | grep OpenGL
And paste the output here.

[Logan Rosen (logan)]

logan@logan-VirtualBox:~$ glxinfo | grep OpenGL
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x300)
OpenGL version string: 2.1 Mesa 8.0.4
OpenGL shading language version string: 1.20
OpenGL extensions:

[Daniel van Vugt (vanvugt)]

Thanks Logan. That confirms this is bug 1021104.

[Raymond Wells (rfw2nd)]

Something similar happens to me as well on bare metal. I'm using fglrx-legacy PPA, which could be part of the issue, but the bug I'm getting looks very similar to that.