rhythmbox-metadata crashed with SIGSEGV in g_type_check_value()

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

Bug Description

Rhythmbox crashed several times after adding new files to my library

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: rhythmbox 2.97-1ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Wed Sep 5 19:55:16 2012
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120724.2)
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f690b4513d8 <g_type_check_value+56>: testb $0x8,0x16(%rbx)
 PC (0x7f690b4513d8) ok
 source "$0x8" ok
 destination "0x16(%rbx)" (0x7f6800000016) 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/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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Robert (robert-giacinto) 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.