ricoh caplio R4 isn't recognized

[Marco Di Pauli]

With the last hardy updates (11 april) my ricoh caplio r4 isn't recognized anymore.... only in usb mass storage mode

[Marco Di Pauli (dipa86)]

Oh gosh, in the title I wrote r5... I mean r4 not r5, my mistake, can I modify the title?

[Pascal De Vuyst (pascal-devuyst)]

Please provide the information described here: https://wiki.ubuntu.com/DebuggingRemovableDevices.

[Marco Di Pauli (dipa86)]

If I use these information it says:

user@linuxbox:~$ killall gnome-volume-manager
gnome-volume-manager: nessun processo terminato
user@linuxbox:~$ gnome-volume-manager -n 2>&1 | tee gvm.log
bash: gnome-volume-manager: command not found
user@linuxbox:~$

I have gnome-volume-manager installed...so, why it says this?

under "removable devices" options, I specified that when a camera is plugged in f-spot asks to import pictures....it works! it recognizes a "generic camera" (with gutsy It recognizes correctly "ricoh caplio r4") and it can import pictures, but under devices or on the desktop I can't see any camera mounted!

[vik (askvictor)]

to run gnome-volume-manager, try '/usr/lib/gnome-volume-manager/gnome-volume-manager -n 2>&1 | tee gvm.log'

I have a similar problem with a caplio R1 - under both gutsy and hardy, f-spot sees that the camera is there, and even recognises it as a Caplio R1, (on importing, it brings up a 'camera selection' box which lets me choose between two ricoh caplio r1's - one on port usb: and the other on port usb:007,016 (or other number depending which usb port I'm plugged in to)). It then thinks for a few seconds, and comes up with a box 'error connecting camera - received error "Error reading from the port" while connecting to camera'. It does this irrespective of which port I choose in the previous step.

[Marco Di Pauli (dipa86)]

I attach hal and udev logs... I can't get a gvm log, I don't understand why, even if I use '/usr/lib/gnome-volume-manager/gnome-volume-manager -n 2>&1 | tee gvm.log'.

[Marco Di Pauli (dipa86)]

why it is still marked as incomplete?

[Brian Murray (brian-murray)]

Could you please also add the USB device id of this via 'lsusb'? Thanks in advance.

[vik (askvictor)]

Here is some debugging info from my R1:
$ lsusb | grep Ricoh
Bus 003 Device 006: ID 05ca:220d Ricoh Co., Ltd Caplio R1/RZ1
$ id
uid=1000(vik) gid=1000(vik) groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),106(fuse),108(lpadmin),114(admin),124(sambashare),125(vboxusers),1000(vik),1002(shared)
$ id hal
id: hal: No such user
$ id haldaemon
uid=110(haldaemon) gid=122(haldaemon) groups=122(haldaemon)
$ uname -a
Linux dust 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 GNU/Linux

attached are the log files

[carchaias (carchaias)]

I've the same Problem. Exactly like #4.

[penalvch (penalvch)]

Marco Di Pauli, thank you for reporting this bug to Ubuntu. Is this an issue in a supported release? If so, could you please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 216294

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]