GNOME Bugzilla – Bug 454460
crash in Rhythmbox Music Player: 关闭
Last modified: 2007-07-07 22:53:56 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 121044992 vsize: 121044992 resident: 31997952 share: 19243008 rss: 31997952 rss_rlim: 4294967295 CPU usage: start_time: 1183782057 rtime: 288 utime: 268 stime: 20 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 -1208763856 (LWP 9153)] [New Thread -1308648560 (LWP 9209)] [New Thread -1242723440 (LWP 9207)] [New Thread -1266664560 (LWP 9161)] (no debugging symbols found) 0x005f6402 in __kernel_vsyscall ()
+ Trace 146256
Thread 2 (Thread -1308648560 (LWP 9209))
----------- .xsession-errors (6 sec old) --------------------- Failed to deregister an IMContext Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Loading "installonlyn" plugin Failed to receive messages at scim_bridge_client_read_and_dispatch () An IOException occurred at handle_message () (rhythmbox:9153): Rhythmbox-WARNING **: Unable to start mDNS browsing: MDNS 服务未运行 (rhythmbox:9153): Rhythmbox-WARNING **: Unable to stop mDNS browsing: MDNS 服务未运行 (rhythmbox:9153): 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 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 ***