rhythmbox crashed with SIGSEGV in g_slice_alloc()

[Alexandre Jesus]

Binary package hint: rhythmbox

I just had enabled Info plugin. Had one song playing and a different one in the queue. I decided to remove that one in the queue and then t just crashed

I'm using Lucid Lynx, with full system updated

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: rhythmbox 0.12.8-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Apr 4 10:18:00 2010
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: rhythmbox
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xc2bcb6 <g_slice_alloc+262>: mov (%edx),%ecx
 PC (0x00c2bcb6) ok
 source "(%edx)" (0xffffffff) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 g_slice_alloc () from /lib/libglib-2.0.so.0
 pango_layout_get_iter () from /usr/lib/libpango-1.0.so.0
 pango_renderer_draw_layout ()
 gdk_draw_layout_with_colors ()
 gdk_draw_layout () from /usr/lib/libgdk-x11-2.0.so.0
Title: rhythmbox crashed with SIGSEGV in g_slice_alloc()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 g_slice_alloc () from /lib/libglib-2.0.so.0
 pango_layout_get_iter (layout=0x98c6810)
 pango_renderer_draw_layout (renderer=0xa45c800,
 IA__gdk_draw_layout_with_colors (drawable=0xa456de8,
 IA__gdk_draw_layout (drawable=0xa456de8, gc=0xb5d35588,

[Pedro Villavicencio (pedro)]

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.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.