GNOME Bugzilla – Bug 497549
crash in Rhythmbox Music Player: 打开一个mp3文件后就不行了。
Last modified: 2007-11-18 14:51:22 UTC
What were you doing when the application crashed? 打开一个mp3文件后就不行了。 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 163307520 vsize: 163307520 resident: 32186368 share: 18976768 rss: 32186368 rss_rlim: 4294967295 CPU usage: start_time: 1195266259 rtime: 334 utime: 303 stime: 31 cutime:1 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 -1208128976 (LWP 3245)] [New Thread -1298154608 (LWP 3278)] [New Thread -1287664752 (LWP 3277)] [New Thread -1266685040 (LWP 3275)] [New Thread -1277174896 (LWP 3272)] [New Thread -1256195184 (LWP 3251)] (no debugging symbols found) 0x0087c402 in __kernel_vsyscall ()
+ Trace 178261
Thread 3 (Thread -1287664752 (LWP 3277))
----------- .xsession-errors (6 sec old) --------------------- Creating backend ... Loading x11 FrontEnd module ... GTK Panel of SCIM 1.4.5 Starting SCIM as daemon ... SCIM has been successfully launched. Smart Common Input Method 1.4.5 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name Loading "installonlyn" plugin (rhythmbox:3245): 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 ***