Can't Import Photos from Canon EOS Digital Rebel XTi

Bug #63473 reported by Chris Gray
14
Affects Status Importance Assigned to Milestone
libgphoto2 (Ubuntu)
In Progress
Medium
Martin Pitt

Bug Description

I just purchased the new Canon EOS Digital Rebel XTi. The default configuration of Ubuntu Dapper (and Ubuntu Edgy on my test box) see that the camera is attached and that there are pictures on the camera. However, the system reports this error when 'Import' is started:

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.

I have tried rebooting and alternately using Picasa for Linux, F-Stop, and other packages to no avail.

Revision history for this message
Daniel Hahler (blueyed) wrote :

I'm getting the same error (which appears to come from libgphoto2-2).

I have a Fujifilm FinePix F30, which gets handled as "PTP".

If the application using libgphoto (e.g. digikam) is being run as root, it works and it worked previously in Ubuntu Dapper.

Changed in gphoto2:
status: Unconfirmed → Confirmed
Revision history for this message
Marcus Meissner (meissner) wrote :

What are the USB ids of the Xti and of the F30?

Ciao, Marcus

Revision history for this message
Daniel Hahler (blueyed) wrote :

$ lsusb
Bus 002 Device 003: ID 04cb:019b Fuji Photo Film Co., Ltd

Why can I ran it as root, but not as normal user?
The following works:
$ kdesu konqueror media:/camera/

Revision history for this message
Chris Gray (chrislg1970) wrote : Re: [Bug 63473] Re: Can't Import Photos from Canon EOS Digital Rebel XTi

I'm not a 'noob', but, how do I find the USB id of the XTi?

On 10/26/06, Marcus Meissner <email address hidden> wrote:
> What are the USB ids of the Xti and of the F30?
>
> Ciao, Marcus
>
> --
> Can't Import Photos from Canon EOS Digital Rebel XTi
> https://launchpad.net/bugs/63473
>

Revision history for this message
Daniel Hahler (blueyed) wrote : How to find USB device id

I had to search myself, but thought that it should be "clear" from my comment.

1. Connect the camera
2. Type "lsusb" on a terminal

That's what I've pasted above for the Fuji

Revision history for this message
Martin Pitt (pitti) wrote :

Will fix in feisty.

Changed in libgphoto2:
assignee: nobody → pitti
importance: Undecided → Medium
status: Confirmed → In Progress
Revision history for this message
Daniel Hahler (blueyed) wrote :

It has been working in Dapper.
What is this caused by?

Revision history for this message
Tormod Volden (tormodvolden) wrote :

See all but the original comment in bug #6602 for more of the same, and some debug information.

Revision history for this message
Jon Leighton (jonleighton) wrote :

I have the same problem with my Canon EOS 400D, as reported in bug #6602. The workaround there works for me. From lsusb:

Bus 004 Device 016: ID 04a9:3110 Canon, Inc.

Revision history for this message
lugburz (thepac78) wrote :

Hi

I had the same kind of problem with a Nikon Coolpix L1 :
used to work with dapper, don't work anymore with edgy

As requested in bug #6602, I will continue here, although I find the solution in that bug report.
I added a line matching my camera's id in /etc/udev/rules/45-libgphoto2 :

SYSFS{idVendor}=="04b0", SYSFS{idProduct}=="0208", MODE="0660", GROUP="plugdev"

I haven't tried the cleaner solution with check_ptp_camera, but I've no doubt it would have worked smoothly, too.

But I read that this bug will be fixed in feisty (i.e. in 6 months from now) : you must be kidding me !
Don't you think that this kind of bug is somehow critical for a distribution aimed at average users, for Mr and Ms "everybody" ?
If you really want (K)Ubuntu to be a popular OS, a challenger for windows, you should really take care of avoiding such bugs in stable releases, or at least fix them as quick as possible.

Revision history for this message
Boudewijn (boud) wrote :

For my Fujifilm s6500fd (f6000fd in USA) I had to add

SYSFS{idVendor}=="04cb", SYSFS{idProduct}=="01bf", MODE="0660", GROUP="plugdev"

in Kubuntu Edgy.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.