rhythmbox-metadata crashed with SIGSEGV in _start()

Bug #820601 reported by J
498
This bug affects 80 people
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Expired
Medium
Unassigned

Bug Description

none

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: rhythmbox 2.90.1~20110802-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-7.9-generic-pae 3.0.0
Uname: Linux 3.0.0-7-generic-pae i686
Architecture: i386
CrashCounter: 1
Date: Wed Aug 3 18:20:09 2011
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
SegvAnalysis:
 Segfault happened at: 0x804e538 <_start+2108>: cmp %eax,0x4(%ebx)
 PC (0x0804e538) ok
 source "%eax" ok
 destination "0x4(%ebx)" (0x00000005) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: rhythmbox
Stacktrace:
 #0 0x0804e538 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 admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
J (jsartti) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 connection_closed_cb (connection=0xa084840, svc=0x1) at rb-metadata-dbus-service.c:216
 ffi_call_SYSV () at ../src/x86/sysv.S:64
 ffi_call (cif=0xbf9127e0, fn=0x804e500 <connection_closed_cb>, rvalue=0xbf912790, avalue=0xbf912750) at ../src/x86/ffi.c:303
 g_cclosure_marshal_generic (closure=0xb6301458, return_gvalue=0x0, n_param_values=3, param_values=0xb6301cd0, invocation_hint=0xbf912910, marshal_data=0x0) at /build/buildd/glib2.0-2.29.14/./gobject/gclosure.c:1146
 g_closure_invoke (closure=0xb6301458, return_value=0x0, n_param_values=3, param_values=0xb6301cd0, invocation_hint=0xbf912910) at /build/buildd/glib2.0-2.29.14/./gobject/gclosure.c:773

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in rhythmbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Changed in rhythmbox (Ubuntu):
status: New → Confirmed
tags: added: bugpattern-needed
Daniel Hahler (blueyed)
visibility: private → public
Revision history for this message
BertN45 (lammert-nijhof) wrote :

It crashed when I was quiting Rhytmbox while it was scanning the music library on a windows share.

tags: added: precise
Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

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.

Changed in rhythmbox (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in rhythmbox (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.