GNOME Bugzilla – Bug 464478
crash in Rhythmbox Music Player: it didnt crash i closed ...
Last modified: 2007-08-21 13:01:33 UTC
What were you doing when the application crashed? it didnt crash i closed it and got this annoying message that comes when i press the x abbruptly 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.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 140922880 vsize: 140922880 resident: 45162496 share: 25440256 rss: 45162496 rss_rlim: 4294967295 CPU usage: start_time: 1186419159 rtime: 73755 utime: 61908 stime: 11847 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 -1208243664 (LWP 18164)] [New Thread -1277072496 (LWP 21395)] [New Thread -1320830064 (LWP 21387)] [New Thread -1245471856 (LWP 21339)] [New Thread -1219933296 (LWP 18171)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 153561
Thread 2 (Thread -1277072496 (LWP 21395))
----------- .xsession-errors (7 sec old) --------------------- (rhythmbox:18164): GStreamer-CRITICAL **: Trying to dispose element fakesink, but it is not in the NULL state. You need to explicitly set elements to the NULL state before dropping the final reference, to allow them to clean up. _IceTransSocketUNIXConnect: Cannot connect to non-local host d64-180-249-74.bchsia.telus.net (gnome-terminal:21280): GnomeUI-WARNING **: While connecting to session manager: Could not open network socket. (rhythmbox:18164): 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 ***