GNOME Bugzilla – Bug 474479
crash in Text Editor: trying to open a backup ...
Last modified: 2007-09-21 19:30:45 UTC
Version: 2.18.0 What were you doing when the application crashed? trying to open a backup file on CD from another server Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 1486139392 vsize: 1486139392 resident: 1457958912 share: 1454505984 rss: 1457958912 rss_rlim: 4294967295 CPU usage: start_time: 1189154761 rtime: 164 utime: 97 stime: 67 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 -1208887584 (LWP 2877)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 161072
Thread 1 (Thread -1208887584 (LWP 2877))
No plugin installed in $HOME. ----------- .xsession-errors (176129 sec old) --------------------- fixme:richedit:fnTextSrv_TxSendMessage 0x188860: STUB fixme:richedit:fnTextSrv_TxSendMessage 0x188860: STUB fixme:richedit:fnTextSrv_TxGetNaturalSize 0x188860: STUB fixme:richedit:fnTextSrv_TxSendMessage 0x1888b8: STUB fixme:richedit:fnTextSrv_TxSendMessage 0x1888b8: STUB fixme:richedit:fnTextSrv_TxSendMessage 0x1888b8: STUB fixme:richedit:fnTextSrv_TxSendMessage 0x1888b8: STUB fixme:richedit:fnTextSrv_TxSendMessage 0x1888b8: STUB fixme:richedit:fnTextSrv_TxSendMessage 0x1888b8: STUB fixme:richedit:fnTextSrv_TxSendMessage 0x1888b8: STUB fixme:richedit:fnTextSrv_TxSendMessage 0x1888b8: STUB fixme:richedit:fnTextSrv_TxSendMessage 0x1888b8: STUB fixme:richedit:fnTextSrv_TxSendMessage 0x1888b8: STUB ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for gedit, gtk, glib, gnome-vfs, libgnome, libgnomeui, pango and gtksourceview (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
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 352099 ***