rhythmbox crashed with SIGSEGV in g_type_module_use()

[Jürgen Mülbert]

Binary package hint: rhythmbox

 rhythmbox 0.11.4-0ubuntu2

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

ProblemType: Crash
Architecture: amd64
Date: Sat Jan 26 13:55:23 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: cdrom
Package: rhythmbox 0.11.4-0ubuntu2
PackageArchitecture: amd64
ProcCmdline: rhythmbox
ProcCwd: /home/juergen
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 PATH=/home/juergen/bin:/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:
 ?? ()
 g_type_module_use ()
 rb_plugins_engine_activate_plugin ()
 ?? ()
 ?? () from /usr/lib/librhythmbox-core.so.0
Title: rhythmbox crashed with SIGSEGV in g_type_module_use()
Uname: Linux seneca 2.6.24-4-generic #1 SMP Mon Jan 14 18:19:11 UTC 2008 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
SegvAnalysis:
 Segfault happened at: 0x45e103: mov 0x150(%rax),%esi
 PC (0x0045e103) ok
 source "0x150(%rax)" (0x00000150) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA

[Apport retracing service (apport)]

StacktraceTop:rb_python_module_load_with_gil (module=0xc44460) at rb-python-module.c:333
IA__g_type_module_use (module=0xc44460) at /build/buildd/glib2.0-2.15.3/gobject/gtypemodule.c:190
rb_plugins_engine_activate_plugin (info=0xc8c2e0) at rb-plugins-engine.c:476
rb_plugins_engine_load_cb (uri=<value optimized out>, dir=<value optimized out>,
rb_uri_handle_recursively_cb (rel_path=<value optimized out>, info=<value optimized out>,

[Pedro Villavicencio (pedro)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=512570

[Chris Wilson (notgary-deactivatedaccount)]

Thanks a lot for reporting this bug, but I do not believe this issue still exists in Ubuntu. The original report was filed against a much older version of the software, and since it has been a long time since there was any activity on this report or any duplicates filed, either here or upstream, it is likely that the issue has been designed out. As such, I'm closing this bug.