Ubuntu
rhythmbox package

rhythmbox crashed with SIGSEGV in rb_python_module_load_with_gil() after last python2.6 upgrade in maverick

Bug #587589 reported by Fabien Tassin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: rhythmbox

the new python 2.6 in maverick killed rhythmbox (crash on startup)

happened after this upgrade: python2.6 2.6.5-1ubuntu6 -> 2.6.5+20100529-0ubuntu1

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: rhythmbox 0.12.8-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.34-4.11-generic 2.6.34
Uname: Linux 2.6.34-4-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Sun May 30 13:50:53 2010
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100331)
ProcCmdline: rhythmbox
ProcCwd: /home/fta
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/usr/bin/tcsh
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 rb_python_module_load_with_gil (module=0x9e78200)
 IA__g_type_module_use (module=0x9e78200)
 load_plugin_module (info=0x9e77f28)
 rb_plugins_engine_activate_plugin_real (info=0x9e77f28)
 rb_plugins_engine_activate_plugin (info=0x9e77f28)
Title: rhythmbox crashed with SIGSEGV in rb_python_module_load_with_gil()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:20237): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Fabien Tassin (fta) wrote :
Revision history for this message
Fabien Tassin (fta) wrote :

dropping the retrace+private tags and the core file, i already uploaded a retraced set of files.

tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, it was probably bug #587534 which has been fixed now

Changed in rhythmbox (Ubuntu):
importance: Undecided → Low
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.