GNOME Bugzilla – Bug 384762
GIMP 2.2.13 fails to open *.psd-files (previously edited and saved in same version)
Last modified: 2008-01-15 13:22:49 UTC
How to reproduce: 1. Open a .psd-file saved in a previous version of GIMP. 2. Edit the file and save the changes. 3. Trying to open it later results in this error message (roughly translated, that the plugin was unable to open the image): GIMP Melding Åpning av «/lager/prosjekter/Julekort/2006/Julekort-forside.psd» feilet: Programtillegg kunne ikke åpne bilde
Can you attach a small example file to this bug report?
Created attachment 78149 [details] File that GIMP has made, but is unable to open The file I had a problem with is 22,2 MB. I created this file for cutting and pasting into that, and it seems that attempting to open this results in the same error message.
So it seems that the scope of this bug is somewhat larger than I first described. GIMP 2.2.13 does not open .psd-files saved in the same version at all, not just files that has been changed after being created in a previous version.
CVS HEAD fails to open the file and says: Error: layer blend signature is incorrect. :-( Confirming (even though i didn't try 2.2)
2.2.13 fails too.
This seems to be a duplicate of bug #335130. If someone could port the patch attached there to the 2.2 branch, that should fix the issue.
singularity: Please can you checkout a copy of the gimp-2-2 branch from Subversion and compile it and verify if this problem you reported is fixed? I have tested it here and it fixes the issue, but it'd be nice if you also confirm it.
Works for me with gimp-2-2.
2007-02-03 Mukund Sivaraman <muks@mukund.org> * plug-ins/common/psd_save.c: Backported fixes from bug #335130 to this branch to make psd_save work properly on 64-bit platforms; this should fix #384762; also fixed a warning about incompatible data types This means that the next release in the 2.2 series (2.2.14) should write correct files again. Unfortunately the PSD files written with the broken version on 64bit machines are broken and I don't see any way to work around that problem in the loader plug-in. Closing as FIXED.