[Linux] Digikam picture import error

Sun, 18 Mar 2007 21:13:01 -0600

------=_Part_88585_12468070.1174273981326
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I assume that, since digikam was able to d/l images from the camera in the
past, the problem is not with the settings in the udev file. I did try to
add a line to the rules file, but it did not help. However, I may have not
added the right content.

I know how to change permissions, but I can't identify the usb device on my
computer. Hence the question. Again, though, it worked fine before, so
unless the permissions or device name were changed by one of the new program
(which I kinda doubt), it should work as is.

Hence my guess that one of the GPS programs is set to monitor the usb
device, and is circumventing its use for the camera. Now I don't want to
delete gpsbabel and gpsman, because I use them to convert data files and
communicate with the gps. So that leaves figuring out which module is
messing with my usb port and how to fix it.

So,

1. which is the common name for the usb device (it is not /dev/usb
derivative).

2. how do I find out an offending source (is there something like fuser
/dev/usb_device_name)

???

I will read about udev, udev rules in google in the coming days. Right now,
I d/l to another computer and ftp it to my linux box. Not the most elegant
solution, but it does work. I may also try to apt-get remove gpsd, etc. to
see if that solves my problem but truly, I use the gps much more than the
camera, so would rather not mess with gps programs right now...

Thanks,

Z.

On 3/18/07, Ray Racine <rracine@adelphia.net> wrote:
>
> On Sun, 2007-03-18 at 08:09 -0600, Steven Benmosh wrote:
> > In the past, I have used digikam to download images from my Canon
> > PowerShot A610 to my ubuntu box without problems.
> >
> > Recently, I have installed a number of GPS related programs (GPSD,
> > GPSMAN, GPSBABEL), and also other programs as well. Now I get the
> > following error message, and I can not import the images:
> >
> > "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."
> >
> > lsusb shows Bus 003 Device 011: ID 04a9:30fd Canon, Inc.
> >
> > dmesg|grep usb shows: [18298574.868000] usb 3-7: new high speed USB
> > device using ehci_hcd and address 11
> > [18298575.028000] usb 3-7: configuration #1 chosen from 1 choice
> >
>
> Have you tried putting in a udev rule?
> Something like in /etc/udev/rules.d/...
>
> BUS=="usb", SYSFS{idProduct}=="020b", SYSFS{idVendor}=="067c",
> MODE="0660", GROUP="cameradev", SYMLINK+="my_digikam"
>
> Get the idXXXs from the lsusb if thats what you are familiar with.
>
> The SYMLINK is pretty nice as it will create a symlink
> in /dev/sony_reader its true location in the /dev tree.
>
> That will solve the "how do I find it problem."
>
> Lots of stuff in google on udev, udev rules, and all that.
>
> If necessary use chmod or chgrp manually on the in the /dev tree or log
> in as root to determine if its permission or something has claimed the
> interface.
>
> Its not uncommon for a device to support several interfaces / endpoints
> but we shouldn't have to go there and a lot would depend on the software
> itself that your using.
>
> > I tried updating the configuration file as recommended for other
> > cameras generating the same bugs (sorry, don't remember the
> > configuration file name). Maybe I did not do it correctly, but either
> > way, it did not help.
> >
> > So here is the questions:
> >
> > 1. How do I find out which program and/or kernel module is using the
> > device, if any?
> > 2. How do I find whether I have read/write access to the device (whice
> > device, btw, I do not seem to have any /dev/usbxx listed (I ran
> > ls /dev|grep usb, grep us, grep sb), my gps is serial)
> > 3. How do I enable access to the device once I find out the culprit?
> >
> > Thanks,
> >
> > Z.
> >
> >
>
> _______________________________________________
> Linux mailing list
> Linux@flux.org
> http://www.flux.org/mailman/listinfo/linux
>

------=_Part_88585_12468070.1174273981326
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I assume that, since digikam was able to d/l images from the camera in the past, the problem is not with the settings in the udev file. I did try to add a line to the rules file, but it did not help. However, I may have not added the right content.
 I know how to change permissions, but I can&#39;t identify the usb device on my computer. Hence the question. Again, though, it worked fine before, so unless the permissions or device name were changed by one of the new program (which I kinda doubt), it should work as is.
 Hence my guess that one of the GPS programs is set to monitor the usb device, and is circumventing its use for the camera. Now I don&#39;t want to delete gpsbabel and gpsman, because I use them to convert data files and communicate with the gps. So that leaves figuring out which module is messing with my usb port and how to fix it.
 So, 1. which is the common name for the usb device (it is not /dev/usb derivative). 2. how do I find out an offending source (is there something like fuser /dev/usb_device_name) ??? I will read about udev, udev rules in google in the coming days. Right now, I d/l to another computer and ftp it to my linux box. Not the most elegant solution, but it does work. I may also try to apt-get remove gpsd, etc. to see if that solves my problem but truly, I use the gps much more than the camera, so would rather not mess with gps programs right now...
 Thanks, Z. <div>On 3/18/07, Ray Racine &lt;<a href="mailto:rracine@adelphia.net">rracine@adelphia.net</a>&gt; wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Sun, 2007-03-18 at 08:09 -0600, Steven Benmosh wrote: &gt; In the past, I have used digikam to download images from my Canon &gt; PowerShot A610 to my ubuntu box without problems. &gt; &gt; Recently, I have installed a number of GPS related programs (GPSD,
 &gt; GPSMAN, GPSBABEL), and also other programs as well. Now I get the &gt; following error message, and I can not import the images: &gt; &gt; &quot;An error occurred in the io-library (&#39;Could not claim the USB
 &gt; device&#39;): Could not claim interface 0 (Operation not permitted). Make &gt; sure no other program or kernel module (such as sdc2xx, stv680, &gt; spca50x) is using the device and you have read/write access to the
 &gt; device.&quot; &gt; &gt; lsusb shows Bus 003 Device 011: ID 04a9:30fd Canon, Inc. &gt; &gt; dmesg|grep usb shows: [18298574.868000] usb 3-7: new high speed USB &gt; device using ehci_hcd and address 11
 &gt; [18298575.028000] usb 3-7: configuration #1 chosen from 1 choice &gt; Have you tried putting in a udev rule? Something like in /etc/udev/rules.d/... BUS==&quot;usb&quot;, SYSFS{idProduct}==&quot;020b&quot;, SYSFS{idVendor}==&quot;067c&quot;,
 MODE=&quot;0660&quot;, GROUP=&quot;cameradev&quot;, SYMLINK+=&quot;my_digikam&quot; Get the idXXXs from the lsusb if thats what you are familiar with. The SYMLINK is pretty nice as it will create a symlink
 in /dev/sony_reader its true location in the /dev tree. That will solve the &quot;how do I find it problem.&quot; Lots of stuff in google on udev, udev rules, and all that. If necessary use chmod or chgrp manually on the in the /dev tree or log
 in as root to determine if its permission or something has claimed the interface. Its not uncommon for a device to support several interfaces / endpoints but we shouldn&#39;t have to go there and a lot would depend on the software
 itself that your using. &gt; I tried updating the configuration file as recommended for other &gt; cameras generating the same bugs (sorry, don&#39;t remember the &gt; configuration file name). Maybe I did not do it correctly, but either
 &gt; way, it did not help. &gt; &gt; So here is the questions: &gt; &gt; 1. How do I find out which program and/or kernel module is using the &gt; device, if any? &gt; 2. How do I find whether I have read/write access to the device (whice
 &gt; device, btw, I do not seem to have any /dev/usbxx listed (I ran &gt; ls /dev|grep usb, grep us, grep sb), my gps is serial) &gt; 3. How do I enable access to the device once I find out the culprit? &gt; 
&gt; Thanks, &gt; &gt; Z. &gt; &gt; _______________________________________________ Linux mailing list <a href="mailto:Linux@flux.org">Linux@flux.org</a> <a href="http://www.flux.org/mailman/listinfo/linux">
http://www.flux.org/mailman/listinfo/linux</a> </blockquote></div>

------=_Part_88585_12468070.1174273981326--