[Hardy Heron] can't import photos from Canon A540

Please provide the information described here: https://wiki.ubuntu.com/DebuggingRemovableDevices.

The same problem here with Canon A520.

Info from wiki instructions is in the attachment.

PS: Couldn't start "gnome-volume-manager" (step 3) there was only "gnome-volume-manager-gthumb" if I used autocomplete - TAB.
The correct step 3 was:
/usr/lib/gnome-volume-manager/gnome-volume-manager -n 2>&1 | tee gvm.log

@Pascal De Vuyst
Thanks for the info.

The same problem here with Canon A520 on clean install of Hardy Beta with all updates.

Info from wiki instructions is in the attachment. If there is anything else just ask.

PS: Couldn't start "gnome-volume-manager" (step 3) there was only "gnome-volume-manager-gthumb" if I used autocomplete - TAB.
The correct step 3 was:
/usr/lib/gnome-volume-manager/gnome-volume-manager -n 2>&1 | tee gvm.log

Same problem with Fujifilm S5700. Also will not autodetect. Fresh install of Hardy Beta.

On 29. of march with all updates my camera Canon A520 works if I manually click on Import icon from F-spot or if I open it with Nautilus.

Still no automatic importing of pictures when I plug in the camera thou.

Thanks for the patch whatever you (or someone else) did ;)

I have a similar problem with a Nikon D-100 under the current Hardy release of KUbuntu using either Digikam or the command line program gphoto2.

It appears that the correct permissions are not being set on the USB device, the remain in the group root rather than plugdev.

lsusb says:

Bus 008 Device 001: ID 1d6b:0002
Bus 007 Device 001: ID 1d6b:0002
Bus 001 Device 001: ID 1d6b:0001
Bus 006 Device 005: ID 04b0:0402 Nikon Corp. DSC D100 (ptp)
Bus 006 Device 001: ID 1d6b:0001
Bus 003 Device 001: ID 1d6b:0001
Bus 005 Device 001: ID 1d6b:0001
Bus 004 Device 001: ID 1d6b:0001
Bus 002 Device 003: ID 046d:c03d Logitech, Inc.
Bus 002 Device 001: ID 1d6b:0001

Permissions on the device are:

# ls -l /dev/bus/usb/006/005
crw-rw-r-- 1 root root 189, 644 2008-04-13 13:50 /dev/bus/usb/006/005

If I manual set the group to plugdev then everything is happy again - until next time I plug it in.. :-(

Forgot to say - if I don't set the permissions the error I get from gphoto2 is:

*** Error ***
An error occurred in the io-library ('Could not claim the USB device'): Could not claim interface 0 (Operation not permitted). Make sure no other program or kernel module (such as sdc2xx, stv680, spca50x) is using the device and you have read/write access to the device.
*** Error (-53: 'Could not claim the USB device') ***

I can't use the referred to debugging page as I use KUbuntu with KDE and not Gnome.

I also can't import photos from my card reader after the hardy heron update.

I thought it was a permission issue so I did it again as root, and it still didn't work.

I got interesting debugging info from gphoto2:

0.604863 gp_file_open(0): Needs to be initialized with fd=-1 to work

When I started gnome-volume-manager -n it backgrounded itself and didn't log any output. Other logfiles are attached. The my-logfile.txt is from gphoto2.

Here is other debugging info asked for on https://wiki.ubuntu.com/DebuggingRemovableDevices

root@t43-brlewis:/tmp# id
uid=0(root) gid=0(root) groups=0(root),16048(dba)
root@t43-brlewis:/tmp# id hal
id: hal: No such user
root@t43-brlewis:/tmp# id haldaemon
uid=120(haldaemon) gid=120(haldaemon) groups=120(haldaemon),24(cdrom),25(floppy),46(plugdev),124(powerdev)
root@t43-brlewis:/tmp# uname -a
Linux t43-brlewis 2.6.24-16-386 #1 Thu Apr 10 12:50:06 UTC 2008 i686 GNU/Linux

confirming, the problem is that the usb devices created by gnome-volume-manager has user:group root:root instead of root:plugdev.

The temporary solution is to issue:

<code>sudo chown -R :plugdev /dev/bus/usb</code>

after plugging the camera's cable.

Waiting for the bug fixing, too. I consider it's a grave bug.

confirmed with canon eos 350d and canon g5

solution presented by donpaolo works:

this is on Ubuntu 8.04

Jepong - what package did you patch to fix this ?

Can I get a confirmation that this wasn't a Gnome specific fix that leaves us KDE users still with a broken system ?

cheers,
Chris

Problem still occurs with all updates applied as of Thu Jun 5 06:28:06 UTC 2008.

Well, same problem with a Canon PowerShot A80.

For "permanent workaround":

First check your camera ID with lsusb:
[...]
Bus 001 Device 005: ID 04a9:309a Canon, Inc. PowerShot A80
[...]

After that, edit the file /etc/udev/rules.d/40-permissions.rules and search for
LABEL="usb_serial_start"

You should add this line (and change you idVendor and idProduct!)
ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="309a", \
                                        MODE="0660", GROUP="plugdev"

(I've found the solution here: http://ubuntuforums.org/showthread.php?t=784864)

And that's all !

This bug just bit me too.

Will there be a Hardy fix?

This regression is 5 months old now, is the answer to say "don't use Ubuntu for cameras" ?

I recently upgraded to Intrepid, but I find that this bug hasn't been fixed in Intrepid either.

OK, bit the bullet and upgraded to the 9.04 version of KUbuntu yesterday and it appears that this bug has finally been fixed.

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in udev.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Was fixed a long time ago..