GNOME Bugzilla – Bug 478837
crash in Rhythmbox Music Player:
Last modified: 2007-09-22 08:38:43 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.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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 116453376 vsize: 116453376 resident: 27877376 share: 16396288 rss: 27877376 rss_rlim: 4294967295 CPU usage: start_time: 1190350152 rtime: 198 utime: 166 stime: 32 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208240416 (LWP 11585)] [New Thread -1250403440 (LWP 11712)] [New Thread -1284412528 (LWP 11636)] [New Thread -1273922672 (LWP 11594)] (no debugging symbols found) 0x007b8402 in __kernel_vsyscall ()
+ Trace 164310
Thread 2 (Thread -1250403440 (LWP 11712))
----------- .xsession-errors --------------------- Invalid entry (missing '=') at /tmp/kde-Hector/kconf_updatepDV1ja.tmp:1 Invalid entry (missing '=') at /tmp/kde-Hector/kconf_update4RG5eb.tmp:1 ScimInputContextPlugin() ~ScimInputContextPlugin() ScimInputContextPlugin() Launched ok, pid = 10869 Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4d specified for 0x4000012 (Preference). ScimInputContextPlugin() ~ScimInputContextPlugin() ScimInputContextPlugin() (rhythmbox:11585): 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 ***