rhythmbox crashed with SIGSEGV in g_closure_invoke()

[Luke Symes]

Binary package hint: rhythmbox

I think I was browsing DAAP shares, then went back to my library. I tried to quit Rhythmbox, but it didn't close, and was otherwise responsive. After xkill'ing it, apport fired up this report.

Rhythmbox 0.12.7-0ubuntu7

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 23 10:16:14 2010
Disassembly: => 0xa0d29: Cannot access memory at address 0xa0d29
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
NonfreeKernelModules: wl nvidia
Package: rhythmbox 0.12.7-0ubuntu7
ProcCmdline: rhythmbox
ProcEnviron:
 LANG=en_NZ.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0xa0d29: Cannot access memory at address 0xa0d29
 PC (0x000a0d29) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: rhythmbox crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

[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)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.