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 625771 - Canon Raw Images Don't Work
Canon Raw Images Don't Work
Status: RESOLVED DUPLICATE of bug 624402
Product: f-spot
Classification: Other
Component: General
0.7.1
Other Linux
: Normal normal
: 0.7.2
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2010-08-01 17:25 UTC by johnf
Modified: 2010-08-02 12:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
f-spot --debug output from crash (188.01 KB, text/plain)
2010-08-01 17:25 UTC, johnf
Details

Description johnf 2010-08-01 17:25:58 UTC
Created attachment 166937 [details]
f-spot --debug output from crash

I upgraded to 0.7.1 from the ppa to check out the new RAW support. Before the upgrade I was running the bundled version from ubuntu 10.04.

 Unfortunately, it seems that RAW support, at least with my Canon devices (CR2), has taken a step back. Before I was able to view RAW images, both as thumbnails and full screen. With 0.7.1 I can no longer view RAW images, I sometimes get thumbnails (they may be from my previous installation, it's probably not creating new thumbnails).

To make matters worse, if I try to import photos from my CF card f-spot actually crashes.

I'm running 0.7.1-1~1.gbp0f660e~ppa~lucid0f from this official, stable ppa: http://ppa.launchpad.net/f-spot/f-spot-ppa/ubuntu.

I have attached a log from f-spot --debug. In this log I start f-spot and attempt to view a RAW image. I then put a note into the log "NOTE: Attempting Import Now". I then insert the CF card, triggering an import, f-spot then crashes. If the CF card is already inserted and I manually run Import from the menu it has the same effect.

To my eye the log entries are quite similar for the two failures, though the import is clearly more catastrophic.

I'm very eager to help diagnose and resolve this problem. Please let me know what I can do to help.
Comment 1 johnf 2010-08-01 18:15:36 UTC
I've uploaded a sample image you can use to reproduce the problem. 

http://zioncluster.ca/~johnf/IMG_3833.CR2
Comment 2 Ruben Vermeersch 2010-08-02 12:40:03 UTC
This should be fixed now. Looks like a duplicate of bug 624402.

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