Compiz driven ubiquity-dm crashes when booting raring

[Para Siva]

Booting to live session with on a VM leads to a black blank screen with just the top bar. The window to select whether to try ubuntu or install it never comes up. So far, this has only been reproducible in VMs, but only a few pieces of hardware have been tried. This seems to have started around the time metacity was switched out for compiz.

Steps:
1. Boot to the live sesion on a vm raring desktop iso
(This bug can be reproduced in both kvm as well as virtualbox)
2. It can be seen that the screen is shown as the screenshot attached.
-- or --
1. Press a key at the boot screen, and select "Install Ubuntu"

Attached is a compiz crash found in /var/crash which may or may not be related.
( Running ubuntu-bug on the crash failed to report the bug)

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: compiz 1:0.9.8.4+bzr3412-0ubuntu1
ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7
Uname: Linux 3.7.0-4-generic x86_64
.tmp.unity.support.test.1:

ApportVersion: 2.6.3-0ubuntu2
Architecture: amd64
CasperVersion: 1.329
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Mon Dec 3 16:28:47 2012
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
GraphicsCard:
 Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc Device [1af4:1100]
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121203)
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Bochs Bochs
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
SourcePackage: compiz
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2007
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.40-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.14-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1
xserver.bootTime: Mon Dec 3 15:46:48 2012
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input AT Translated Set 2 keyboard KEYBOARD, id 7
 input ImExPS/2 Generic Explorer Mouse MOUSE, id 8
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.13.0-0ubuntu8

[Para Siva (psivaa)]

Further logs are attached as log.tar.gz

[Paul Larson (pwlars)]

I can confirm that this also happens in virtualox. With a dell laptop, using the amd64 image, I do not see the compiz crash, and I'm able to successfully boot to the desktop.

[Paul Larson (pwlars)]

If I take the same image (amd64 or amd64+mac) on virtualbox and enable 3d acceleration under display properties, I'm able to boot up to the live desktop.

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1060327, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

[Paul Larson (pwlars)]

Daniel, can you explain why this was duped to bug #1060327? That bug is 2 months old, and this is a new bug that seems to have just started in the last couple of days. While it may be possible that the compiz issue is the same as in this other bug, and may be unrelated to the other symptoms, I believe the issue stated in the description does not match what was happening in that earlier bug.

[Daniel van Vugt (vanvugt)]

Paul,

The .crash file shows a stack trace (search for "Stacktrace:") that is identical to bug 1060327. Hence it is bug 1060327.

[Gema Gomez (gema)]

We don't think this bug is a duplicate.

[Paul Larson (pwlars)]

I can confirm that this broke sometime between the 20121129 and 20121202 image if that helps. I don't have the interim images handy at the moment but if I can dig them up somewhere, I'll try to test with those as well. Hopefully this gives a starting place to look though.

[Paul Larson (pwlars)]

After talking to didrocks and xnox today, psivaa and I were both able to confirm that killing X and restarting lightdm brings up the proper ubiquity-dm session and let's you pick whether to install or try ubuntu.

[Launchpad Janitor (janitor)]

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

[Jackson Doak (noskcaj)]

if you didn't know, all that was achieved on my copy of the bug (the older one) is that you can workaround the problem by selecting "try ubuntu without installing" from the cli menu then using the install link on the desktop.

[Daniel van Vugt (vanvugt)]

I have checked the stacks again. It is a duplicate of bug 1060327. Please trust me as Compiz maintainer on this one. And if you don't, ask some other developer to compare the stack traces.