GNOME Bugzilla – Bug 167691
gedit crash
Last modified: 2005-02-17 11:00:44 UTC
Distribution: Slackware Slackware 10.0.0 Package: gedit Severity: normal Version: GNOME2.6.2 2.6.1 Gnome-Distributor: GNOME.Org Synopsis: gedit crash Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: 2.6.1 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: gedit crashed when i click open after already opening a file. it has crashed on me several times when opening or saving files. Expected Results: an open file dialogue How often does this happen? pretty much every time I use gnome on this network of identical PCs Additional Information: doesnt happen on my home PC Debugging Information: 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)...(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)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 5928)] [New Thread 32769 (LWP 5957)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 5928)] [New Thread 32769 (LWP 5957)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 5928)] [New Thread 32769 (LWP 5957)] [New Thread 16386 (LWP 5958)] [New Thread 32771 (LWP 5959)] [New Thread 49156 (LWP 5960)] (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)...0x40d124da in waitpid () from /lib/libpthread.so.0
+ Trace 55802
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-17 05:29 ------- Unknown version 2.6.1 in product gedit. Setting version to "2.6.x". 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 rjm502@york.ac.uk. 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. *** This bug has been marked as a duplicate of 151715 ***