rhythmbox-metadata crashed with SIGSEGV in g_type_check_value()

Bug #824702 reported by Josh Dalziel
96
This bug affects 22 people
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Apport says that it crash, but I never noticed a crash

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: rhythmbox 2.90.1~20110802-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-8.10-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
Architecture: amd64
Date: Thu Aug 11 11:04:46 2011
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f5a9ffbdcb4 <g_type_check_value+52>: testb $0x8,0x16(%rbx)
 PC (0x7f5a9ffbdcb4) ok
 source "$0x8" ok
 destination "0x16(%rbx)" (0xaaaaaaaaaaaaaabe) 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/libgstreamer-0.10.so.0
 gst_structure_copy () from /usr/lib/libgstreamer-0.10.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/libgstreamer-0.10.so.0
Title: rhythmbox-metadata crashed with SIGSEGV in g_type_check_value()
UpgradeStatus: Upgraded to oneiric on 2011-08-11 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Josh Dalziel (josh-dalziel) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 type_get_qdata_L (quark=17774536, node=0xaaaaaaaaaaaaaaa8) at /build/buildd/glib2.0-2.29.16/./gobject/gtype.c:3623
 type_check_is_value_type_U (type=<optimized out>) at /build/buildd/glib2.0-2.29.16/./gobject/gtype.c:4093
 g_type_check_is_value_type (type=<optimized out>) at /build/buildd/glib2.0-2.29.16/./gobject/gtype.c:4120
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in rhythmbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in rhythmbox (Ubuntu):
status: New → Confirmed
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

visibility: private → public
Changed in rhythmbox (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]

Changed in rhythmbox (Ubuntu):
status: Incomplete → Expired
jc1985 (jc1985)
Changed in rhythmbox (Ubuntu):
status: Expired → New
Revision history for this message
Vadim Rutkovsky (roignac) wrote :

Please, don't change status without comments. Original report should also provide required information for this bug to be accepted

Changed in rhythmbox (Ubuntu):
status: New → Incomplete
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.