GNOME Bugzilla – Bug 444778
crash in Rhythmbox Music Player: closing the application
Last modified: 2007-06-06 22:31:33 UTC
What were you doing when the application crashed? closing the application 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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 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: 124334080 vsize: 124334080 resident: 27746304 share: 16162816 rss: 27746304 rss_rlim: 4294967295 CPU usage: start_time: 1181147281 rtime: 262 utime: 234 stime: 28 cutime:0 cstime: 1 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208637728 (LWP 3440)] [New Thread -1239164016 (LWP 3492)] [New Thread -1270633584 (LWP 3491)] [New Thread -1291613296 (LWP 3489)] [New Thread -1281123440 (LWP 3485)] [New Thread -1249653872 (LWP 3447)] (no debugging symbols found) 0x00a8b402 in __kernel_vsyscall ()
+ Trace 138796
Thread 3 (Thread -1270633584 (LWP 3491))
----------- .xsession-errors (12 sec old) --------------------- (K3bDevice::Device) /dev/scd0: Device reports bogus disc information length of 24 (K3bDevice::Device) /dev/scd0: Number of supported write speeds via GET PERFORMANCE: 1 (K3bDevice::Device) /dev/scd0 : 11080 KB/s ScimInputContextPlugin() ~ScimInputContextPlugin() ScimInputContextPlugin() (K3bDevice::DeviceManager) request for empty device! Launched ok, pid = 3364 ~ScimInputContextPlugin() ICE default IO error handler doing an exit(), pid = 3361, errno = 0 (rhythmbox:3440): 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 ***