Photo Import from Canon IXUS 30/Powershot SD200 failed

[antistress]

I tried to import photos from my camera with Gutsy (tribe 5, RC, beta and final). It´s a Canon Digital IXUS 30. The import dialog appeared with the following bug report :

"Une erreur est intervenue dans la bibliothèque d'entrée-sortie ('Mauvais paramètres'): Impossible de trouver le périphérique USB (fabricant 0x4a9, produit 0x30c0). Assurez-vous qu'il est bien connecté à l'ordinateur."

or

"Appareil pas prêt, les requêtes d'identification de l'appareil ont échoué : Erreur du système lors de la communication avec l'appareil-photo"

Before Gutsy i was running ubuntu 7.04 and i could easily import photos from my camera.
I have formated my system disk to install ubuntu 7.10 tribe 5 and it doesn't work anymore since then.
I tried to import my photo from Ubuntu gutsy liveCD but i also had an error : "Camera not ready, multiple 'Identify camera' requests failed: OS error in camera communication" then something like "loading drivers from..."
I tried to import my photo from Ubuntu Depper liveCD and all was ok

it seems to be a gutsy regression.

Another guy has the same problem with the same camera http://forum.ubuntu-fr.org/viewtopic.php?pid=1262007#p1262007
Another guy has apparently the same problem with another camera : Panasonic FX30 http://forum.ubuntu-fr.org/viewtopic.php?pid=1274323#p1274323

[antistress (antistress)]

"Une erreur est intervenue dans la bibliothèque d'entrée-sortie ('Mauvais paramètres'): Impossible de trouver le périphérique USB (fabricant 0x4a9, produit 0x30c0). Assurez-vous qu'il est bien connecté à l'ordinateur." means something like : "an error occured in I/O system (wrong parameters) : can't find the usb device (Manufacturer 0x4a9, model 0x30c0). See if the device is well plugged to the PC"

and "Appareil pas prêt, les requêtes d'identification de l'appareil ont échoué : Erreur du système lors de la communication avec l'appareil-photo" means something like : "device not ready, identitification requests failed : system error when trying to communicate with the camera device"

[wwjd (wwjd)]

I can confirm this bug and a few other Gutsy users as well...

http://ubuntuforums.org/showthread.php?p=3654164
http://forum.ubuntuusers.de/topic/126497/#1026785

(Note that Canon IXUS 30 and Canon Powershot SD200 are the same cameras)

[antistress (antistress)]

Since that Canon IXUS 30 and Canon Powershot SD200 are the same cameras, i have updated the title of this report.

Can we hope this bug to be solve in Gutsy or shall we go back to Feisty, waiting for next ubuntu version ?

[antistress (antistress)]

libgphoto2 knows this camera since its 2.1.6 version (June 23rd, 2005) : http://www.gphoto.org/news/
For libgphoto 2.2.4, this camera is marked as :
Canon Digital IXUS 30 (normal mode) (EXPERIMENTAL)
Canon Digital IXUS 30 (PTP mode)

what's wrong ?

[antistress (antistress)]

instead og "For libgphoto 2.2.4, this camera is marked as" i wanted to write "For libgphoto2 2.4.0, this camera is marked as"
(libgphoto2 2.4.0 is the latest version)

[antistress (antistress)]

see that thread on gPhoto mailing list : http://sourceforge.net/mailarchive/forum.php?thread_name=7b26f72b0711040655l7450ec9bge6771178152cd0d7%40mail.gmail.com&forum_name=gphoto-user

[Jonas Christian (jonasvp)]

I had a similar problem with a Canon IXUS 500/Powershot S500, it would hang on picture import and I could not get capture to work. My solution was to remove it from the list of cameras that the canon driver would feel responsible for. The PTP2-driver of libgphoto2 would then take over and work perfectly.

I'm attaching the patch that worked for me. Maybe an IXUS 30 would only need a similar patch, removing the lines pertaining to that model.

Step by step:
- install build-essential and libltdl3-dev
- get the source: apt-get source libgphoto2-port0
- patch canon.c
- ./configure --disable-nls; make; make install

I got errors while compiling, "--disable-nls" fixed that. The new library is installed under /usr/local/lib, I used
  export LD_LIBRARY_PATH=/usr/local/lib:/usr/lib
in order to use it. Good luck.

[ignatzsol (flyingrobot)]

I have the same problem with my SD200. It used to work in Feisty, though I did not use it regularly. I was surprised to find that it is not recognized in Gutsy. I am looking forward to any usable fix.

[Frainbart (iwilllai)]

I have the same problem as well with my SD200. I had no issues importing photos from this camera in Feisty. Now the Gnome Import Photos application identifies it as a Canon IXUS 30 and gives the following error:
"Camera not ready, multiple 'Identify camera' requests failed: OS error in camera communication"
When I try to manually select the camera (normal and PTP mode) via the catalog, it hangs and freezes the camera. The camera has to be reset by removing the battery.

[antistress (antistress)]

that bug is still present in hardy alpha

this is a regression since gutsy : does it mean that our cameras will never work anymore with Ubuntu ?

[antistress (antistress)]

sorry i wanted to write "in hardy alpha 4" above

[antistress (antistress)]

still doesn't work in hardy alpha 6 liveCD
i got "Erreur lors de la connexion de l'appareil photo. Erreur "données corrompues" reçue lors de la connexion de l'appareil photo.

Don't you consider regressions to be prioritary ?

[antistress (antistress)]

i also got in another window :
Impossible de monter Canon, Inc. Digital IXUS 30 (PTP mode) / PowerShot SD200 (PTP mode)
Error initializing camera: -114: Erreur du système lors de la communication avec l'appareil-photo

[Martin Pitt (pitti)]

On a current Hardy installation or a live system, can you please create a hal debug log as described on https://wiki.ubuntu.com/DebuggingHal#head-63a8aeb350e85f87bb1989ff631c0b8e60de05ee ?

[antistress (antistress)]

here are the files

I've done these actions :
i've plugged my camera and started it and i've seen nothing
then i've unplugged it and plugged it again and i've seen nothing
then i've manually started F-Spot and tried to import pictures from the camera (which was correctly named in F-Spot menu)

[Martin Pitt (pitti)]

According to antistress' log files, the kernel and hal did recognize the camera and enabled user access to it, but then f-spot crashed. Antistress, did apport (the automatic crash handling system) catch this? did you report it to Launchpad?

[antistress (antistress)]

actually i don't have crashes

the name of my camera is shown in F-Spot but i got an error message : "Erreur lors de la connexion de l'appareil photo. Erreur "unknown error" reçue lors de la connexion de l'appareil photo"

[Peter de Kraker (peterdekraker)]

I am having a similar problem in Hardy Beta 1, x86_64
Camera gets recognized when plugged in (Bus 003 Device 003: ID 04a9:30bb Canon, Inc. PowerShot A95), but no software starts.

When I start f-spot, it does recognize the camera, but when I try to import from it by clicking it's name, I get:
"Error connecting to camera. Received error: "Could not claim the USB device" while connecting to the camera "

I also cannot use it in Gutsy, but Hardy is more important I guess.

[dancer58 (dancer581)]

Same problem different camera

Ubuntu 8.04 beta

uname -a
Linux asus 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux

gthumb version 3:2.10.6-Obuntu3

I get the following when I try to import pictures with gthumb

=====================================================================================

RUNN FROM MENU
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.

=======================================================================================
RUN FROM TERMINAL
harold@asus:~$ sudo gthumb
[sudo] password for harold:

** (gthumb:8618): CRITICAL **: Error opening file: No such file or directory

** (gthumb:8618): CRITICAL **: Error opening file: No such file or directory

** (gthumb:8618): CRITICAL **: Error opening file: No such file or directory

** (gthumb:8618): CRITICAL **: Error opening file: No such file or directory

** (gthumb:8618): CRITICAL **: Error opening file: No such file or directory

** (gthumb:8618): CRITICAL **: Error opening file: No such file or directory

** (gthumb:8618): CRITICAL **: Error opening file: No such file or directory

** (gthumb:8618): CRITICAL **: Error opening file: No such file or directory

THIS IS AN ERROR BOX:
The folder contents could not be displayed
Operation not supported

Running as root the camera pictures show but with the above errors

=======================================================================================

gphoto2 -debug
harold@asus:~$ gphoto2 --debug
0.000200 main(2): ALWAYS INCLUDE THE FOLLOWING LINES WHEN SENDING DEBUG MESSAGES TO THE MAILING LIST:
0.000241 main(2): gphoto2 2.4.0
0.000252 main(2): gphoto2 has been compiled with the following options:
0.000269 main(2): + gcc (C compiler used)
0.000275 main(2): + popt (mandatory, for handling command-line parameters)
0.000282 main(2): + exif (for displaying EXIF information)
0.000297 main(2): + cdk (for accessing configuration options)
0.000304 main(2): + no aa (for displaying live previews)
0.000326 main(2): + jpeg (for displaying live previews in JPEG format)
0.000331 main(2): + readline (for easy navigation in the shell)
0.000345 main(2): libgphoto2 2.4.0
0.000361 main(2): libgphoto2 has been compiled with the following options:
0.000369 main(2): + gcc (C compiler used)
0.000379 main(2): + ltdl (for portable loading of camlibs)
0.000384 main(2): + EXIF (for special handling of EXIF files)
0.000395 main(2): libgphoto2_port 0.8.0
0.000407 main(2): libgphoto2_port has been compiled with the following options:
0.000413 main(2): + gcc (C compiler used)
0.000422 main(2): + ltdl (for portable loading of camlibs)
0.000427 main(2): + USB (libusb, for USB cameras)
0.000438 main(2): + serial (for serial cameras)
0.000448 main(2): + no resmgr (serial port access and locking)
0.000453 main(2): + no baudboy (serial port locking)
0.000463 main(2): + no ttylock (serial port locking)
0.000468 main(2): + no lockdev (serial port locking)
0.000479 main(2): CAMLIBS env var not set,...

[Martin G Miller (mgmiller)]

I have a Canon SD 550 which works perfectly in Gutsy.
Using the Live CD Hardy Beta daily builds from 03-25-2008 and 04-01-2008.
When I plug in the camera with Hardy beta, no software is triggered. If I run F-spot or have previously installed and run gthumb, it does show the camera in the drop down as an import source. If I select the camera, the system instantly freezes with no response to keyboard or mouse. Only recourse is forced reboot from restart switch on the tower.
As I recall, it worked properly up through Hardy Beta 03-21-2008 Live CD. The bug started with the Beta release on 03-25-2008.

I have tried this in 3 different computers and they all behave the same way.

[brian0r (briansuh)]

I have the same problem with a Canon Powershot SD500. It will not detect. I am using the most recent Hardy Beta. Unfortunately, I have not tested whether it worked or not before the upgrade. In Gutsy, it worked perfectly.

[antistress (antistress)]

but nobody seems to care about that regression in Ubuntu. It looks like we are alone, stuck with this bug for ever

[Martin Pitt (pitti)]

We disabled the gvfs gphotofs backend again for the final release, which interfered with the intended handling of photo cameras. Does this still happen to you in the final release?

[antistress (antistress)]

yes
that bug exists since ubuntu 7.10 ans ubuntu 7.10 didn't know GVFS either
therefore if nothing has changed in ubuntu about that, it seems logical that the bug still exists.
Note that the camera is properly detected and f-spot tried to import photo "from canon ixus 30 (normal mode" but didn't managed to do it.
that's is exactly the same behaviour as before

[Martin G Miller (mgmiller)]

I am now running Hardy final. My camera is a Canon SD 550. Gthumb identifies it after a short delay as a Canon Digital IXUS 750 (PTP mode).
Gthumb now functions normally to import and delete pictures from the camera.
F-spot also identifies the camera as an IXUS 750 and functions normally to import pictures. I did not see a delete after importing feature, so I could not test that.
F-spot did not crash on exit.
For my system, this bug appears fixed.

[antistress (antistress)]

since my system is an upgrade from an alpha version of hardy, i've tried with hardy final liveCD and i've got the same error as before
bug is not fixed for me

[antistress (antistress)]

how can i enable the PTP mode ?

[antistress (antistress)]

that bug IS FIXED for me thanks to yesterday update in Hardy :

libgphoto2-2
* cherry-pick patch form upstream to use PTP mode for some Canon cameras:
- powershot SD200
- digital IXUS 30
- IXY digital 40

many thanks