[intrepid] rhythmbox crashed with SIGSEGV in free()

Bug #263903 reported by Greg A on 2008-09-02
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Ubuntu Desktop Bugs

Bug Description

Binary package hint: rhythmbox

I was playing a song from my hard drive in rhythmbox. I then connected (via USB) a MP3 player. I didn't then do anything with it inside rhythmbox. However when unmounting my MP3 player (via the Nautilus eject icons) Rhythmbox crashed immediately stopping playing.

Version: 0.11.6svn20080807-0ubuntu1

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: nvidia
Package: rhythmbox 0.11.6svn20080807-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: rhythmbox
Signal: 11
SourcePackage: rhythmbox
 free () from /lib/tls/i686/cmov/libc.so.6
 g_free () from /usr/lib/libglib-2.0.so.0
 ?? ()
 ?? ()
 dbus_connection_dispatch () from /lib/libdbus-1.so.3
Title: rhythmbox crashed with SIGSEGV in free()
Uname: Linux 2.6.26-5-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Greg A (etulfetulf) wrote :

StacktraceTop:free () from /lib/tls/i686/cmov/libc.so.6
IA__g_free (mem=0x40802000) at /build/buildd/glib2.0-2.17.7/glib/gmem.c:190
g_proxy_volume_update (volume=0xb44c7310, iter=0xbff3f89c) at gproxyvolume.c:244
filter_function (connection=0x9c726f0, message=0x9c9cd30, user_data=0x9c9dc80)
dbus_connection_dispatch (connection=0x9c726f0) at dbus-connection.c:4406

Changed in rhythmbox:
importance: Undecided → Medium
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in rhythmbox:
assignee: nobody → desktop-bugs
status: New → Incomplete
Greg A (etulfetulf) wrote :

Attaching valgrind log.

Changed in rhythmbox:
status: Incomplete → New
Sebastien Bacher (seb128) wrote :

the log lacks debug informations but the issue is likely bug #263268

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers