GNOME Bugzilla – Bug 481449
crash in Rhythmbox Music Player: 征程操作
Last modified: 2007-10-01 08:52:24 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 126541824 vsize: 126541824 resident: 30195712 share: 17489920 rss: 30195712 rss_rlim: 4294967295 CPU usage: start_time: 1191060721 rtime: 498 utime: 452 stime: 46 cutime:3 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 -1209177552 (LWP 8399)] [New Thread -1272890480 (LWP 8433)] [New Thread -1284134000 (LWP 8411)] [New Thread -1248453744 (LWP 8408)] [New Thread -1261778032 (LWP 8406)] (no debugging symbols found) 0x001a7402 in __kernel_vsyscall ()
+ Trace 166287
Thread 2 (Thread -1272890480 (LWP 8433))
----------- .xsession-errors (9 sec old) --------------------- (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files ConsoleKit console-kit-daemon (pid 2224) 正在运行... ConsoleKit console-kit-daemon (pid 2224) 正在运行... ConsoleKit console-kit-daemon (pid 2224) 正在运行... The application 'pup' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. (rhythmbox:8399): 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 ***