Description of problem: After upgrade to gphoto2-2.3.1-1.fc5 no image thumbnails shown when importing photos from USB mass-storage camera (Samsung DigiMax 410) with F-Spot or gThumb Version-Release number of selected component (if applicable): gphoto2-2.3.1-1.fc5 How reproducible: Always Steps to Reproduce: 1. Import images with f-spot or gthumb. 2. 3. Actual results: Image thumbnails not shown in import dialogs. Expected results: Display image thumbnails. Additional info:
Could you please send the description and debug log file: gphoto2 --debug --debug-logfile=my-logfile.txt -T to gphoto-devel.net ? The upstream should be aware of it as well to fix it in the next release as this seems to be an apparent regression.
Created attachment 145969 [details] Log file
Which platform do you use? Is it x86_64?
No, it is i386.
*** Bug 222528 has been marked as a duplicate of this bug. ***
Marcus, the problem is that gphoto2-2.3.1 requires at least libexif-0.6.13, but we have libexif-0.6.12 in FC5 so that the configure script refuses to use it. Should I also request update of libexif to FC5 or will gphoto2 work also with libexif-0.6.12 so that I can force it to the configure script?
in my eyes you can just patch the libgphoto2 configure.ac to only require the 0.6.12 version. While there are bugfixes in libexif 0.6.13, none of them are actually necessary for libgphoto2 if I remember correctly. (I am not sure why the requirement got bumped.)
Could you please test the following packages whether it fixes the problem for you? http://people.redhat.com/jnovy/files/gphoto2-2.3.1-2.i386.rpm http://people.redhat.com/jnovy/files/gphoto2-devel-2.3.1-2.i386.rpm I'll release updates then.
On x86_64 the problem has been resolved with the latest update: gphoto2.x86_64 2.3.1-3.fc5
Ok, closing ERRATA. Thanks.
To comment #6: I filled bug #222271 for this issue. May be that bug will be closed accordingly.
*** Bug 222271 has been marked as a duplicate of this bug. ***
gphoto2-2.3.1-3.fc6 has been pushed for fc6, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.