gPhoto / Bugs / #789 Error when transfer more then 3 photos

Elix - 2009-04-16

an all white photo (converted from ppm to png)

White photo.ppm.png

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marcus Meissner - 2009-04-16

assigned_to: nobody --> kilgota
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marcus Meissner - 2009-04-16

I merged over the trunk version of the driver for 2.4.5

but this 3 image issue is strange

reassign to camlib maintainer

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Theodore Kilgore - 2009-04-17

I just downloaded a fresh copy of libgphoto2-2.4.5, installed it, and tested one of my SQ905C cameras. I filled the entire camera with frames and had no trouble downloading them. Since the bug is not thus duplicated, things become more difficult. There could be a myriad of reasons for the problem. However, there was no problem running under libgphoto2-2.4.4 and the problem has appeared in libgphoto2-2.4.5. Since there have been no code changes between these two libgphoto2 versions in camlibs/digigr8, which supports this camera, it would seem that the problem lies in some other direction. Whether the issue is one of hardware (deteriorating USB cable?) or is a kernel issue (was the kernel changed in the meantime, too?), or is still some other problem could perhaps be detected by debugging and experimentation, combined with an exact description of the hardware and of the other relevant software versions on the machine. And besides all of this it could even be the camera. These are cheap cameras, and quite possibly some of them are buggy the day they leave the factory.

I would need, in addition to the information that the bug exists, at least the following (in no exact order):

1. kernel version which is being used, on which distro

2. report of results of experimentation with another USB cable (if at all possible, please)

3. libusb version

4. description of the hardware of the machine. For example, output of the command "cat /proc/cpuinfo" and the output of lspci and also were there any other USB devices hooked up?

5. Was the camera being run through a USB hub?

6. Was this failure occurring with a gphoto command (such as gphoto2 -P, for example) being run at the command line, or did the failure occur while some other program is calling upon the libgphoto2 functionality? If so, then there is the possibility that the libgphoto2 upgrade has affected the functioning of that other software.

7. ???

The submitter should feel free to contact me, and we can try to track down the source of the problem.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Elix - 2009-04-17

1. Kernel: Darwin 9.6.0
OS: Mac OS X 10.5.6 (9G55)
2. Same results
3. libusb 1.0.0
4. The computer is an Apple iBook G4 1,33 GHz, with 1,25 GB of RAM and 2 USB 2.0 ports
5. I haven't any USB Hub for try...
6. The program doesn't return any error and gphoto is the only program that use libgphoto2
7. The USB cable seems in perfect conditions

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marcus Meissner - 2009-04-17

can you capture a debug trace for this and attach it here?

Like:
gphoto2 -P --debug --debug-logfile=xx.log

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marcus Meissner - 2009-04-17

i guess at some point in time we read 0xff bytes, which in turn will turn into whitepixels. :/

need to see the logfile though.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Elix - 2009-04-18

This is the link for th debug file (17,4MB): http://dl.getdropbox.com/u/583046/debug.log

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marcus Meissner - 2009-04-18

15.457399 context(2): Downloading 'pict004.ppm' from folder '/'...
15.459692 gphoto2-filesystem(2): Lookup folder '/'...
15.459780 gphoto2-filesystem(2): Found! / is 0x1006b0
15.459832 digigr8/digigr8/library.c(2): Fetch entry 2

15.459876 gphoto2-port(2): Reading 32768=0x8000 bytes from port...
20.462472 gphoto2-port(2): Could only read 0 out of 32768 byte(s)
20.462600 gphoto2-port(3): Empty hexdump of empty buffer
20.462628 gphoto2-port(2): Reading 32768=0x8000 bytes from port...
25.466314 gphoto2-port(2): Could only read 0 out of 32768 byte(s)
25.466472 gphoto2-port(3): Empty hexdump of empty buffer
25.466525 gphoto2-port(2): Reading 32768=0x8000 bytes from port...
30.469183 gphoto2-port(2): Could only read 0 out of 32768 byte(s)
30.469348 gphoto2-port(3): Empty hexdump of empty buffer
30.469420 gphoto2-port(2): Reading 32768=0x8000 bytes from port...
...

its expecting data from the camera, but not reading any.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marcus Meissner - 2009-04-18

It does

Fetch entry 3
... data flows ...
and then

Fetch entry 2
.... data does not flow ...

I think the issue is that it does not wrap back to 0 so the "ongoing" download is not working

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Marcus Meissner - 2009-04-19

I changed the lowlevel filesystem code in 2.4.5 which causes this symptom.

You can either use 2.4.4 (the camera driver has not changed actually), or try a test snapshot
until the next release happens.

test snapshot is at :
http://www.lst.de/~mm/libgphoto2-2.4.5.2.tar.bz2

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Error when transfer more then 3 photos - Che-Ez Snap SNAP-U

Group

Searches

Help

#789 Error when transfer more then 3 photos - Che-Ez Snap SNAP-U

Discussion