GNOME Bugzilla – Bug 128392
Gedit crashing on close
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Unknown Package: gedit Severity: normal Version: GNOME2.4.0 2.4.0 Gnome-Distributor: FreeBSD GNOME Project Synopsis: Gedit crashing on close Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: 2.4.0 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: When I quit gedit its saying that it crashed and providing this dialog for the bug report. It happens even if i close all the files i was editing. It dosn't matter is i close with the button on the app window or from the file menu. Steps to reproduce the crash: 1. open gedit 2. close gedit 3. Expected Results: n/a How often does this happen? Every time I close gedit. Additional Information: freeBSD 4.9 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)...0x28fd7900 in __sys_poll () from /usr/lib/libc_r.so.4
+ Trace 42250
Thread 1 (process 92669, thread 1)
#3 0x0 in ?? () No symbol table info available. ------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-12-02 16:20 ------- Unknown version 2.4.0 in product gedit. Setting version to the default, "unspecified". The original reporter (datalite@qwest.net) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, maggi@athena.polito.it.
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.
*** This bug has been marked as a duplicate of 110280 ***