GNOME Bugzilla – Bug 138158
FileChooser can't save files
Last modified: 2011-02-04 16:16:32 UTC
What happens: I open gedit, write something, then choose save. The default file name "no title" in my language (portuguese) has an accentuated character: "sem título". However, the name I see on the entry box of the fileChooser is just "sem t", meaning that the accentuated character caused an error of some sort. And when I try to save the file (with the default filename or any other I choose) it says something like: "Couldn't build the file name from /foo/bar and test.txt" What I expected: That the full default name for the file got correctly displayed, and that I could actually save the file! ;) Additional Information: It works fine from epiphany because it doesn't use the default filename with the accentuated character; My locale is not set to utf-8, but of course, the translations are in utf-8;
Can you please try again with the latest version of GTK+?
tried with GTK+ from cvs, the same thing happens: The filename entry is empty untill I click on it, and only then "Sem t" appears. I am able to save the file if I click on the entry and press a letter very fast so the default name doesn't appear. This is what appears in the terminal when I click Save or Save as: ** (gedit:5883): WARNING **: Invalid UTF8 string passed to pango_layout_set_text() ** (gedit:5883): WARNING **: Invalid UTF8 string passed to pango_layout_set_text() ** (gedit:5883): CRITICAL **: file pango-layout.c: line 1769 (pango_layout_get_cursor_pos): assertion `index >= 0 && index <= layout->length' failed ** (gedit:5883): CRITICAL **: file pango-layout.c: line 1769 (pango_layout_get_cursor_pos): assertion `index >= 0 && index <= layout->length' failed And when I try to edit the default filename: "Sem t", this error appears at every keypress: ** (gedit:5883): WARNING **: Invalid UTF8 string passed to pango_layout_set_text()
This is related to bug #140532. I think gedit has another bug whereby it can't display the filenames (e.g. in the notebook tabs) even when they match the encoding specified in G_FILENAME_ENCODING. I'll look for it and file it later.
OK, I found the real cause for the warnings you get. I've filed bug #141844 about this, so I'll mark this one as a duplicate. Note that bug #140532 is still open, and this bug depends on that one. *** This bug has been marked as a duplicate of 141844 ***