GNOME Bugzilla – Bug 395938
crash in Text Editor: Trying to setup reposito...
Last modified: 2007-01-18 20:52:47 UTC
Version: 2.15.9 What were you doing when the application crashed? Trying to setup repositories for yum. 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:19 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- (nautilus:5391): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists. (nautilus:5391): Eel-WARNING **: Trying to add a callback for preferences/background_set that already exists. (nautilus:5391): Eel-WARNING **: Trying to add a callback for preferences/background_color that already exists. (nautilus:5391): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists. (nautilus:5391): Eel-WARNING **: Trying to add a callback for preferences/background_set that already exists. (nautilus:5391): Eel-WARNING **: Trying to add a callback for preferences/background_color that already exists. (nautilus:5391): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists. ** (bug-buddy:6177): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 97689600 vsize: 0 resident: 97689600 share: 0 rss: 24743936 rss_rlim: 0 CPU usage: start_time: 1168641320 rtime: 0 utime: 383 stime: 0 cutime:355 cstime: 0 timeout: 28 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gedit' (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 -1208444352 (LWP 6104)] (no debugging symbols found) 0x00c76402 in __kernel_vsyscall ()
+ Trace 101658
Thread 1 (Thread -1208444352 (LWP 6104))
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 393467 ***