metacity crashed with SIGABRT

[Eliah Kagan]

Binary package hint: metacity

On the Oneiric i386 20110619 [and 20110620] daily-live, metacity 1:2.34.0-0ubuntu1 crashed with SIGABRT yielding an apparently corrupt and possibly useless stack trace. This occurred shortly after the start of a unity-2d session, and also almost immediately after the first time I clicked on the Unity home button (above the launcher, on the upper-left corner of the screen). However, the places menu came up (that time, and also after subsequent clicks on the home button), and the crash did not recur when I clicked on that button later.

I suspect this is an instance bug 797078, but there is no good trace to confirm, and the presentation is possibly different, so I decided to file a separate report. The stack trace here is very bad, but perhaps Apport retracing service can process it into something useful (or, more likely, mark this Invalid).

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: metacity 1:2.34.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3
Uname: Linux 3.0-1-generic i686
Architecture: i386
Date: Mon Jun 20 06:29:46 2011
ExecutablePath: /usr/bin/metacity
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110619)
ProcCmdline: metacity --sm-disable
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: metacity
Stacktrace:
 #0 0x00451416 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfafa304
StacktraceTop: ?? ()
Title: metacity crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Stacktrace:
 #0 0x00451416 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xbfafa304
StacktraceTop: ?? ()

[Pedro Villavicencio (pedro)]

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Launchpad Janitor (janitor)]

[Expired for metacity (Ubuntu) because there has been no activity for 60 days.]