rhythmbox-metadata crashed with SIGSEGV in g_type_check_value()

Bug #919517 reported by Michael Kowalchuk
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gstreamer0.10 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

First launch of Rhythmbox since upgrading to Precise - got a couple of these crash reports while it was scanning my collection.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libgstreamer0.10-0 0.10.35.2-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0
Uname: Linux 3.2.0-8-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Fri Jan 20 22:47:18 2012
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
SegvAnalysis:
 Segfault happened at: 0x7f1223b3a3d4 <g_type_check_value+52>: testb $0x8,0x16(%rbx)
 PC (0x7f1223b3a3d4) ok
 source "$0x8" ok
 destination "0x16(%rbx)" (0x500000036) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gstreamer0.10
StacktraceTop:
 g_type_check_value () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 gst_value_init_and_copy () from /usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
 gst_structure_copy () from /usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-0.10.so.0
Title: rhythmbox-metadata crashed with SIGSEGV in g_type_check_value()
UpgradeStatus: Upgraded to precise on 2012-01-15 (5 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
Michael Kowalchuk (michael-kowalchuk) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gstreamer0.10 (Ubuntu):
status: New → Confirmed
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.