GNOME Bugzilla – Bug 489881
crash in Rhythmbox Music Player:
Last modified: 2007-10-24 17:50:24 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.20-2936.fc7xen #1 SMP Fri Sep 21 12:07:35 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: 129699840 vsize: 129699840 resident: 43122688 share: 28659712 rss: 43122688 rss_rlim: 4294967295 CPU usage: start_time: 1193247808 rtime: 385 utime: 356 stime: 29 cutime:84 cstime: 7 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208654112 (LWP 5489)] [New Thread -1247954032 (LWP 5497)] (no debugging symbols found) 0x00880402 in __kernel_vsyscall ()
+ Trace 172588
Thread 1 (Thread -1208654112 (LWP 5489))
----------- .xsession-errors --------------------- Traceback (most recent call last): File "/usr/lib/rhythmbox/plugins/magnatune/MagnatuneSource.py", line 38, in __init__ rb.BrowserSource.__init__(self, name=_("Magnatune")) NameError: global name '_' is not defined 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/lyrics/lyrics.py", line 256, in activate self.action = gtk.Action ('ViewSongLyrics', _('Song L_yrics'), 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 409540 ***