| Summary: | Digikam does not work with Olympus C-170 CAMEDIA camera | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Julio A. Cartaya <jacartaya> |
| Component: | Import-Gphoto2 | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | aegoss, caulier.gilles |
| Priority: | NOR | ||
| Version First Reported In: | 0.9.2 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 5.1.0 | |
| Sentry Crash Report: | |||
| Attachments: |
jacartaya.vcf
Output for the 486 kernel - Debian Etch Output for the 686 kernel - Debian Etch jacartaya.vcf |
||
|
Description
Julio A. Cartaya
2007-12-09 12:36:21 UTC
Julio, There is no camera drivers in digiKam. We use libgphoto2 for that. Witch version you use in your computer ? Gilles Caulier Espa Hi Gilles,
I encountered the very same problem I described at two different
computers (even 2 different distros):
* The one at my office (where I am now) is running Open SuSE 10.3 on
an x86-64 CPU, and uses libgphoto2-2.4.0-25.2.
* The other computer is my home machine, runs Mandriva 2008 Power
Pack, on an x86-32 CPU, and I will have to wait until I get back
home to tell you exactly which version of libgphoto2 is using.
When I attempt to access the pictures through the USB storage device I
get an error message from KDE that says it can not write to the port.
Wouldn't that be indication that the failure resides perhaps at the USB
driver?
Thanks
Julio
------------------------------------------------------------------------
Gilles Caulier escribió:
[bugs.kde.org quoted mail]
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Gilles,<br>
<br>
I encountered the very same problem I described at two different
computers (even 2 different distros):<br>
<ul>
<li>The one at my office (where I am now) is running Open SuSE 10.3
on an x86-64 CPU, and uses libgphoto2-2.4.0-25.2. <br>
</li>
<li>The other computer is my home machine, runs Mandriva 2008 Power
Pack, on an x86-32 CPU, and I will have to wait until I get back home
to tell you exactly which version of libgphoto2 is using.</li>
</ul>
When I attempt to access the pictures through the USB storage device I
get an error message from KDE that says it can not write to the port.
Wouldn't that be indication that the failure resides perhaps at the USB
driver?<br>
<br>
Thanks<br>
<br>
Julio<br>
<hr size="2" width="100%">Gilles Caulier escribió:
<blockquote cite="mid:20071209122740.4184.qmail@ktown.kde.org"
type="cite">
<pre wrap="">------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
<a class="moz-txt-link-freetext" href="http://bugs.kde.org/show_bug.cgi?id=153716">http://bugs.kde.org/show_bug.cgi?id=153716</a>
caulier.gilles gmail com changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|general |Camera GUI
------- Additional Comments From caulier.gilles gmail com 2007-12-09 13:27 -------
Julio,
There is no camera drivers in digiKam. We use libgphoto2 for that. Witch version you use in your computer ?
Gilles Caulier
</pre>
</blockquote>
<br>
</body>
</html>
Created an attachment (id=22445)
jacartaya.vcf
Could you try the following commands on the command-line and report their output: a) connect camera, what is the output of dmesg (only the camera related part) b) gphoto2 -v c) gphoto2 --list ports d) gphoto2 --auto-detect -L e) gphoto2 --abilities f) gphoto2 --list-folders ((Please don't quote the full message in your reply, as this makes reading the thread in the web-interface very difficult, see http://bugs.kde.org/show_bug.cgi?id=153716 )) Thanks, Arnd Espa I am having the "Could not read file Error writing to the port" problem as well, but on Debian Etch KDE, both 486 and 686 kernels. I plug in the camera (Olympus SP-510UZ), and Konqueror attempts to initialise it for while, before popping up the message. I will attach the output for both kernels. On the same machine I have Kubuntu 6.06, on which I can upload the files from the camera with no trouble. I am not using Digikam, just uploading via Konqueror. Espa Created attachment 22812 [details]
Output for the 486 kernel - Debian Etch
Espa Created attachment 22813 [details]
Output for the 686 kernel - Debian Etch
Espa owner@bugs.kde.org escribió: [bugs.kde.org quoted mail] Created an attachment (id=22820) jacartaya.vcf Andy, does: env LANG=C gphoto2 --debug --auto-detect -L work as root user (it might be a rights issue). In any case: it is not a digikam problem and therefore is better asked on the corresponding gphoto2 mailing list. Arnd, env LANG=C gphoto2 --debug --auto-detect -L does work, the following looks like the relevant part: 0.469963 gphoto2-port-usb(1): Looking for USB device (vendor 0x7b4, product 0x109)... found. 0.469979 gphoto2-port-usb(1): USB device (vendor 0x7b4, product 0x109) is a mass storage device, and might not function with gphoto2. Reference: http://www.linux-usb.org/USB-guide/x498.html 0.469994 gphoto2-port-usb(1): Detected defaults: config 1, interface 0, altsetting 0, inep 82, outep 01, intep ffffffff, class 08, subclass 06 0.470024 gphoto2-abilities-list.c(2): Found 'Olympus C-370Z' (0x7b4,0x109) 0.470043 gphoto2-port(2): Freeing port... 0.470057 gphoto2-port(2): Closing port... 0.470916 foreach(2): Executing action 'List Files' for folder '/'. 0.471397 gphoto2-camera(2): Listing files in '/'... 0.471436 gphoto2-camera(2): Initializing camera... 0.471458 gphoto2-port-usb(1): Looking for USB device (vendor 0x7b4, product 0x109)... found. 0.471482 gphoto2-port-usb(1): USB device (vendor 0x7b4, product 0x109) is a mass storage device, and might not function with gphoto2. Reference: http://www.linux-usb.org/USB-guide/x498.html 0.471497 gphoto2-port-usb(1): Detected defaults: config 1, interface 0, altsetting 0, inep 82, outep 01, intep ffffffff, class 08, subclass 06 0.471514 gphoto2-camera(2): Loading '/usr/lib/libgphoto2/2.2.1/sierra'... 0.471769 gphoto2-port(2): Opening USB port... 0.471867 gphoto2-port(0): Could not query kernel driver of device. 0.471941 gphoto2-port(2): Setting settings... 10.472577 gphoto2-port(0): Could not set config 0/1 (Connection timed out) 10.472814 sierra/sierra.c(2): Operation failed (-37)! 10.472930 gphoto2-port(2): Closing port... 10.473038 gphoto2-port(0): Could not release interface 0 (Invalid argument). 10.473206 context(0): An error occurred in the io-library ('Error updating the port settings'): Could not release interface 0 (Invalid argument). *** Error *** An error occurred in the io-library ('Error updating the port settings'): Could not release interface 0 (Invalid argument). *** Error (-37: 'Error updating the port settings') *** 10.474688 gp-camera(2): Freeing camera... 10.474867 gphoto2-port(2): Freeing port... 10.474960 gphoto2-port(2): Closing port... 10.475064 gphoto2-port(0): Could not release interface 0 (Invalid argument). It seems to have mis-identified the camera. As you suggest, gphoto2 might be a better place for this bug. there is a usb conflict/mix between the mass storage and the libgphoto2 driver. Can you chose to use the Mass Storage driver? Espa "there is a usb conflict/mix between the mass storage and the libgphoto2 driver. Can you chose to use the Mass Storage driver? " All I am doing is plugging the camera in and chosing PC on its menu. Konqueror comes up, followed after a minute or so by the error message. How do I elect to use the Mass Storage driver? I have opened a Debian bug, 459017, which has been assigned to libgphoto2-2, to avoid (I hope) confusion, as I have no problem with Digikam. But I will continue to monitor this bug. I am observing this problem with a similar camera (fe-190) and have posted the following message to debian-kde@lists.debian.org. ...... after a recent upgrade in testing, digikam does not recognize my Olympus fe-190 camera correctly anymore. Instead, it reports the camera as a Olympus C-310Z and fails to connect. Using PTP USB mode it is possible to connect, but not with the functionality I had before (new pictures are recognized for instance). Does anyone have any suggestions for me, should I post a bug-report to digikam? Thanks, C Here is my lsusb and /proc/partitions, I'm using the 2.6.24-1-686 kernel. major minor #blocks name 3 0 40209120 hda 3 1 6835626 hda1 3 2 1 hda2 3 5 32868958 hda5 3 6 497983 hda6 3 64 117220824 hdb 3 65 117218241 hdb1 Bus 001 Device 009: ID 07b4:0109 Olympus Optical Co., Ltd C-370Z/D-535Z/X-450 Bus 001 Device 003: ID 04a9:220d Canon, Inc. CanoScan N670U/N676U/LiDE 20 Espa What's news in this report ? using digiKam 0.9.4 and a recent version of libgphoto2 fix the problem ? Gilles Caulier What's news here ? using digiKam 0.10.0 fix the problem ? Gilles Caulier No answer since more then a year. I close this bug report. Feel free to reopen if necessary. New digiKam 4.11.0 is available. https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles Caulier With digiKam 5.0.0, this problem is not reproducible. I close this file now. Don't hesitate to re-open if necessary. Gilles Caulier |