GNOME Bugzilla – Bug 308141
gedit crashed when switching focus back to it.
Last modified: 2005-07-19 19:13:03 UTC
Distribution: Fedora Core release 4 (Stentz) Package: gedit Severity: normal Version: GNOME2.10.0 2.10.2 Gnome-Distributor: Red Hat, Inc Synopsis: gedit crashed when switching focus back to it. Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: 2.10.2 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: I had gedit up with a single Unsaved Document open. The doc had about a page worth of text in it. I had copied about 3 lines of text to the clipboard and was switching focus back to gedit when it crashed Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? This is the first time. Additional Information: WM was Fluxbox from Fedora Core 4 Extras; Running Fedora Core 4 on i686. Debugging Information: Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found) Using host libthread_db library "/lib/obsolete/linuxthreads/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 4675)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x003da7c8 in waitpid () from /lib/obsolete/linuxthreads/libpthread.so.0
+ Trace 61192
Thread 1 (Thread 16384 (LWP 4675))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-18 02:15 UTC ------- Unknown version 2.10.2 in product gedit. Setting version to "2.10.x". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was peter.smith@utsouthwestern.edu.
Thanks for the bug report. 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? *** This bug has been marked as a duplicate of 305680 ***
I will look into it. Peter