compiz segfaulted during restart of Alternate OEM Install

[Charlie Kravetz]

Binary package hint: compiz

RELEASE: Natty Narwhal Alpha2 pre-release
CD/DVD VARIANT: 32bit Ubuntu Alternate cd
ISO BUILD: 20110201.2

SYMPTOMS:
After completing the Alternate OEM installation, I restarted the computer. During the restart, compiz crashes before the GDM login screen.

STEPS TO REPRODUCE:

1. Install as instructed by http://testcases.qa.ubuntu.com/Install/AlternateOem
2. Restart at end of installation
3. Can not report a bug using apport, since the GUI won't start
4. Can not report the bug from the command line

I am attaching the generated crash report from /var/crash along with the /var/log/syslog.

[Charlie Kravetz (cjkgeek)]

Segfault from the syslog:

Feb 3 08:31:12 justhaveto gnome-session[1124]: WARNING: Could not launch application 'libcanberra-login-sound.desktop': Unable to start application: Failed to execute child process "/usr/bin/canberra-gtk-play" (No such file or directory)
Feb 3 08:31:25 justhaveto kernel: [ 71.103147] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro,commit=0
Feb 3 08:31:35 justhaveto kernel: [ 81.249210] compiz[1435]: segfault at 44 ip 07ce1752 sp bff391d0 error 4 in libnux-graphics-0.9.so.0.914.4[7c53000+c5000]
Feb 3 08:33:06 justhaveto kernel: [ 172.339146] [drm:subconnector_show] *ERROR* Unable to find subconnector property
Feb 3 08:33:06 justhaveto kernel: [ 172.339250] [drm:select_subconnector_show] *ERROR* Unable to find select subconnector property
Feb 3 08:33:06 justhaveto kernel: [ 172.350273] [drm:subconnector_show] *ERROR* Unable to find subconnector property
Feb 3 08:33:06 justhaveto kernel: [ 172.350367] [drm:select_subconnector_show] *ERROR* Unable to find select subconnector property

[Jean-Baptiste Lallement (jibel)]

Thanks for your report.

There has been many updates in compiz and nux since Alpha 2, are you able to reproduce it with Natty Beta 2 ?

[Charlie Kravetz (cjkgeek)]

I am no longer able to reproduce this issue. It appears to have been fixed. As the original reporter, I am closing this report as invalid. If someone can reproduce this, the report can be re-opened by changing the status above to "New".