GNOME Bugzilla – Bug 157372
random application crash
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Slackware Slackware 10.0.0 Package: gedit Severity: normal Version: GNOME2.6.2 2.6.1 Gnome-Distributor: GNOME.Org Synopsis: random application 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 closes down Steps to reproduce the crash: 1. open gedit 2. start writing, try to save 3. gedit closes Expected Results: gedit should just save and let me continue! How often does this happen? four times in a row so far Additional Information: fix it 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 3414)] [New Thread 32769 (LWP 3415)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 3414)] [New Thread 32769 (LWP 3415)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 3414)] [New Thread 32769 (LWP 3415)] [New Thread 16386 (LWP 3416)] [New Thread 32771 (LWP 3417)] [New Thread 49156 (LWP 3418)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x40d064da in waitpid () from /lib/libpthread.so.0
+ Trace 51632
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-04 12:48 ------- Unknown version 2.6.1 in product gedit. Setting version to "0.5.1". 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 nsz100@cs.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.
*** This bug has been marked as a duplicate of 151715 ***