metacity crashed with SIGABRT in __kernel_vsyscall()

[salvam]

:(

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: metacity 1:2.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed Aug 31 13:15:56 2011
ExecutablePath: /usr/bin/metacity
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
ProcCmdline: metacity
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/false
 PATH=(custom, no user)
Signal: 6
SourcePackage: metacity
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
 ?? ()
Title: metacity crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: Upgraded to oneiric on 2011-08-30 (1 days ago)
UserGroups:

XsessionErrors:
 (polkit-gnome-authentication-agent-1:7401): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:7398): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (users-admin:7541): Liboobs-WARNING **: There was an unknown error communicating asynchronously with the backends: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
 (nautilus:7398): Eel-WARNING **: "unique eel_ref_str" hash table still has 3 elements at quit time (keys above)
 (nautilus:7398): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 3 elements at quit time

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #827452, so 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. Please continue to report any other bugs you may find.