GNOME Bugzilla – Bug 497888
crash in Rhythmbox Music Player:
Last modified: 2007-11-25 11:11:39 UTC
Version: 0.10.1 What were you doing when the application crashed? Distribution: Momonga Linux release 4 (Izumi) Gnome Release: 2.18.3 2007-08-13 (GNOME.Org) BugBuddy Version: 2.18.1 System: Linux 2.6.21-28m.mo4 #1 SMP Thu Aug 16 05:49:21 JST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 157900800 vsize: 157900800 resident: 50552832 share: 37691392 rss: 50552832 rss_rlim: 4294967295 CPU usage: start_time: 1195389924 rtime: 775 utime: 683 stime: 92 cutime:11 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208367328 (LWP 10957)] [New Thread 47164304 (LWP 10968)] (no debugging symbols found) 0x00878402 in __kernel_vsyscall ()
+ Trace 178504
----------- .xsession-errors (36 sec old) --------------------- Traceback (most recent call last): File "/usr/lib/rhythmbox/plugins/magnatune/__init__.py", line 79, in activate action = gtk.Action('MagnatunePurchaseAlbum', _('Purchase Album'), NameError: global name '_' is not defined Traceback (most recent call last): File "/usr/lib/rhythmbox/plugins/jamendo/JamendoSource.py", line 51, in __init__ rb.BrowserSource.__init__(self, name=_("Jamendo")) NameError: global name '_' is not defined Traceback (most recent call last): File "/usr/lib/rhythmbox/plugins/jamendo/__init__.py", line 69, in activate action = gtk.Action('JamendoDownloadAlbum', _('_Download Album'), NameError: global name '_' is not defined Rhythmbox-ERROR **: file rb-shell-preferences.c: line 286 (rb_shell_preferences_new): assertion failed: (name != NULL) aborting... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 484988 ***