Version: 2.3 (using KDE 4.6.2) OS: Linux When I edit any .jpeg or .jpg image and I want to save the made changes trough File > Save or File > Save As... (the latter, saving the file with the changes in the same directory from where I opened it) I get this error message: Error - Krita Could not save I try to save the edited images, with the defaults options save, that appears in the pop up when Krita receives the order of saving. Also, I have checked the permissions of the directory where I try to save the edited images: $ ls -l drwxr-xr-x 16 zuargo users 36864 abr 11 13:16 Imágenes As you see the user zuargo (me), has permissions of reading,, writing and executing in the directory *Imágenes*. Inside this folder, I try to save the edited images. Aditionally, I have tried to save the images edited inside another folder (inside my home directory, called just *zuargo*) by File > Save As... and it was successful. Also, I have tried to save another edited images in the same directory (*Imágenes*) but, those has, by default, other file extensions like .png, .gif and .jp2 (I didn't change the file extension). I had no problem with this. I think the problem is due to the name of the folder where I try to save the edited .jpg images, it is *Imágenes*. This one has a spanish character called "tilde" above the *a* letter. I think this becouse I tried to save another edited .jpg image inside another folder that has this spanish character called "tilde" and I had the same error. Krita could not save the changes. And I insist, the problem is, only, saving edited .jpg images inside folders that has in their names a "tilde". Reproducible: Always Steps to Reproduce: 1.-Make a directory in their name has a "tilde", for example Imágenes. 2.-Edit a jpg image and try to save this one inside the named directory. Actual Results: The edited image is not saved Expected Results: The edited image is saved OS: ArchLinux (i686) release 2.6.37-pae Compiler: gcc
Confirmed. the jpg filter cannot save to directories with a ã in them -- probably other unicode characters have the same problem.
*** This bug has been marked as a duplicate of bug 268007 ***