GNOME Bugzilla – Bug 497109
crash in Rhythmbox Music Player: 获取软件包更新信息!
Last modified: 2007-11-18 14:50:14 UTC
What were you doing when the application crashed? 获取软件包更新信息! Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 132947968 vsize: 132947968 resident: 33361920 share: 19087360 rss: 33361920 rss_rlim: 4294967295 CPU usage: start_time: 1195059539 rtime: 783 utime: 716 stime: 67 cutime:7 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 -1208935888 (LWP 3088)] [New Thread -1299199088 (LWP 3120)] [New Thread -1242895472 (LWP 3114)] [New Thread -1309688944 (LWP 3112)] [New Thread -1255683184 (LWP 3095)] (no debugging symbols found) 0x00a66402 in __kernel_vsyscall ()
+ Trace 177922
Thread 2 (Thread -1299199088 (LWP 3120))
----------- .xsession-errors (15 sec old) --------------------- self._err_handler.fatalError(exc) File "/usr/lib/python2.5/site-packages/_xmlplus/sax/handler.py", line 38, in fatalError raise exception xml.sax._exceptions.SAXParseException: <unknown>:1:0: no element found Traceback (most recent call last): File "/usr/lib/rhythmbox/plugins/jamendo/JamendoSource.py", line 162, in finish_loadscreen self.__load_db () File "/usr/lib/rhythmbox/plugins/jamendo/JamendoSource.py", line 294, in __load_db tracks = self.__saxHandler.tracks AttributeError: JamendoSaxHandler instance has no attribute 'tracks' (rhythmbox:3088): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed GThread-ERROR **: file gthread-posix.c: line 171 (): error '设备或资源忙' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)' 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 434003 ***