rhythmbox crashed with SIGSEGV

Bug #1061448 reported by Merelin on 2012-10-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)

Bug Description

Description: Ubuntu quantal (development branch)
Release: 12.10

  Installed: 2.97-1ubuntu5
  Candidate: 2.97-1ubuntu5
  Version table:
 *** 2.97-1ubuntu5 0
        500 http://archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
        100 /var/lib/dpkg/status

rhythbox is expected to work but crashes with SIGSEGV

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: rhythmbox 2.97-1ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-16.24-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Oct 4 11:58:13 2012
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1)
ProcCmdline: rhythmbox
 PATH=(custom, user)
SegvAnalysis: Failure: 'dx'
Signal: 11
SourcePackage: rhythmbox
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/librhythmbox-core.so.6
 ?? () from /usr/lib/librhythmbox-core.so.6
 ?? () from /usr/lib/librhythmbox-core.so.6
Title: rhythmbox crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Merelin (merelin) wrote :
visibility: private → public

 ?? ()
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x7fd88c5e6320, hash_table=0x3061120) at /build/buildd/glib2.0-2.34.0/./glib/ghash.c:401
 g_hash_table_remove_internal (hash_table=0x3061120, key=0x7fd88c5e6320, notify=1) at /build/buildd/glib2.0-2.34.0/./glib/ghash.c:1269
 remove_child (data=data@entry=0x7fd88c5e6320, parent=<error reading variable: Unhandled dwarf expression opcode 0xfa>) at rhythmdb-tree.c:1517
 remove_entry_from_album (db=db@entry=0x1f2c270, entry=entry@entry=0x7fd88c5e6320) at rhythmdb-tree.c:1538

Changed in rhythmbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers