GNOME Bugzilla – Bug 458600
crash in Text Editor: menu File
Last modified: 2007-07-20 16:39:21 UTC
Version: 2.18.0 What were you doing when the application crashed? menu File > Print, after several <page setup>, <print preview>. 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.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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 87814144 vsize: 87814144 resident: 27938816 share: 14245888 rss: 27938816 rss_rlim: 4294967295 CPU usage: start_time: 1184923802 rtime: 5910 utime: 5831 stime: 79 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209006368 (LWP 3948)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 149311
Thread 1 (Thread -1209006368 (LWP 3948))
No plugin installed in $HOME. ----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/librsvg-2.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgsf-1.so.114" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libcroco-0.6.so.3" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libbz2.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 405900 ***