Unable to view any pictures on my Canon Powershot SD500

[Johnathon]

I am currently using Breezy. In, Hoary, I could just connect this camera to my
laptop through USB and It would work great with gthumb. However, now when I plug
in my camera, a pop-up opens up and I coose to import it with gthumb. However, I
get an error saying "Camera not ready, multiple 'Identify camera' requests
failed: OS error in camera communication". Also, the wrong camera is selected as
what it detected... it says it is a "Canon Digital IXUS 700 (normal mode)" which
is incorrect. By this time, my camera has seemed to have crashed and I cannot
get it to respond to me. I have to shut it down. Before I retry by camera, dmesg
says this:

[4372921.538000] usb 5-1: new high speed USB device using ehci_hcd and address 3
[4373305.661000] usb 5-1: USB disconnect, address 3

Now, I restart my camera, pop-up comes up again, I say import. This time the
error in the box is "Could not establish initial contact with camera". dmesg now
says:

[4373618.013000] atkbd.c: Unknown key released (translated set 2, code 0xaa on
isa0060/serio0).
[4373618.013000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.
[4373618.156000] atkbd.c: Unknown key pressed (translated set 2, code 0xaa on
isa0060/serio0).
[4373618.156000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.
[4373800.396000] atkbd.c: Unknown key released (translated set 2, code 0xaa on
isa0060/serio0).
[4373800.396000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.
[4373800.560000] atkbd.c: Unknown key pressed (translated set 2, code 0xaa on
isa0060/serio0).
[4373800.560000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.
[4373800.647000] atkbd.c: Unknown key released (translated set 2, code 0xaa on
isa0060/serio0).
[4373800.647000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.
[4373800.713000] atkbd.c: Unknown key pressed (translated set 2, code 0xaa on
isa0060/serio0).
[4373800.713000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.
[4373801.779000] atkbd.c: Unknown key released (translated set 2, code 0xaa on
isa0060/serio0).
[4373801.779000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.
[4373801.958000] atkbd.c: Unknown key pressed (translated set 2, code 0xaa on
isa0060/serio0).
[4373801.958000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.
[4373885.141000] atkbd.c: Unknown key released (translated set 2, code 0xaa on
isa0060/serio0).
[4373885.141000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.
[4373885.263000] atkbd.c: Unknown key pressed (translated set 2, code 0xaa on
isa0060/serio0).
[4373885.263000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.
[4373885.550000] atkbd.c: Unknown key released (translated set 2, code 0xaa on
isa0060/serio0).
[4373885.550000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.
[4373885.642000] atkbd.c: Unknown key pressed (translated set 2, code 0xaa on
isa0060/serio0).
[4373885.642000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.
[4373902.126000] atkbd.c: Unknown key released (translated set 2, code 0xaa on
isa0060/serio0).
[4373902.126000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.
[4373902.249000] atkbd.c: Unknown key pressed (translated set 2, code 0xaa on
isa0060/serio0).
[4373902.249000] atkbd.c: Use 'setkeycodes e02a <keycode>' to make it known.
[4373971.608000] usb 5-1: new high speed USB device using ehci_hcd and address 4
[4374003.440000] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd gthumb rqt 64 rq 4
len 80 ret -110
[4374008.440000] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd gthumb rqt 64 rq 4
len 80 ret -110
[4374018.442000] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd gthumb rqt 192 rq
12 len 1 ret -110

I have listed this as a problem with gthumb, because I've tried many other
programs in hopes that the camrea would work in them, but it does not. digikam,
gtkam, showFoto... none of these work. Also, I've tried specifically setting
gthumb to use the right camera, and then try to import the photos, but it still
doesn't work. I can provide any more output that is desired.

[z_diver (chuck-lagunadata)]

I have this problem as well and it continues to be an issue for me in Dapper flight 5. From what I've read, the IXUS-700 may be the European model equivalent of the SD-500(bought in the US) but for some reason photo import or picture viewing does not work. As stated above, the camera freezes in addition to gthumb or f-spot giving errors.

[Matt Zimmerman (mdz)]

Is this problem still present in current Dapper?

[Johnathon (outdooricon)]

I am unable to verify that this still doesn't work in Flight 6 as I'm not testing Dapper... z_diver, are you using Dapper Flight 6?

[z_diver (chuck-lagunadata)]

Hello John,
I have a clean Flight 5 install that I update daily... just now in fact
and I retried the procedure below which came back with the same error.

Steps taken to produce error:
I plugged the camera directly into a USB 2.0 port and I got the "A
camera has been detected" message asking if I want to import photos to
my album. If I click "Import" the next box gives me the "IXUS 700"
camera name, which might or might not be correct, and the error message:
Camera not ready, multiple 'Identify camera' requests failed: OS error
in camera communication.

I do have many machines around so if you would like I can try a fresh
Flight 6 install if you think it would make a difference.

On Sat, 2006-04-01 at 04:49 +0000, John wrote:
> I am unable to verify that this still doesn't work in Flight 6 as I'm not testing Dapper... z_diver, are you using Dapper Flight 6?

[Johnathon (outdooricon)]

z_diver,
If you could install Dapper Flight 6 on a machine and determine if it still doesn't work on there, that would be great. If you verify that the camera still doesn't work on your Flight 6 install, then I can upgrade the status of this bug and hopefully move things along. Thanks!

[z_diver (chuck-lagunadata)]

John,
I tried to import photos from the Canon SD500 to a Dapper Flight 6 live
CD as well as a fresh installation of Flight 6 both before and after
updating it but unfortunately I still get the same "Camera not ready..."
error.

[Johnathon (outdooricon)]

z_diver has verified that this is still an issue in Flight 6... changing status to Confirmed. Also, changing Severity to Major.

[Marcus Meissner (meissner)]

gphoto2 -L --debug output would help.

what you can also try is:
rm /usr/lib/libgphoto2/2.1.6/canon.*

then reattach the camera and try again

[z_diver (chuck-lagunadata)]

Marcus, good news, your workaround worked except the files to remove
were in /usr/lib/gphoto2/2.1.6 instead of /usr/lib/libgphoto2/2.1.6/.

Further below is the output from gphoto2 -L --debug BEFORE deleting
*canon* from /usr/lib/gphoto2/2.1.6. I verified this solution works on
two up to date installations of Dapper and one of Breezy.

In all three cases after deleting the *canon* files, I was able to
import pictures from my camera as a Canon IXUS 700 in (PTP mode).

chuckh@hicacos:~$ gphoto2 -L --debug
0.000061 main(2): ALWAYS INCLUDE THE FOLLOWING LINES WHEN SENDING DEBUG
MESSAGES TO THE MAILING LIST:
0.000560 main(2): gphoto2 2.1.6
0.000776 main(2): gphoto2 has been compiled with the following options:
0.000985 main(2): + gcc (C compiler used)
0.001191 main(2): + no popt (for handling command-line parameters)
0.001426 main(2): + exif (for displaying EXIF information)
0.001633 main(2): + cdk (for accessing configuration options)
0.001839 main(2): + no aa (for displaying live previews)
0.002045 main(2): + jpeg (for displaying live previews in JPEG format)
0.002252 main(2): + readline (for easy navigation in the shell)
0.002788 main(2): libgphoto2 2.1.6
0.003004 main(2): libgphoto2 has been compiled with the following
options:
0.003213 main(2): + gcc (C compiler used)
0.004012 main(2): + EXIF (for special handling of EXIF files)
0.004219 main(2): + no ltdl (working around buggy libltdl, eh? :-)
0.004436 main(2): + /proc/meminfo (adapts cache size to memory
available)
0.004650 main(2): libgphoto2_port 0.5.1
0.004865 main(2): libgphoto2_port has been compiled with the following
options:
0.005073 main(2): + gcc (C compiler used)
0.005280 main(2): + USB (for USB cameras)
0.005496 main(2): + serial (for serial cameras)
0.005702 main(2): + no resmgr (serial port access and locking)
0.005909 main(2): + no baudboy (serial port locking)
0.006115 main(2): + no ttylock (serial port locking)
0.006322 main(2): + no lockdev (serial port locking)
0.006539 main(2): + no ltdl (working around buggy libltdl, eh? :-)
0.006750 foreach(2): Executing action 'List Files' for folder '/'.
0.007501 gphoto2-camera(2): Listing files in '/'...
0.007827 gphoto2-camera(2): Initializing camera...
0.008085 gphoto2-port-usb(1): Looking for USB device (vendor 0x4a9,
product 0x30f2)... found.
0.008308 gphoto2-port-usb(1): Detected defaults: config 1, interface 0,
altsetting 0, inep 81, outep 02, intep 83, class 06, subclass 01
0.008542 gphoto2-camera(2): Loading
'/usr/lib/gphoto2/2.1.6/libgphoto2_canon.so'...
0.009251 gphoto2-port(2): Opening USB port...
0.021729 gphoto2-port(0): Could not query kernel driver of device.
0.078792 canon/library.c(2): canon camera_init()
0.079135 canon/library.c(2): GPhoto tells us that we should use a USB
link.
0.079472 canon/usb.c(2): Initializing the (USB) camera.

0.079757 canon/usb.c(2): canon_usb_camera_init()
0.080022 canon/usb.c(2): canon_usb_identify: USB ID match 0x04a9:0x30f2
(model name "Canon:PowerShot SD500 (normal mode)")
0.080288 context(2): Detected a 'Canon:PowerShot SD500 (normal mode)'.
Detected a 'Canon:PowerShot SD500 (normal mode)'.
0.080975 gphoto2-port(2): Reading message (request=0xc value=0x55
index...

[Johnathon (outdooricon)]

This is the entire debug output from gphoto when attaching my camera, after I performed the rm of /usr/lib/gphoto2/2.1.6/libgphoto2_canon.so .

[Johnathon (outdooricon)]

I can confirm that the rm /usr/lib/gphoto2/2.1.6./*canon* workaround works in breezy, and so it defaults to using the libgphoto2_ptp2.so module instead. At least we know this narrows down the problem to the canon module itself then. I have attached my debug output which is displayed AFTER using the workaround, in case this is useful too.

[Marcus Meissner (meissner)]

this is a known bug of the canon driver.

it will be fixed in the next libgphoto2 release (by commenting the ids out)

[Johnathon (outdooricon)]

Will the relase make it into Dapper?

[Martin Pitt (pitti)]

Marcus, is this already fixed in upstream svn? I couldn't find anything obvious.

[Marcus Meissner (meissner)]

yes.

it is however basically #if 0s around several canons.

I will attach a patch that does that.

Ciao, Marcus

[Marcus Meissner (meissner)]

if 0 some cameras.

[Martin Pitt (pitti)]

Thanks, Markus!

[Martin Pitt (pitti)]

 libgphoto2 (2.1.6-5.2ubuntu8) dapper; urgency=low
 .
   * camlibs/canon/canon.c: Disable normal mode of some Canon cameras which
     were found only to work in PTP mode. Thanks to Marcus Meissner for
     providing the upstream patch. Closes: LP#27586
   * camlibs/ptp2/library.c: Disable theme.dat special file handling; it's not
     yet complete and just breaks (upstream svn has it disabled for now, too).
     Closes: LP#43163