rhythmbox-metadata crashed with SIGSEGV in g_type_check_value()

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

Bug Description

This happened while rhythmbox was doing an initial import of my music into its database.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: rhythmbox 2.97-1ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic x86_64
ApportVersion: 2.4-0ubuntu8
Architecture: amd64
Date: Fri Aug 17 07:15:48 2012
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803)
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=nl_NL.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7feefa168ed9 <g_type_check_value+105>: mov (%rax),%rax
 PC (0x7feefa168ed9) ok
 source "(%rax)" (0x00000050) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
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 quantal on 2011-12-03 (257 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv pcscd plugdev sambashare video wireshark

Revision history for this message
Martijn vdS (martijn) 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 this software better. This particular crash has already been reported and is a duplicate of bug #838812, 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-amd64-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.