The below mail was send to the gphoto2 mailinglist a couple of days ago, I've not checked but F-14 has the involved gvfs and libgphoto2 versions so this likely needs to be fixed in F-14 too:
As you probably know, GVFS has its gphoto2 backend which detects USB
cameras by listening to (g)udev events having ID_GPHOTO2 property set.
When a camera gets plugged in, it runs this exact code:
port = g_strdup_printf ("usb:%d,%d", bus_num, device_num);
/* Connect to the camera */
context = gp_context_new ();
if (gp_camera_new (&camera) != 0)
if (gp_port_info_list_new (&il) != 0)
if (gp_port_info_list_load (il) != 0)
n = gp_port_info_list_lookup_path (il, port);
if (n == GP_ERROR_UNKNOWN_PORT)
if (gp_port_info_list_get_info (il, n, &info) != 0)
if (gp_camera_set_port_info (camera, info) != 0)
il = NULL;
if (gp_camera_init (camera, context) != 0)
I've just spent quite some time investigating why gp_camera_init()
fails. Boy, that was fun! It turns out that since svn revision 13242 and
13245 libgphoto2 doesn't like when the specified port string differs in
format from what libgphoto2 autodetects: "usb:3,21" vs "usb:003,021".
Do you think it's a GVFS "bug" or not necessarily? My current workaround
is to patch gvfs ("usb:%03d,%03d").
BTW, I find it ugly that libgphoto2 autodetects what was already
autodetected by udev (rules generated by gphoto's own
PS. GNOME users running libgphoto2 >= 2.4.10 and gvfs <= 1.6.3 are going
to be PISSED :)
Created attachment 452712 [details]
I confirm that this patch works for me.
gvfs-1.6.4-3.fc14 has been submitted as an update for Fedora 14.
gvfs-1.6.4-3.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update gvfs'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/gvfs-1.6.4-3.fc14
gvfs-1.6.4-3.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.