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 578888 - Can no longer import Canon RAW files (.CR2)
Can no longer import Canon RAW files (.CR2)
Status: RESOLVED NOTGNOME
Product: gthumb
Classification: Other
Component: general
2.10.x
Other Linux
: Normal normal
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2009-04-13 22:38 UTC by richard
Modified: 2009-04-14 01:41 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description richard 2009-04-13 22:38:50 UTC
Hello,

with recent versions of gthumb (at least 3:2.10.10-2 and 3:2.10.11-1 in Debian), when I connect my Canon EOS 450D to my machine using USB and try to import pictures via PTP using gthumb, this is only possible for JPEG files.

RAW (.CR2) files on the camera do not show up in the preview, and I cannot select and import them. This used to work fine with older versions of the program. Importing and deleting only the JPEGs with gthumb works - after doing that, the import dialog will report that no files are on the camera, even though the RAWs are still there.

Typically, I shoot in RAW+JPEG mode, so there are two versions of each file on the camera, e.g. named IMG_1234.CR2 and IMG_1234.JPG. They both end up in the same directory "/store_00020001/DCIM/100CANON" on the camera's SD card. I can import the RAWs on the command line without problems using "gphoto2 -P".
BTW, "gphoto2 -L" shows the RAWs as "application/x-unknown".

Cheers,

  Richard
Comment 1 Michael Chudobiak 2009-04-13 23:14:21 UTC
You'll need to figure out why the CR2 images are being reported as "application/x-unknown". That is why gThumb ignores them. They should be reported as "image/x-canon-cr2" or something similar.

This isn't a gthumb bug; something else is wrong on your system.

- Mike
Comment 2 richard 2009-04-14 01:41:38 UTC
Thanks for that information! It looks like a libgphoto2 issue, the relevant bug is here:
http://sourceforge.net/tracker/?func=detail&aid=2760486&group_id=8874&atid=108874