GNOME Bugzilla – Bug 452171
crash in Rhythmbox Music Player: Trying to play the test ...
Last modified: 2007-06-29 22:59:33 UTC
What were you doing when the application crashed? Trying to play the test wav file supplied with the realtek alsa audio driver Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 134225920 vsize: 134225920 resident: 66752512 share: 21655552 rss: 66752512 rss_rlim: 4294967295 CPU usage: start_time: 1183102398 rtime: 457 utime: 437 stime: 20 cutime:2 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 -1208554960 (LWP 3066)] [New Thread -1245709424 (LWP 3077)] [New Thread -1233196144 (LWP 3076)] [New Thread -1256199280 (LWP 3074)] (no debugging symbols found) 0x00b49402 in __kernel_vsyscall ()
+ Trace 144550
Thread 3 (Thread -1233196144 (LWP 3076))
----------- .xsession-errors --------------------- localuser:beejay being added to access control list SESSION_MANAGER=local/rjm0002:/tmp/.ICE-unix/2838 Loading "installonlyn" plugin Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00022 (Music Play) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. (rhythmbox:3066): 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 ***