Created attachment 1001947 [details] A photo taken with “Canon EOS DIGITAL REBEL” Description of problem: An infinity process is started when a photo from “Canon EOS DIGITAL REBEL” is opened in Darktable darkroom. Version-Release number of selected component (if applicable): 1.6.3-1 How reproducible: 100% Steps to Reproduce: 1. Open any CRW image taken with “Canon EOS DIGITAL REBEL” 2. Switch to darkroom. Actual results: A Never-ending message "Working..." Expected results: A photo should be opened in the darkroom. Additional info: Next time the attempt to open the same photo results in a marked as unreadable image in the ligthtable. There was no such problems with Darktable 1.2.3.
It has been fixed in upstream When 1.6.4 comes out the camera will work again. http://www.darktable.org/redmine/issues/10370
darktable-1.6.3-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/darktable-1.6.3-2.fc20
darktable-1.6.3-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/darktable-1.6.3-2.fc21
darktable-1.6.3-2.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/darktable-1.6.3-2.fc22
Package darktable-1.6.3-2.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing darktable-1.6.3-2.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-4543/darktable-1.6.3-2.fc21 then log in and leave karma (feedback).
darktable-1.6.3-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
darktable-1.6.3-2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
darktable-1.6.3-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.