rhythmbox-metadata crashed with SIGSEGV in g_type_check_value()

Bug #839243 reported by alkafer
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

luego de instalar me envio un mensaje al ingresar la musica, pero aun siguio funcionando

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: rhythmbox 2.90.1~20110802-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Thu Sep 1 23:40:55 2011
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
SegvAnalysis:
 Segfault happened at: 0x329c30 <g_type_check_value+64>: testb $0x8,0xe(%esi)
 PC (0x00329c30) ok
 source "$0x8" ok
 destination "0xe(%esi)" (0xdc9cb5b2) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 g_type_check_value () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 gst_value_init_and_copy () from /usr/lib/libgstreamer-0.10.so.0
 gst_structure_copy () from /usr/lib/libgstreamer-0.10.so.0
 ?? () from /usr/lib/libgstreamer-0.10.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: rhythmbox-metadata crashed with SIGSEGV in g_type_check_value()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
alkafer (ackerdfeld) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #838193, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
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.