GNOME Bugzilla – Bug 456635
crash in Rhythmbox Music Player: 1. trying to open a red...
Last modified: 2007-07-15 00:21:05 UTC
What were you doing when the application crashed? 1. trying to open a redio statation, CBC1. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (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: Clearlooks Icon Theme: Fedora Memory status: size: 163151872 vsize: 163151872 resident: 36364288 share: 23945216 rss: 36364288 rss_rlim: 4294967295 CPU usage: start_time: 1184369738 rtime: 1032 utime: 767 stime: 265 cutime:7 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 -1208710608 (LWP 4067)] [New Thread -1320113264 (LWP 4141)] [New Thread -1309623408 (LWP 4091)] [New Thread -1299133552 (LWP 4090)] [New Thread -1288643696 (LWP 4087)] [New Thread -1278153840 (LWP 4086)] [New Thread -1266852976 (LWP 4076)] [New Thread -1243714672 (LWP 4075)] [New Thread -1256363120 (LWP 4074)] (no debugging symbols found) 0x0078d402 in __kernel_vsyscall ()
+ Trace 147813
Thread 7 (Thread -1266852976 (LWP 4076))
----------- .xsession-errors (36 sec old) --------------------- packet exception -- command code: 0x 2 EvaUHManager runs finished EvaUHManager::cleanUp EvaUHManager::cleanUp X Error: BadWindow (invalid Window parameter) 3 Major opcode: 7 Minor opcode: 0 Resource id: 0x2c0004d ICE default IO error handler doing an exit(), pid = 4052, errno = 0 (rhythmbox:4067): Rhythmbox-CRITICAL **: rb_player_gst_play: assertion `mp->priv->playbin != NULL' failed GThread-ERROR **: file gthread-posix.c: line 171 (): error '设备或资源忙' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)' aborting... Xlib: unexpected async reply (sequence 0x103d5)! --------------------------------------------------
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 ***