GNOME Bugzilla – Bug 631562
gphoto backend does not work with libgphoto2 >= 2.4.10
Last modified: 2010-10-29 02:24:49 UTC
Created attachment 171853 [details] [review] workaround suggested by Krzysztof Kotlenga on gphoto-devel $Summary says all. The problem was described here: http://sourceforge.net/mailarchive/message.php?msg_name=20100901193427.GB24225%40foo steps to reproduce: get usb port of the camera try gvfs-mount "gphoto2://[usb:012345]/" gvfs-mount will fail to mount The workaround suggested in above post solves the problem.
Comment on attachment 171853 [details] [review] workaround suggested by Krzysztof Kotlenga on gphoto-devel Please mark patches as such when uploading them
Created attachment 173411 [details] [review] Use correct "usb:" address for GPhoto mounts with gudev gphoto2 expects the usb:X,X addresses to use the dirname and device names from libusb, which are zero-padded. Given that it's what udev gives us, just don't transform it to an int before printing.
Please test with this patch, it should fix it properly, and not break other versions (that use HAL).
Note for self, also at: https://bugzilla.redhat.com/show_bug.cgi?id=642836
(In reply to comment #3) > Please test with this patch, it should fix it properly, and not break other > versions (that use HAL). I have tested this patch in Fedora 14 (udev) and I can confirm that it solves the problem.
commit 089ba0b1af08f8b7506bd867a415e197f4017ec0 Author: Bastien Nocera <hadess@hadess.net> Date: Thu Oct 28 17:25:12 2010 +0100 Use correct "usb:" address for GPhoto mounts with gudev gphoto2 expects the usb:X,X addresses to use the dirname and device names from libusb, which are zero-padded. Given that it's what udev gives us, just don't transform it to an int before printing. https://bugzilla.gnome.org/show_bug.cgi?id=631562