GNOME Bugzilla – Bug 449394
crash in Rhythmbox Music Player: Simplemente la estaba ab...
Last modified: 2007-06-20 21:51:56 UTC
What were you doing when the application crashed? Simplemente la estaba abriendo por primera vez y nevegando por sus secciones. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 99102720 vsize: 99102720 resident: 34422784 share: 22761472 rss: 34422784 rss_rlim: 4294967295 CPU usage: start_time: 1185782740 rtime: 204 utime: 183 stime: 21 cutime:2 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 -1208423888 (LWP 3471)] [New Thread -1247806576 (LWP 3480)] [New Thread -1220539504 (LWP 3478)] [New Thread -1234859120 (LWP 3476)] (no debugging symbols found) 0x00bf7402 in __kernel_vsyscall ()
+ Trace 142360
Thread 2 (Thread -1247806576 (LWP 3480))
----------- .xsession-errors --------------------- warning: /var/named/named.ip6.local saved as /var/named/named.ip6.local.rpmsave warning: /var/named/named.local saved as /var/named/named.local.rpmsave warning: /var/named/named.zero saved as /var/named/named.zero.rpmsave --- Hash table keys for warning below: --> file:///root (nautilus:3243): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (gnome-terminal:3266): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (rhythmbox:3471): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Dispositivo o recurso ocupado' 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 ***