GNOME Bugzilla – Bug 158739
Crash when opening a new document
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: Crash when opening a new document Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: Steps to reproduce the crash: 1. Open 3 tabs up in gedit 2. fill the clipboard 3. hit the New button Expected Results: crash How often does this happen? don't know- only happened once or twice so far 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 -150801760 (LWP 9936)] [New Thread 13564848 (LWP 26608)] [Thread debugging using libthread_db enabled] [New Thread -150801760 (LWP 9936)] [New Thread 13564848 (LWP 26608)] [New Thread 27249584 (LWP 26607)] (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 -150801760 (LWP 9936)] [New Thread 13564848 (LWP 26608)] (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)...0x00cae402 in ?? ()
+ Trace 52221
Thread 1 (Thread -150801760 (LWP 9936))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-19 15:05 ------- 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 davidg_70@hotmail.com. 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.
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. Matches the stack trace in bug 158543, which has been marked as a duplicate of 151715. *** This bug has been marked as a duplicate of 151715 ***