GNOME Bugzilla – Bug 127479
Closing gedit causes an error
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: Closing gedit causes an error Bugzilla-Product: gedit Bugzilla-Component: general Bugzilla-Version: 2.4.0 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: Any time I open gedit to work with a text file. It crashes anytime I close gedit. Steps to reproduce the crash: 1. open gedit 2. view a document 3. close gedit Expected Results: Crashes with a fatal error How often does this happen? All the time. Additional Information: 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)...0x28fd7900 in __sys_poll () from /usr/lib/libc_r.so.4
+ Trace 41936
Thread 1 (process 225, thread 1)
#3 0x0 in ?? () No symbol table info available. ------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-11-20 09:12 ------- Unknown version 2.4.0 in product gedit. Setting version to the default, "unspecified". 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 ***