GNOME Bugzilla – Bug 126555
Problems with files containing a NULL character
Last modified: 2010-02-07 09:48:27 UTC
Package: gedit Severity: normal Version: 2.4.1 Synopsis: Crash on startup Bugzilla-Product: gedit Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of Problem: Crashed Steps to reproduce the problem: 1. Browsing the web, trying to open this file, http://members.dcsi.net.au/chuma/media/docs/T&MHSP.rtf Epiphany launched gedit. 2. then the little crash box came up How often does this happen? First time only, now there's an encoding error. Additional Information: Debugging Information: Backtrace was generated from '/usr/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)...[New Thread 16384 (LWP 28781)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x0eff3fdc in waitpid () from /lib/libpthread.so.0
+ Trace 41581
Thread 1 (Thread 16384 (LWP 28781))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-11-09 08:45 ------- Reassigning to the default owner of the component, maggi@athena.polito.it.
This appears to be a unique stack trace, according to the simple-dup-finder.
The crash seems to happend in gedit_document_get_type (). This is very weird. How did you install gedit? Which version of gtk+/glib were you using?
I am using debian unstable, and installed everything through apt (apt-get install gnome, or something along those lines). I haven't really updated much since the report, so here's a list of current packages on my system (should be fairly similar): ii libglib2.0-0 2.2.3-1 The GLib library of C routines ii libglib2.0-dev 2.2.3-1 Development files for the GLib library ii libglib2.0-doc 2.2.3-1 Documentation files for the GLib library ii libgtk2.0-0 2.2.4-2 The GTK+ graphical user interface library ii libgtk2.0-comm 2.2.4-2 Common files for the GTK+ graphical user int ii libgtk2.0-dev 2.2.4-2 Development files for the GTK+ library ii libgtk2.0-doc 2.2.4-2 Documentation for the GTK+ graphical user in ii gedit 2.4.1-1 light-weight text editor
Are you still able to reproduce this bug? If you are still able, please send me a new stack trace. See http://bugzilla.gnome.org/getting-traces.cgi for more information about getting a useful stack trace. Note for me: Try to understand why gedit is not able to open the http://members.dcsi.net.au/chuma/media/docs/T&MHSP.rtf and reports a encoding problem? [paolo@sara gnome]$ file T\&MHSP.rtf T&MHSP.rtf: Rich Text Format data, version 1, ANSI Which encoding is used by RTF?
The (encoding) problem seems to be caused by the fact that the file contains a NULL (00) character. I'm not sure how gedit should behave in this case.
Stewart: are you still able to reproduce it?
I could not refetch the file mentioned in the existing report, but i grabbed an RTF file and inserted a null character, and instead got this message (and similar for each of the encoding options in open): "Could not open the file "/home/stewart/test.rtf" using the Western (ISO-8859-15) character coding. Please, check that you are not trying to open a binary file and that you selected the right character coding in the 'Open File...' (or 'Open Location') dialog and try again." which is better than a crash - but i'm wondering if there could be a better way of dealing with this (such as "force" an encoding)? Currently using the debian (sid) package for: ii gedit 2.4.1-1 light-weight text editor
*** Bug 133207 has been marked as a duplicate of this bug. ***
We have revamped the encoding conversion code and now uses gio... let's close this.