sushi-start crashed with SIGSEGV in mb_result_list_get_size()

Bug #927555 reported by Cristian Aravena Romero on 2012-02-06
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Sushi
Fix Released
Critical
gnome-sushi (Ubuntu)
Medium
Unassigned

Bug Description

I'm working with nautilus and crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-sushi 0.2.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
Uname: Linux 3.0.0-16-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Mon Feb 6 08:12:27 2012
ExecutablePath: /usr/lib/gnome-sushi/sushi-start
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
ProcCmdline: /usr/lib/gnome-sushi/sushi-start
SegvAnalysis:
 Segfault happened at: 0x7fb8a053f7e0 <mb_result_list_get_size>: mov 0x8(%rdi),%rax
 PC (0x7fb8a053f7e0) ok
 source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-sushi
StacktraceTop:
 mb_result_list_get_size () from /usr/lib/libmusicbrainz3.so.6
 ?? () from /usr/lib/libsushi-1.0.so.0
 io_job_thread (data=0x7fb898053660, user_data=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gio/gioscheduler.c:180
 g_thread_pool_thread_proxy (data=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gthreadpool.c:319
 g_thread_create_proxy (data=0x38e6540) at /build/buildd/glib2.0-2.30.0/./glib/gthread.c:1962
Title: sushi-start crashed with SIGSEGV in mb_result_list_get_size()
UpgradeStatus: Upgraded to oneiric on 2011-10-04 (124 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

StacktraceTop:
 mb_result_list_get_size () from /tmp/tmpnNo0Do/usr/lib/libmusicbrainz3.so.6
 fetch_uri_job (sched_job=0x7fb898053660, cancellable=<optimized out>, user_data=0x3a13700) at libsushi/sushi-cover-art.c:230
 io_job_thread (data=0x7fb898053660, user_data=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gio/gioscheduler.c:180
 g_thread_pool_thread_proxy (data=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gthreadpool.c:319
 g_thread_create_proxy (data=0x38e6540) at /build/buildd/glib2.0-2.30.0/./glib/gthread.c:1962

Changed in gnome-sushi (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Changed in gnome-sushi:
importance: Unknown → Medium
status: Unknown → New
Changed in gnome-sushi:
importance: Medium → Critical
Changed in gnome-sushi (Ubuntu):
status: New → Confirmed
Changed in gnome-sushi:
status: New → Fix Released
Changed in gnome-sushi (Ubuntu):
status: Confirmed → Triaged
status: Triaged → Fix Committed
Vadim Rutkovsky (roignac) wrote :

This bug has been fixed upstream, but not yet released in Ubuntu's repos.
Could somebody affected try to test latest Sushi from git (use ppa:roignac/gnome-sushi) and report back here?
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-sushi - 0.4.1-0ubuntu1

---------------
gnome-sushi (0.4.1-0ubuntu1) precise; urgency=low

  * New upstream release.
    - Fix a crash when fetching album cover art (LP: #927555)
    - Move the window to the current desktop workspace when shown
      (LP: #897559)
    - Avoid maximization and window snapping
    - Plug some memory leaks
  * debian/control.in: Bump minimum clutter to 1.10
  * debian/90-make-fullscreen-button-placement-consistent.patch:
    - Git patch to move evince-viewer's fullscreen button to the right
      like other viewers (LP: #896987)
  * debian/91-add-client-decorations-preference.patch:
    - Git patch to add gsettings option to use native window
      management buttons
  * debian/gnome-sushi.gsettings-override:
    - Use native window management buttons by default (LP: #876805,
      LP: #880262)
 -- Jeremy Bicha <email address hidden> Sat, 21 Apr 2012 23:48:30 -0400

Changed in gnome-sushi (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.