gvfsd-gphoto2 unmount leaves camera in a bad state

[Chris Wulff]

Binary package hint: gvfs

When unmounting a Kodak V1253 PTP camera the device is left in a bad state. Since this is automounted on connection, you can't use F-Spot or other applications which require it to be unmounted first.

If I kill off gvfs-gphoto2-volume-monitor (to prevent the automount from happening) and power cycle the camera, applications like F-Spot will work fine. If I then mount the volume I can access the files in nautilus fine, but once unmounted, the next application trying to access the camera will hang (including mounting again.)

The attached patch works around this problem by resetting the camera after a few tries but this only patches the symptom and not the initial problem (there is still a delay while the camera is reset to get it out of the bad state.)

Other applications can be opened and closed multiple times without problems. This leads me to believe that something in the unmount is not correctly closing out the camera session.

PTP symptom from the application after the unmount (from gphoto2 -l --debug):

 * Camera continuously returns 0x2004 (Invalid TrasactionID) from opensession (this will repeat forever without the attached patch)

0.143070 ptp(2): PTP: Opening session
0.143092 gphoto2-port(2): Writing 16=0x10 byte(s) to port...
0.143112 gphoto2-port(3): Hexdump of 16 = 0x10 bytes follows:
0000 10 00 00 00 01 00 02 10-00 00 00 00 01 00 00 00 ................

0.143383 ptp2/ptp_usb_getresp(2): reading response
0.143404 ptp2/ptp_usb_getpacket(2): getting next ptp packet
0.143423 gphoto2-port(2): Reading 512=0x200 bytes from port...
0.144372 gphoto2-port(2): Could only read 12 out of 512 byte(s)
0.144392 gphoto2-port(3): Hexdump of 12 = 0xc bytes follows:
0000 0c 00 00 00 03 00 04 20-00 00 00 00 ....... ....

0.144410 ptp2/usb_getresp(0): request code 0x1002 getting resp error 0x2004

Package versions:

  gvfs-backends: 1.4.1-0ubuntu1
  libgphoto2-2: 2.4.6-1ubuntu6

[Sebastien Bacher (seb128)]

Thank you for your bug report, the bug is an upstream one and should be sent to GNOME by somebody having the issue

[Pedro Villavicencio (pedro)]

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=608279