GNOME Bugzilla – Bug 460222
crash in Rhythmbox Music Player: enjoy music
Last modified: 2007-07-29 01:39:16 UTC
What were you doing when the application crashed? enjoy music 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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 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: 123437056 vsize: 123437056 resident: 42917888 share: 16388096 rss: 42917888 rss_rlim: 4294967295 CPU usage: start_time: 1185397289 rtime: 1346 utime: 650 stime: 696 cutime:1 cstime: 10 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 -1208494368 (LWP 11494)] [New Thread -1279411312 (LWP 11526)] [New Thread -1220265072 (LWP 11507)] [New Thread -1244583024 (LWP 11504)] (no debugging symbols found) 0x00b5a402 in __kernel_vsyscall ()
+ Trace 150431
Thread 2 (Thread -1279411312 (LWP 11526))
----------- .xsession-errors (40 sec old) --------------------- Cannot install source packages. No packages were given for installation. Loading "installonlyn" plugin Cannot install source packages. No packages were given for installation. Loading "installonlyn" plugin Cannot install source packages. No packages were given for installation. (rhythmbox:11494): libgnomevfs-WARNING **: trying to read a non-existing handle (rhythmbox:11494): 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 ***