Menu
▾
▴
[gphoto-bugs] [ gphoto-Bugs-1393207 ] Thumbnail download fails on Kodak Z700
|
From: SourceForge.net <no...@so...> - 2005-12-30 11:44:09
|
Bugs item #1393207, was opened at 2005-12-29 22:41 Message generated for change (Comment added) made by marcusmeissner You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108874&aid=1393207&group_id=8874 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Austin Clements (amthrax) Assigned to: Nobody/Anonymous (nobody) Summary: Thumbnail download fails on Kodak Z700 Initial Comment: The Kodak Z700 has three control files that appear in "/store_00020001": DCEMAIL.ABK, DDISCVRY.DPS, and LABELCTB.LCB (I believe these are related to its "easy share" features). If gphoto attempts to retrieve a thumbnail of any of these files, the Kodak Z700 responds unexpectedly and stops responding to any further retrieval requests. "gphoto -T" partially works because it traverses the camera's file system in such a way that it downloads the actual photo thumbnails from /store_00010001 before attempting to download the "thumbnails" of the control files. However, as soon as it reaches a control file, it fails and exits. Attached is the output of "gphoto2 --debug -T" (with the middle removed to make it fit in SF's limits). At line 1796, it begins retrieving PTP object information for these control files. At line 3251, it begins traversing into /store_0002001 for thumbnail retrieval. This is more problematic for other applications that use libgphoto2. For example, digikam traverses the file system in a different order, so it attempts to retrieve thumbnails of the control files before reaching the photos. This causes the protocol to lock up, so it cannot retrieve any of the thumbnails. Worse, it then cannot retrieve the actual photos. As an experiment, I added a hack to Digikam to avoid downloading thumbnails of any files that did not begin with "100" (all of the photos on the Z700 appear to be prefixed with 100) and everything worked. (My bug report to digikam can be found at http://bugs.kde.org/show_bug.cgi?id=119170 ) If desired, I can attach a gphoto2 debug log of digikam's retrieval process. The gphoto2 tool should probably not try to retrieve thumbnails of these files and libgphoto2 should not freeze up if it is told to download a thumbnail of a file that does not have a thumbnail. Possibly, gphoto2 -P should not even download these files (though this does work), because they are not technically photos. A few points I found interesting in the attached log: ---------------------------------------------------------------------- >Comment By: Marcus Meissner (marcusmeissner) Date: 2005-12-30 11:44 Message: Logged In: YES user_id=48092 you are right, the communication stopped. I will change the code so that it tries this only for JPEG images. will be in 2.2. ---------------------------------------------------------------------- Comment By: Austin Clements (amthrax) Date: 2005-12-30 10:26 Message: Logged In: YES user_id=160535 I'm attaching the libgphoto2 debug output produced when Digikam tries to construct its thumbnail view. You can see on line 1749 it starts downloading thumbnails, starting with DCEMAIL.ABK. I'm not sure what libgphoto2 is expecting in the response from the camera, but it's getting the first 10 bytes of that file, which appears to be confusing it. After this, Digikam tries to get the remainder of the files, but never receives any further responses from the camera. Starting at line 2264 (sorry, forgot to fflush), you can see the error responses gp_camera_file_get returns. ---------------------------------------------------------------------- Comment By: Marcus Meissner (marcusmeissner) Date: 2005-12-30 09:07 Message: Logged In: YES user_id=48092 hmm. The trace does not include a lockup or protocol errors ... It has just a "not supported" error, which should probably have been ignored. Are there any gphoto errors on digikams console output (likely in ~/.xsession-errors when started from the menu)? ---------------------------------------------------------------------- Comment By: Marcus Meissner (marcusmeissner) Date: 2005-12-29 22:58 Message: Logged In: YES user_id=48092 hmm. The trace does not include a lockup or protocol errors ... It has just a "not supported" error, which should probably have been ignored. Are there any gphoto errors on digikams console output (likely in ~/.xsession-errors when started from the menu)? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=108874&aid=1393207&group_id=8874 |