GNOME Bugzilla – Bug 166945
Three file opening bug (This is in english)
Last modified: 2005-02-10 16:59:08 UTC
Distribution: Slackware Slackware 10.0.0 Package: gedit Severity: normal Version: GNOME2.6.2 2.6.1 Gnome-Distributor: GNOME.Org Synopsis: Three file opening bug (This is in english) Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: 2.6.1 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: Open a file, then another, then another (third is fatal) Steps to reproduce the crash: 1. Open a file 2. Open another 3. Try to open another Expected Results: Failure to open the third How often does this happen? Constantly Additional Information: 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 5770)] [New Thread 32769 (LWP 5771)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 5770)] [New Thread 32769 (LWP 5771)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 5770)] [New Thread 32769 (LWP 5771)] [New Thread 16386 (LWP 5772)] [New Thread 32771 (LWP 5773)] (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 55555
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-10 11:35 ------- 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 ncm500@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. Matches the stack trace in bug 165133, which has been marked as a duplicate of 151715. *** This bug has been marked as a duplicate of 151715 ***