GNOME Bugzilla – Bug 169052
crashed while opening html file
Last modified: 2005-05-04 01:24:24 UTC
Distribution: Slackware Slackware 10.1.0 Package: gedit Severity: normal Version: GNOME2.6.2 2.6.1 Gnome-Distributor: GNOME.Org Synopsis: crashed while opening html file Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: 2.6.1 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: Crashed upon opening html file; I opened gedit, went to the directory which contained the file that I wanted to open. Realizing I didn't have the files yet, I switched over to gftp to download them. Clicked back over to gedit, clicked up one directory and back to refresh. Then clicked to open the file I wanted. I upgraded to Slack 10.1 from 10.0 about a week ago, but hardly have ever used gedit on this computer before. Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? First time. 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 881)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x40d13488 in waitpid () from /lib/libpthread.so.0
+ Trace 56371
Thread 1 (Thread 16384 (LWP 881))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-02 21:00 ------- 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 andy333@tcq.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.
*** Bug 169053 has been marked as a duplicate of this bug. ***
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but the maintainer is looking for more information. Could you answer the question(s) in bug 167951? *** This bug has been marked as a duplicate of 167951 ***
No, I can't answer any of those questions, but I can add some more information to it that I came across earlier today.
*** Bug 300030 has been marked as a duplicate of this bug. ***
*** Bug 302780 has been marked as a duplicate of this bug. ***