rhythmbox-metadata crashed with SIGSEGV in connection_closed_cb()

[Che Dean]

I had just shut Rhythmbox down when the crash happened. Using Ubuntu 12.04 LTS Beta1 with the latest updates installed. The only other application that was runnng was Gwibber. I shut down Rythmbox and immediately got a crash report.

Ubuntu 12.04 LTS Beta 1

Rhythmbox Version 2.95

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: rhythmbox 2.95-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
Date: Sat Mar 3 21:06:19 2012
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 LANGUAGE=en_IE:en
 PATH=(custom, no user)
 LANG=en_IE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4081a5 <_start+1937>: cmp %rbp,0x8(%rbx)
 PC (0x004081a5) ok
 source "%rbp" ok
 destination "0x8(%rbx)" (0x00000009) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: rhythmbox
Stacktrace:
 #0 0x00000000004081a5 in _start ()
 No symbol table info available.
StacktraceTop: _start ()
Title: rhythmbox-metadata crashed with SIGSEGV in _start()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 connection_closed_cb (connection=0x7ff54c003040, svc=0x1) at rb-metadata-dbus-service.c:216
 ffi_call_unix64 () at ../src/x86/unix64.S:75
 ffi_call (cif=0x7fff2f5acac0, fn=0x408170 <connection_closed_cb>, rvalue=<optimized out>, avalue=<optimized out>) at ../src/x86/ffi64.c:486
 g_closure_invalidate (closure=0x10) at /build/buildd/glib2.0-2.31.20/./gobject/gclosure.c:572
 ?? ()

[Walter Garcia-Fontes (walter-garcia)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]