compiz crashed with SIGABRT while changing external monitor configuration

[Bryce Harrington]

Was messing around with screen configuration to diagnose bug #887046, and compiz crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.6+bzr20110929-0ubuntu8
ProcVersionSignature: Ubuntu 3.2.0-2.6-generic-pae 3.2.0-rc3
Uname: Linux 3.2.0-2-generic-pae i686
.tmp.unity.support.test.0:

ApportVersion: 1.90-0ubuntu1
Architecture: i386
CompizPlugins: [core,bailer,detection,composite,opengl,decor,imgpng,gnomecompat,regex,place,snap,vpswitch,mousepoll,grid,compiztoolbox,animation,move,session,resize,unitymtgrabhandles,workarounds,wall,expo,fade,ezoom,scale,unityshell]
CompositorRunning: compiz
Date: Thu Dec 15 12:18:04 2011
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Limited. Device [10cf:1458]
   Subsystem: Fujitsu Limited. Device [10cf:1458]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111121)
MachineType: FUJITSU LifeBook T4410
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-generic-pae root=UUID=74b73169-6ac4-4698-bb5e-1f9b21250507 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: compiz
Stacktrace:
 #0 0xb7731424 in ?? ()
 No symbol table info available.
 #1 0x00000000 in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? ()
 ?? ()
Title: compiz crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev root sambashare
dmi.bios.date: 09/30/2009
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.05
dmi.board.name: FJNB206
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: A40R8CE708EA1001
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.05:bd09/30/2009:svnFUJITSU:pnLifeBookT4410:pvr:rvnFUJITSU:rnFJNB206:rvr:cvnA40R8CE708EA1001:ct10:cvr:
dmi.product.name: LifeBook T4410
dmi.sys.vendor: FUJITSU
version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu8
version.libdrm2: libdrm2 2.4.27-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.10.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

[Apport retracing service (apport)]

Stacktrace:
 #0 0xb7731424 in ?? ()
 No symbol table info available.
 #1 0x00000000 in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? ()
 ?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for compiz-plugins-main-default: package version 1:0.9.6-0ubuntu4 dbgsym version 1:0.9.6-0ubuntu4.1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[Bryce Harrington (bryce)]

Interesting!

So, the processing of this bug report highlights several flaws in the processors:

First, version 1:0.9.6-0ubuntu4.1 of compiz-plugins-main-default is not included in Precise (indeed, the SRU for including it in oneiric is blocked *because* the fix isn't in precise yet.) So the tracer should not have rejected the report based on this.

Second, version 1:0.9.6-0ubuntu4.1 of compiz-plugins-main-default includes two bug fixes neither of which have to do with crashes, so this crash report is still valid.

Third, for whatever reason, apport was unable to produce a valid trace. Perhaps this is due to something related to the first issue.

Fourth, the core file has been deleted, even though I set the bug report to public when I filed it (the machine is a test box with no private data). If apport is unable to create a trace from a core dump on a public bug, it should not delete the core dump; again that just hides information which could be useful in tracking down the problem.

[Bryce Harrington (bryce)]

Ok, the crash itself was a dupe of bug 838128.

I've pinged Martin about the processing issues in case he's interested in investigating, but otherwise this can just be duped.