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 790844 - Support RAW photos when navigating forward/back
Support RAW photos when navigating forward/back
Status: RESOLVED DUPLICATE of bug 344601
Product: eog
Classification: Core
Component: collection
3.26.x
Other Linux
: Normal normal
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-11-26 10:36 UTC by Anton Keks
Modified: 2018-04-04 14:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Anton Keks 2017-11-26 10:36:58 UTC 
Currently, RAW photos are displayed only one-by-one (using the embedded JPEG previews that all cameras save), but pressing forward/back arrows doesn't work - probably because raw file extensions are not recognized.

Please support most common RAW file extensions for collections/navigation.
These are at least CR2, CRW, NEF, PEF, DNG (as well as lowercase variants)

That is a really long standing usability issue for photographers on Linux. Thanks!
Comment 1 Felix Riemann 2017-12-10 13:35:21 UTC 
Selecting the files to add to the collection (and thus allowing Next/Prev) is not handled by file extension but through the mime type GIO reports for them. The list of supported mime types is determined by the list of installed loaders for gdk-pixbuf.

If you don't get the other RAW images added to your collection you'll have to install a loader that supports them. libopenraw ships one for example.

Without such a loader showing RAW files may work in formats that use the basic structure of TIFF files, like CR2.
Comment 2 Felix Riemann 2018-04-04 14:04:52 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 344601 ***