After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 326838 - Support for GIMP file types
Support for GIMP file types
Product: f-spot
Classification: Other
Component: General
Other All
: Normal enhancement
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Reported: 2006-01-13 13:11 UTC by Jacques Botha
Modified: 2018-07-12 00:05 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Jacques Botha 2006-01-13 13:11:15 UTC
Thanks for the CR2 and CRW support, it great !!!!! 
Now we just need support for Gimp .xcf file types and we are really sorted ! :)

Comment 1 Larry Ewing 2006-02-26 04:40:55 UTC
supporting full dispay of xcf files is not something that is simple to do because it implies duplicating the concept of layers and blending modes but there might be something we could do.
Comment 2 Bengt Thuree 2007-11-26 17:28:50 UTC
Do we still have a problem with .xcf file support?
Comment 3 Maxxer 2007-11-27 08:24:26 UTC
(In reply to comment #2)
> Do we still have a problem with .xcf file support?

Yes. DnD silently ignores xcf files.
Comment 4 Martin Schwenke 2008-10-25 22:05:49 UTC
Would it be possible to add a read-only viewing mode for XCF files?  They could just be converted to JPG for display...

This, along with being able to import extra versions (for example, an XCF generated by doing something funky with UFRAW), is really all that is stopping f-spot being used for serious workflow.
Comment 5 Glen Birkbeck 2009-01-25 11:38:37 UTC

I agree with the above comments. If the filetype is something that cannot be displayed in f-spot, then I could live with a default "Image cannot be displayed" message, but to track all my file types within F-Spot, I need RAW (.NEF), GIMP, TIFF and JPEG.

Not having GIMP means I have to "Copy Photo Location" in F-Spot, then "Open Location" in GIMP, and then change the extension to load the GIMP file.

I moved from Windows and PSE with the photo manager and being able to stack all related files in the photo manager has alot of advantages. I also have a whole set of PSD files which I can open in GIMP but F-Spot ignores. Again, I could live with no image preview in F-Spot, but it would make F-Spot feel much more complete to be able to have the files presence acknowledged in F-Spot.
Comment 6 Wouter Bolsterlee (uws) 2009-03-11 00:34:31 UTC
It looks like Stephane Delcroix is working on getting this fixed by implementing XCF support for GdkPixbuf:
Comment 7 Martin Schwenke 2009-03-11 00:56:37 UTC
Wouter, thanks for letting us know.

Stephane, many thanks for working on this.  It is an excellent idea and will help to make F-Spot more awesome!  :-)

peace & happiness,
Comment 8 Stephane Delcroix 2009-04-28 07:49:16 UTC
some update on this...

with an xcf loader, like the one I wrote, f-spot(svn) now display xcf and even allows you to open a jpeg in gimp and save the result back as a xcf in f-spot
Comment 9 Jean-Philippe Fleury 2009-04-28 12:05:09 UTC
(In reply to comment #8)
> allows you to open a jpeg in gimp and save the result back as a xcf in f-spot

Do you mean that a xcf can be a version of a jpg?
Comment 10 Ruben Vermeersch 2010-05-23 15:36:26 UTC
This will require shipping the XCF loader (which we'll have to maintain) or getting it fully upstream. I'd consider embedding it if someone wants to take up active maintenance of it.
Comment 11 André Klapper 2018-07-12 00:05:41 UTC
F-Spot has moved to

If this Bugzilla ticket is still valid in a recent version of F-Spot, please feel free to post this topic as a ticket in the F-Spot project on GitHub.

Closing this report as WONTFIX as part of Bugzilla Housekeeping as we are planning to shut down GNOME Bugzilla in favor of GNOME Gitlab.