GNOME Bugzilla – Bug 310554
Gedit can't save with different encoding.
Last modified: 2005-07-21 22:17:59 UTC
When you type in some text with Gedit and you want to save it the first time, then you get a FileChooser Dialog prompted that asks you for the Filename and the charset encoding. It's only possible to save with UTF8. Trying to save it with ISO-8859-15 or something else will disable (deactivate) the 'Save' button. CVS But also stable versions (released Tarballs).
I cannot reproduce it with gnome 2.10.3 on Ubuntu.
paolo pbor: are you able to reproduce bug #310554? pbor no pbor I don't even see code that sets the sensitivity of the button at all paolo yep paolo yep, I don't see how it could be possible Could you please try to give us more info on your configuration? Or, if you are a developer, could you please try to track the problem in the code?
Created attachment 49532 [details] Illustration I was refering to the save dialog as you can see in the attachment (PNG). When changing the encoding from UTF8 to ISO-8859-15 (for example) then the save button next to it will not allow to save. You can press like mad on the button and nothing much happens. > I cannot reproduce it with gnome 2.10.3 on Ubuntu. Please pardon when I say this but I doubt that Ubuntu with GNOME 2.10.3 is the right version for coding on CVS HEAD related material. It is required to compile GNOME CVS HEAD from time to time and make sure that the stuff you've been working on still works. If we all use different GNOME versions, that is, the one uses FC4 + provided GNOME and codes on one specific HEAD material, the other uses DEBIAN + provided GNOME and codes on one specific HEAD material, the other uses whatever + provided GNOME and codes on one specific HEAD material then we end up in a mixture of stuff that depends on the GNOME that comes with the developers specially shipped GNOME version on their distro. It may work with other things or it may not. And in this case it doesn't. The GNOME version I've been using is GNOME from CVS HEAD that is the GNOME that moves towards GNOME 2.12 (which release might be in two months IIRC). But the problems I describe also exist with lates release GNOME 2.11.x version (that includes all the libraries, tarballs etc. which I regulary test when updating a new version of CVSGnome). Hope I was informative and helpful for tracking the issues down.
Works fine for me in CVS HEAD and gedit 2.10.3 package on Breezy (which, by the way, are exactly the same code at the moment). The package maintainers know what they're doing and you should probably avoid lecturing them about what version of their own software they should or should not be running.
I confirm that cvs HEAD is exactly the same as gedit 2.10.3 (except from some translations) since all the developement is happening on a branch. Anyway for now I am resetting to NEEDINFO in case you can try to investigate why it's happening on your system. We can always close the bug at a later time.
I investigated a bit more into this and now believe that this might be a GTK+ GtkFileChooser related bug ? I have illustrated this with a few screenshots so you can comment on this. The reason why I believe this to be GTK+ related (also CVS HEAD) is that I saw some other strange issues with GtkFileChooser under The Gimp for quite some time that e.g. all my homedir pictures show up in the root directory (they are shown in root but they are not in root, they are in home). I believe this is the same triggered issue e.g. some filenames show up in GtkFileChoosers code that aren't there where they should due to wrong memory allocation, free'ing, concatenating, object or whatever. Is it possible to reallocate this bugreport to the GTK+ people so they can comment on it ?
Created attachment 49535 [details] Illustration #1
Created attachment 49537 [details] Illustration #2
Created attachment 49538 [details] Illustration #3
Created attachment 49539 [details] Illustration #4
Created attachment 49541 [details] Gimp triggering #1
Created attachment 49542 [details] Gimp triggering #2
As you can see I am triggering similar stuff "ghosted entries" from GtkFileChooser from within GIMP as well, this happens every now and then and quitting GIMP and restarting it solves it usually. But Gedit seem to be more affected by it due to whatever reasons so I assumed them to be two different bugs. Unfortunately the internals of GtkFileChooser seem to cause these issues. I will open a new bugreport about this to the GTK+ people and reference to this bugreport.
Just filled this bugreport: http://bugzilla.gnome.org/show_bug.cgi?id=311187
Yep, looks like a GtkFileChooser issue (I asked federico on irc) I was going to transfer this bug to gtk, but since you filed a new one I'll just mark this as a dup of the other. Thanks for the bugreport. *** This bug has been marked as a duplicate of 311187 ***