sushi-start crashed with SIGSEGV in pthread_mutex_lock()

[Alfredo Baeza]

I can't open sushi. This is the console output if I try to open it manually:

alfredo@Matrix:~$ sushi

Gtk-WARNING **: Theme parsing error: gtk-style.css:13:14: Not using units is deprecated. Assuming 'px'.

Gtk-WARNING **: Theme parsing error: gtk-style.css:40:20: Not using units is deprecated. Assuming 'px'.

Gtk-WARNING **: Theme parsing error: gtk-style.css:50:19: Not using units is deprecated. Assuming 'px'.

Gtk-WARNING **: Theme parsing error: gtk-style.css:81:14: Not using units is deprecated. Assuming 'px'.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-sushi 0.2.1-2
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 23 19:44:04 2012
ExecutablePath: /usr/lib/gnome-sushi/sushi-start
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120125)
ProcCmdline: /usr/lib/gnome-sushi/sushi-start
SegvAnalysis:
 Segfault happened at: 0x7f89c00e7e84 <pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7f89c00e7e84) ok
 source "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-sushi
StacktraceTop:
 pthread_mutex_lock () from /lib/x86_64-linux-gnu/libpthread.so.0
 XrmQGetResource () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XGetDefault () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
Title: sushi-start crashed with SIGSEGV in pthread_mutex_lock()
UpgradeStatus: Upgraded to precise on 2012-01-31 (23 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #931381, 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.