After upgrading kde from 4.7 to 4.8 I couldnt preview xcf files any longer.
Using gwenview I get "loading image failed", and in the log I see "Could not generate thumbnail".
I've seen this thread http://forums.opensuse.org/english/get-technical-help-here/applications/472010-kde-4-8-0-gwenview-wont-display-xcf-files-error-while-reading-metadata.html where the workaround is downgrading to 4.7 which Ive done.
It doesnt seem like a gwenview issue since I've kept kde-base in 4.7 and upgraded gwenview to 4.8 and is still working. Same behaviour using 4.9.2.
Thanks for any hints!
Steps to Reproduce:
2.open a folder with gimp xcf files
3.double click a .xcf file
I get "loading image failed", and in the log I see "Could not generate thumbnail".
show a preview of the gimp xcf image.
it started happening when upgrading from kde 4.7 to 4.8, but its still happening with 4.9.2
I've downgraded to 4.7 where is working normally.
Can you reproduce the problem with a freshly created user account? Does it happen with all .xcf files?
I quickly tested with those from the calligra test suite, and gwenview (from KDE 4.9.2) could load them all. See https://projects.kde.org/projects/calligra/repository/revisions/master/show/krita/plugins/formats/xcf/tests/data/sources
If it only works with specific files, please attach a file that does not work.
If you can provide the information requested in comment #1, please add it.
(In reply to comment #1)
> Can you reproduce the problem with a freshly created user account?
yes, it happens with a freshly created user account.
> Does it happen with all .xcf files?
it does with all new xcf files. If a folder contains a .xcf that has been already previewed, it shows the preview from the cache (I think)
let me know any other tests...
Thanks for the update, I have no idea why it works here, but not on your system.
(In reply to comment #4)
> Thanks for the update, I have no idea why it works here, but not on your
It doenst in both my pcs (archlinux both). I thought it could be a misconfigutraion issue until I saw the post mentioned on the first comment where people using opensuse were experiencing the same.
Setting status correctly.
same issue as @Mattas here.
Running an up-to-date KDE SC 4.9.2 on Arch Linux x86_64.
*** Bug 309465 has been marked as a duplicate of this bug. ***
Does opening those .xcf files work in kolourpaint?
@Cristoph: yes, no problem opening any .xcf file with KolourPaint 4.9.2
Thanks, so the xcf loader in kdelibs actually works. No idea why other programs fail to load .xcf files. Maybe the list of allowed extensions has been changed in those applications?
Can someone check, which applications work, and which do not? The bug here is reported for digiKam and gwenview. Can you confirm? What about Dolphin thumbnail previews?
* UPDATE *
.xcf files works with KolourPaint, Dolphin previews, Plasma Desktop Files previews, showFoto, DigiKam... and now Gwenview :P
Besides the usual system update stuff I don't what have changed but now everything is working okay on Arch Linux 4.9.2.
Anyone else? Please confirm.
(In reply to comment #12)
> * UPDATE *
> .xcf files works with KolourPaint, Dolphin previews, Plasma Desktop Files
> previews, showFoto, DigiKam... and now Gwenview :P
> Besides the usual system update stuff I don't what have changed but now
> everything is working okay on Arch Linux 4.9.2.
> Anyone else? Please confirm.
Im seeing some strange behaviour. Gwenview seems to be able to preview some new files but some others no.
I've tried saving a working file with a different name and wont work.
I tried deleting gwenview's recent folder and .thumbnails but nothing new.
Kolourpaint follows the same results, the files working in gwenview open in kolourpaint, and the ones
not previewing in gwenview give this error "Could not open "TEST4.xcf" - unsupported image format.
The file may be corrupt.".
If I save a new test file with just a plain color layer the preview works, but if I add a layer with some transparency and save over, again I get the error.
could it be related to Gimp version? Im using 2.8.0, and tried with 2.8.2 but seeing similar results with both.
If you can attach an .xcf file that KolourPaint cannot open, I can check, if it is indeed corrupt.
Created attachment 75113 [details]
test xcf notworking
Created attachment 75114 [details]
test xcf working
Thanks, it is a file with a layer larger than the image. The commit for bug 234030 added a check to not load those files, because they were treated as corrupt. Removing the check makes it load. I will improve the checks for 4.9.4 release.
Good news, thank you =)
Git commit b26309ebb120aceb2cdd4dc26925f4c786d70673 by Christoph Feck.
Committed on 24/11/2012 at 23:52.
Pushed by cfeck into branch 'KDE/4.9'.
Add tolerance to layer size sanity check
Commit for bug 234030 caused a regression with images
that have layers larger than the canvas.
The factor 2 is arbitrary, but is hopefully sufficient.
M +1 -1 kimgio/xcf.cpp
Awesome, thank you!
just updated to 4.9.4!! working flawlessly!!
(In reply to comment #20)
> Git commit b26309ebb120aceb2cdd4dc26925f4c786d70673 by Christoph Feck.
> Add tolerance to layer size sanity check
> > Commit for bug 234030 caused a regression with images
> that have layers larger than the canvas.
> > The factor 2 is arbitrary, but is hopefully sufficient.
> FIXED-IN: 4.9.4
Hi, sorry to bring this issue back, but I'm still having issues with some files. I believe its related to the factor set in the 4.9.4 fix.
I enclose two sample files.
Created attachment 76257 [details]
test post 4.9.4 fix. not working file
Created attachment 76258 [details]
test post 4.9.4 fix. working file
Yes, the image is 1000x1000, the layer is 2200x1400. What is the reason for layers larger than the image, i.e. what workflow creates those files?
(In reply to comment #26)
> Yes, the image is 1000x1000, the layer is 2200x1400. What is the reason for
> layers larger than the image, i.e. what workflow creates those files?
-I usually add photos straight from the camera to web sized files and use just parts of the photos, make an export and then move the photos to another parts, export and so on.
-Also I make designs that I later use in blender, and I use a same xcf to test different screenshots or test-frames, so I need big layers to move around and try several settings.
How big? Instead of using a factor, I should probably hardcode a safe maximum size for a layer. I did not find any limitation imposed by GIMP itself, so I have to select a sane limit. Would 16384x16384 be enough? That's already 2 GB memory used to load the layer.
(In reply to comment #28)
> How big? Instead of using a factor, I should probably hardcode a safe
> maximum size for a layer. I did not find any limitation imposed by GIMP
> itself, so I have to select a sane limit. Would 16384x16384 be enough?
Interesting point. I have used files (and layers) of more than 20000 pixels wide, but probably you wouldnt want to preview those... :P
Git commit 16f4dc07334af5a0eca754868eafd89e7908e2b3 by Christoph Feck.
Committed on 27/01/2013 at 14:39.
Pushed by cfeck into branch 'KDE/4.10'.
Even more tolerance in layer size sanity check
Appearantly, there are files out there with layers much
larger than the actual image. The layer size is now checked
against larger limits (32K in each dimension, 256M total).
M +1 -1 kimgio/xcf.cpp