rhythmbox crashed with SIGSEGV in g_closure_invoke()

[Ward Muylaert]

Binary package hint: rhythmbox

Ubuntu 10.10, latest version (ran an update 20 minutes or so ago).
Rhythmbox 0.13.0

rhythmbox:
  Installed: 0.13.0git20100715-0ubuntu6
  Candidate: 0.13.0git20100715-0ubuntu6
  Version table:
 *** 0.13.0git20100715-0ubuntu6 0
        500 http://be.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages
        100 /var/lib/dpkg/status

Happened twice after closing down rhythmbox, it seems to close down (no window left), but then I get an indication that the application crashed.
What I do in rhythmbox doesn't seem to matter. The first time I had briefly played a built-in radio station, the second time had done absolutely nothing.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: rhythmbox 0.13.0git20100715-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
Uname: Linux 2.6.35-15-generic i686
Architecture: i386
Date: Tue Aug 17 00:23:32 2010
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
ProcCmdline: rhythmbox
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xafcb0f35: mov 0x30(%esi),%eax
 PC (0xafcb0f35) ok
 source "0x30(%esi)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/libindicate.so.4
 ?? () from /usr/lib/libdbus-glib-1.so.2
 ?? () from /usr/lib/libdbus-glib-1.so.2
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: rhythmbox crashed with SIGSEGV in g_closure_invoke()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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.

[Pedro Villavicencio (pedro)]

could be a libindicate issue.

[Ward Muylaert (ward-muylaert)]

Did the backtrace as requested, it mentioned a segfault from libindicate yes:

Program received signal SIGSEGV, Segmentation fault.
0x03567f35 in ?? () from /usr/lib/libindicate.so.4

Hope that is what you needed, anything else I can do?

[Sebastien Bacher (seb128)]

The crash is a libindicate one

[Ted Gould (ted)]

Pedro, why did you remove the need retrace tag? I think this really does need a retrace to be useful as we need to know the symbol names.

[Pedro Villavicencio (pedro)]

Because the retracers are broken and we're asking the reporters to do that by hand for now.

[Sebastien Bacher (seb128)]

Karl, could you try to figure what is wrong there?

[Launchpad Janitor (janitor)]

This bug was fixed in the package libindicate - 0.4.1-0ubuntu3

---------------
libindicate (0.4.1-0ubuntu3) maverick; urgency=low

  * Backport the commit fixing rhythmbox crashing on exit (lp: #618944)
  * debian/control: don't build-depends on gir-repository-dev
 -- Sebastien Bacher <email address hidden> Wed, 08 Sep 2010 11:51:50 +0200