GNOME Bugzilla – Bug 155275
gedit crashes when opening a new file while editing.
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Unknown Package: gedit Severity: normal Version: GNOME2.6.2 2.6.2 Gnome-Distributor: FreeBSD GNOME Project Synopsis: gedit crashes when opening a new file while editing. Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: 2.6.2 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: When I edit a xhtml file with syntax highlighting and wants to open the open-dialog gedit crashes. Steps to reproduce the crash: 1. open gedit 2. open a xhtml file and activate syntax highlighting for xhtml. 3. click the open button Expected Results: The open dialog. How often does this happen? Everytime. Additional Information: os: FreeBSD 5.3-BETA7 wm: Gnome 2.6.2 Debugging Information: Backtrace was generated from '/usr/X11R6/bin/gedit' (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Switching to LWP 100319] 0x283f6d7f in pthread_testcancel () from /usr/lib/libpthread.so.1
+ Trace 51000
Thread 5 (LWP 100319)
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-10-13 05:33 ------- Unknown version 2.6.2 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 nr1_enforcer@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. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Please make sure that the package was compiled with debugging symbols and see http://bugzilla.gnome.org/getting-traces.cgi for more information about useful stack traces. Beside it's seems likely that this is a gtkfilechooser bug (we got lots of dups of crash-on-open crash-on-save) it should be fixed in newer gtk/gnome libs.
From the description it seems a duplicate of bug #151715.
*** This bug has been marked as a duplicate of 151715 ***