#944 PTP I/O error with Canon cameras on amd64
gphoto consistently fails when connecting a Canon 40D via PTP on amd64 systems with an "Unspecified error".
This has been seen on 64-bit Ubuntu 12.04, 12.10, 13.04 (latest build as of 3/18/2013) on amd64 systems. It works fine on the same hardware with 32-bit Ubuntu.
The full log file for gphoto2 --debug --debug-logfile=gphoto.log -L has been attached.
Here is one of the setups that doesn't work:
Linux 3.2.0-39-generic #62-Ubuntu SMP Thu Feb 28 00:28:53 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
gphoto2 2.4.11 gcc, popt(m), exif, cdk, aa, jpeg, readline
libgphoto2 2.4.13 gcc, ltdl, EXIF
libgphoto2_port 0.8.0 gcc, ltdl, USB (libusb0), serial without locking
(Again, the problem persists on 13.04, which I believe is using gphoto2 2.5.1.)
A related bug in Launchpad for Ubuntu seems to be this: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1094888
if the camera is attached to a USB 3 port, attach it to a USB 2 port and try again.
Thanks for the response! I tried again (this time under Ubuntu 13.04 to give you a variety of environments), and I get the same result on both the USB2 and USB3 port of the laptop.
I've attached both the USB2 logfile.
The system here:
Linux Sony-SVS15118FXB 3.8.0-12-generic #21-Ubuntu SMP Thu Mar 7 19:08:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
gphoto2 2.4.14 gcc, popt(m), exif, cdk, no aa, jpeg, readline
libgphoto2 2.4.14 gcc, ltdl, EXIF
libgphoto2_port 0.8.0 gcc, ltdl, USB (libusb0), serial without locking
Btw, seems I was wrong, Ubuntu 13.04 is still using gphoto2 2.4.14.
And here is the USB3 log:
no ideas currently ...
only thing you could try is this patch which helps with usb 3 ports, but it is likely not the same issue
(also it might yet be another gvfs gphoto2 slave interaction issue)
Seems to be a problem with interference from gvfs-gphoto2-volume-monitor - some people got around it by killing the process. When I remove the executable flag of that file, I can reliably download images. Question is - which system is the culprit here? Is gphoto just minding its own business, and gvfs needs to be taught some manners?
Basically it is gvfs-gphoto2-volume-monitor that need to be taught manners. I believe there is a bug in Gnome bugzilla, but the original author of the package is now prisoner in the Google void - ie he stopped contributing - and I'm not sure who takes care of this today.
The bigger picture is that we do need some sort of arbitrator for cameras and libgphoto2 to directly make use of that.
Yes, arbitrage between gvfs and other libgphoto2 frontends is the issue here. Kind of hard to solve without putting in effort into a GphotoKit daemon or similar.