GNOME Bugzilla – Bug 464814
crash in Rhythmbox Music Player: mix pendza avgust 2007
Last modified: 2007-08-21 13:17:15 UTC
What were you doing when the application crashed? mix pendza avgust 2007 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: 138559488 vsize: 138559488 resident: 35852288 share: 18776064 rss: 35852288 rss_rlim: 4294967295 CPU usage: start_time: 1186334009 rtime: 50263 utime: 45771 stime: 4492 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 -1208997328 (LWP 4032)] [New Thread -1221637232 (LWP 6624)] [New Thread -1300255856 (LWP 6541)] [New Thread -1234658416 (LWP 6378)] [New Thread -1247806576 (LWP 4042)] (no debugging symbols found) 0x00f87402 in __kernel_vsyscall ()
+ Trace 153799
Thread 2 (Thread -1221637232 (LWP 6624))
----------- .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:4032): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Device or resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)' 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 434003 ***