GNOME Bugzilla – Bug 483332
crash in Rhythmbox Music Player:
Last modified: 2007-10-05 10:07:46 UTC
Version: 0.10.1 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 107188224 vsize: 107188224 resident: 39874560 share: 26279936 rss: 39874560 rss_rlim: 4294967295 CPU usage: start_time: 1191501730 rtime: 105 utime: 92 stime: 13 cutime:1 cstime: 0 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 -1208600016 (LWP 2968)] [New Thread -1249248368 (LWP 2974)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 167681
Thread 1 (Thread -1208600016 (LWP 2968))
----------- .xsession-errors --------------------- 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 the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 409540 ***