rhythmbox crashed with SIGSEGV in rhythmdb_entry_set_internal()

Bug #274532 reported by goto
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Rhythmbox
Fix Released
Critical
rhythmbox (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: rhythmbox

Hello,
I just put in an "Amy Winehouse" CD and rhythmbox started, and then it crashed with this error and some gvfs-stuff crashed, too.
Thanks!

ProblemType: Crash
Architecture: amd64
Date: Thu Sep 25 21:30:55 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: fglrx
Package: rhythmbox 0.11.5-0ubuntu8
PackageArchitecture: amd64
ProcCmdline: rhythmbox cdda://scd0/
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/librhythmbox-core.so.0
 ?? () from /usr/lib/librhythmbox-core.so.0
 ?? () from /usr/lib/librhythmbox-core.so.0
 rhythmdb_entry_set_internal ()
Title: rhythmbox crashed with SIGSEGV in rhythmdb_entry_set_internal()
Uname: Linux 2.6.24-19-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Tags: apport-crash
Revision history for this message
goto (gotolaunchpad) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:remove_child (parent=0xc80930, data=0x17e5a70) at rhythmdb-tree.c:1410
remove_entry_from_album (db=<value optimized out>, entry=0x17e5a70)
rhythmdb_tree_entry_set (adb=<value optimized out>, entry=0x17e5a70,
rhythmdb_entry_set_internal (db=0xa18000, entry=0x17e5a70, notify_if_inserted=0,
entry_set_string_prop (db=0xa18000, entry=0x17e5a70, is_inserted=<value optimized out>,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in rhythmbox:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

thanks for the report, it looks like bug http://bugzilla.gnome.org/show_bug.cgi?id=454247 which is known upstream, linking the report, thanks for reporting.

Changed in rhythmbox:
assignee: nobody → desktop-bugs
status: New → Triaged
Changed in rhythmbox:
status: Unknown → New
Changed in rhythmbox:
importance: Unknown → Critical
Changed in rhythmbox:
status: New → Fix Released
Revision history for this message
Ryan Kitty (gothickitty93) wrote :

I just experienced this issue. Should I create a new report if it happens again, as this report is a bit old.

Revision history for this message
Paul White (paulw2u) wrote :

Upstream report closed "RESOLVED FIXED" on 2012-02-09
No further comments re crash for over 7 years so closing as fixed

Changed in rhythmbox (Ubuntu):
status: Triaged → Fix Released
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.