GNOME Bugzilla – Bug 425928
crash in Text Editor: abriendo un archivo desd...
Last modified: 2007-04-07 14:49:09 UTC
Version: 2.15.9 What were you doing when the application crashed? abriendo un archivo desde un dvd fedora install x_64 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.2869.fc6 #1 SMP Wed Dec 20 14:51:34 EST 2006 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- (nautilus:10680): Eel-WARNING **: Trying to add a callback for preferences/background_set that already exists. (nautilus:10680): Eel-WARNING **: Trying to add a callback for preferences/background_color that already exists. (nautilus:10680): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists. (nautilus:10680): Eel-WARNING **: Trying to add a callback for preferences/background_set that already exists. (nautilus:10680): Eel-WARNING **: Trying to add a callback for preferences/background_color that already exists. (nautilus:10680): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists. ** (nautilus:10680): WARNING **: destroyed file has call_when_ready pending ** (bug-buddy:10899): WARNING **: No se pudo cargar el icono para Abrir carpeta -------------------------------------------------- Memory status: size: 384032768 vsize: 384032768 resident: 25206784 share: 13844480 rss: 25206784 rss_rlim: -1 CPU usage: start_time: 1175622950 rtime: 46 utime: 31 stime: 15 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496375536 (LWP 10894)] (no debugging symbols found) 0x0000003b1ee0d935 in waitpid () from /lib64/libpthread.so.0
+ Trace 124680
Thread 1 (Thread 46912496375536 (LWP 10894))
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 354046 ***