GNOME Bugzilla – Bug 427056
crash in Movie Player: configurando Apache
Last modified: 2007-04-07 17:12:04 UTC
Version: 2.16.1 What were you doing when the application crashed? configurando Apache Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2798.fc6xen #1 SMP Mon Oct 16 15:11:19 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 68694016 vsize: 0 resident: 68694016 share: 0 rss: 21778432 rss_rlim: 0 CPU usage: start_time: 1175891349 rtime: 0 utime: 51 stime: 0 cutime:44 cstime: 0 timeout: 7 it_real_value: 0 frequency: 2 Backtrace was generated from '/usr/bin/totem' (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 -1209084208 (LWP 3742)] [New Thread -1230128240 (LWP 3745)] [New Thread -1219638384 (LWP 3744)] (no debugging symbols found) 0x003b9402 in __kernel_vsyscall ()
+ Trace 125593
Thread 1 (Thread -1209084208 (LWP 3742))
----------- .xsession-errors --------------------- ** (bug-buddy:3747): WARNING **: No se pudo cargar el icono para Ayuda ** (bug-buddy:3747): WARNING **: No se pudo cargar el icono para Calendar ** (bug-buddy:3747): WARNING **: No se pudo cargar el icono para Contacts ** (bug-buddy:3747): WARNING **: No se pudo cargar el icono para Editor del menú ** (bug-buddy:3747): WARNING **: No se pudo cargar el icono para Impresora predeterminada ** (bug-buddy:3747): WARNING **: No se pudo cargar el icono para Navegador Web Epiphany ** (bug-buddy:3747): WARNING **: No se pudo cargar el icono para Tasks ** (bug-buddy:3747): WARNING **: No se pudo cargar el icono para Mostrar el escritorio --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 348455 ***