rhythmbox-metadata crashed with SIGSEGV in memcpy()

Bug #397571 reported by teJECSke
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: rhythmbox

no comment

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Jul 9 21:51:34 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
NonfreeKernelModules: nvidia
Package: rhythmbox 0.12.2-0ubuntu2
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-2.16-generic
SegvAnalysis:
 Segfault happened at: 0x52d79f6 <memcpy+70>: rep movsl %ds:(%esi),%es:(%edi)
 PC (0x052d79f6) ok
 source "%ds:(%esi)" (0xb71ae07b) not located in a known VMA region (needed readable region)!
 destination "%es:(%edi)" (0xb6c9d07b) ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 memcpy () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 gst_buffer_span () from /usr/lib/libgstreamer-0.10.so.0
 ?? () from /usr/lib/gstreamer-0.10/libgstbluetooth.so
 ?? () from /usr/lib/libgstreamer-0.10.so.0
Title: rhythmbox-metadata crashed with SIGSEGV in memcpy()
Uname: Linux 2.6.31-2-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
teJECSke (attila-jecs) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

the crash is due to libgstbluetooth.so

affects: rhythmbox (Ubuntu) → bluez-gnome (Ubuntu)
Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

rassigning to the right component

affects: bluez-gnome (Ubuntu) → bluez (Ubuntu)
Revision history for this message
Mario Limonciello (superm1) wrote :

Unfortunately the stack trace in this bug is no good for debugging purposes. If this happens again, please refile and hopefully a good trace will be attached.

Changed in bluez (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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