GNOME Bugzilla – Bug 158026
gedit crashed while opening FILE menu to save file changes
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: gedit Severity: normal Version: GNOME2.6. unspecified Gnome-Distributor: Red Hat, Inc Synopsis: gedit crashed while opening FILE menu to save file changes Bugzilla-Product: gedit Bugzilla-Component: docs Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found)...Using host libthread_db library "/lib/tls/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 -150281568 (LWP 3551)] [New Thread 1682352 (LWP 3564)] [Thread debugging using libthread_db enabled] [New Thread -150281568 (LWP 3551)] [New Thread 1682352 (LWP 3564)] [Thread debugging using libthread_db enabled] [New Thread -150281568 (LWP 3551)] [New Thread 1682352 (LWP 3564)] [New Thread 119798704 (LWP 3563)] (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)...0x002a0402 in ?? ()
+ Trace 51873
Thread 1 (Thread -150281568 (LWP 3551))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-12 02:08 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gedit". Setting to default milestone for this product, '---' 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 luc1ph3r6@netscape.net. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** This bug has been marked as a duplicate of 151715 ***