can't mount digital camera showing a window popup message: -60 could not lock the device message

[bill goldberg]

Ubuntu 8.10 can't seem to mount my Lumix DMC-LS80 camera.

It worked fine in Ubuntu 8.04.1

An error box pops up saying:

Unable to mount Panasonic (Matsushita) Lumix DMC-FZ10 Camera

Error initializing camera: -60: Could not lock the device

The dmesg command after adding the camera:

[29369.836032] usb 1-1: new full speed USB device using ohci_hcd and address 3
[29370.006867] usb 1-1: configuration #1 chosen from 1 choice
[29370.008591] scsi10 : SCSI emulation for USB Mass Storage devices
[29370.009970] usb-storage: device found at 3
[29370.009975] usb-storage: waiting for device to settle before scanning
[29418.139185] usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd gvfsd-gphoto2 rqt 33 rq 102 len 0 ret -62

Most of the time the last line doesn't get mentioned. The one I get now is:

[31067.144041] usb 1-1: new full speed USB device using ohci_hcd and address 6
[31067.315387] usb 1-1: configuration #1 chosen from 1 choice
[31067.330233] scsi13 : SCSI emulation for USB Mass Storage devices
[31067.334453] usb-storage: device found at 6
[31067.334458] usb-storage: waiting for device to settle before scanning

[Yuriy Tkachenko (yuriytk)]

The same happens with Panasonic Lumix DMC-FZ8 camera.
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/195976/comments/12 helps to mount camera as usb disk.

[Ian Weisser (ian-weisser)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingHardwareDetection as separate attachments.

[bill goldberg (billgoldbergmania)]

Ok, the correct info is attached now.

[bill goldberg (billgoldbergmania)]

I can't seem to put multiple files in one comment, so sorry, but this is going to take a few posts.

[bill goldberg (billgoldbergmania)]

See above.

[bill goldberg (billgoldbergmania)]

Dito.

[bill goldberg (billgoldbergmania)]

Idem.

[Connor Imes (ckimes)]

Bill, are you able to mount the device manually with the mount command? If you need help with that please, post the output of
 sudo fdisk -l
 cat /etc/fstab
 mount
 sudo blkid
with the device plugged in. Thanks in advance.

[bill goldberg (billgoldbergmania)]

sudo fdisk -l:

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x35f7bad7

   Device Boot Start End Blocks Id System
/dev/sda1 1 25019 200965086 83 Linux
/dev/sda2 * 25020 30119 40965750 7 HPFS/NTFS
/dev/sda3 30120 30401 2265165 82 Linux swap / Solaris

Disk /dev/sdb: 500.1 GB, 500107862016 bytes <i>(this is my external hdd)</i>
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8d399bc0

   Device Boot Start End Blocks Id System
/dev/sdb1 1 60427 485379846 b W95 FAT32
/dev/sdb2 60428 60801 3004155 5 Extended
/dev/sdb5 * 60428 60801 3004123+ b W95 FAT32

-------------------

cat /etc/fstab

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=0fcfdd46-270c-4b34-8f39-8aa8fb90e3c8 / reiserfs notail,relatime 0 1
# /dev/sda3
UUID=af36cfb7-a684-4c91-9e2c-f962be6107c0 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

---------------
mount

/dev/sda1 on / type reiserfs (rw,relatime,notail)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
/proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,nosuid,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
lrm on /lib/modules/2.6.27-7-generic/volatile type tmpfs (rw,mode=755)
securityfs on /sys/kernel/security type securityfs (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/rw/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=rw)
/dev/sdb1 on /media/disk type vfat (rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush)
/dev/sdb5 on /media/disk-1 type vfat (rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush)

--------------

sudo blkid

/dev/sda1: UUID="0fcfdd46-270c-4b34-8f39-8aa8fb90e3c8" TYPE="reiserfs"
/dev/sda2: UUID="78783E6B783E2870" TYPE="ntfs"
/dev/sda3: TYPE="swap" UUID="af36cfb7-a684-4c91-9e2c-f962be6107c0"
/dev/sdb1: UUID="474D-A3A2" TYPE="vfat"
/dev/sdb5: UUID="474D-A36F" TYPE="vfat"

[Connor Imes (ckimes)]

I am not seeing the device appear in the fdisk command at all, which would lead me to believe either you didn't have the device plugged in, or something is terribly wrong with it. I do see it appear in the lsusb command at least:

Bus 002 Device 004: ID 04da:2372 Panasonic (Matsushita) Lumix DMC-FZ10 Camera

If you have the hardware to do so (like that media card reader I see), can you plug the camera's flash card in to the computer without using a USB cable to the camera? Does it mount? Right now it is looking like you have a hardware problem with the camera.

[bill goldberg (billgoldbergmania)]

The camera was plugged in. And it was showing in nautilus and gave the same error I mentioned in the OP.

I don't have a flash card in the camera (nor own one), everything is on the internal drive.

The camera was working fine a few days ago in Hardy.

I can't check now, but I'll try it on hardy again tommorow and see if it works, but it should.

[Connor Imes (ckimes)]

OK, that is an appropriate next step. Let me know if it works in Hardy.

[bill goldberg (billgoldbergmania)]

I couldn't test it in Hardy, but tested in Windows XP;

The camera is fine and works as expected.

When I plugged it in today, I was prompted (for the first time) by Ubuntu itself to send the bugreport.

See:

https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/288691

-------------

I checked the commands I gave again after I was prompted to send the bug report. Still no mention of the device in any of them.

[Connor Imes (ckimes)]

I have marked bug #285682 as a duplicate of this - a developer can look there for more technical data.

This current bug report contains the background information and discussion. I am setting the package to gvfs and setting the status to Triaged so a developer can begin work. Thank you.

[bill goldberg (billgoldbergmania)]

Thank you.

Should the person who will take on this bug need more info, feel free to contact me.

[Adam Hunt (adamandruth)]

I just wanted to draw your attention to Ubuntu Forum post http://ubuntuforums.org/showthread.php?t=965167

This posting has collected reports of similar problems as described here in this bug report, but for many different brands and models of cameras, including Panasonic, Nikon, Canon and Kodak. In all cases they worked fine on 8.04 and now fail to work in 8.10. It seems the problem is wide-spread.

I will post a link to this bug report on the forum page, just to keep that group of users up to date and prevent duplicate reporting.

[SimonWerner (simonwerner)]

I have the same problem with a Canon S5 IS. The camera is auto-mounted, then the "Import Photos" dialog appears and there is the error message. Unmounting the camera, then running the import again it works. Note, that I upgraded from 8.04.1, I did not install from scratch.

[bill goldberg (billgoldbergmania)]

According to the post it seems that loads of people are affected by this bug.

[Adam Hunt (adamandruth)]

It seems from reading the Ubuntu Forum http://ubuntuforums.org/showthread.php?t=965167&page=3 that this problem may have been fixed by updates sent out for Intrepid since it was released.

[bill goldberg (billgoldbergmania)]

I can confirm that the recent updates in Intrepid fixed this issue.

[Retief de Villiers (retief-devilliers)]

I can confirm that my Nikon Coolpix S550, which worked perfectly without a hitch in Hardy, does not work at all in my fully up to date Intrepid. I get similar error messages as mentioned in the posts above. This bug is not solved yet and really requires urgent attention. I have photographs that I want to download from my camera and I do not want to approach one of my gloating Windows colleagues!

[Adam Hunt (adamandruth)]

For those users who still can't get their camera recognized by Ubuntu 8.10, as the forum post describes, there is a work-around, as long as your camera uses a removable SD card, which many do. If you obtain a USB-SD card reader, remove the SD card from the camera and insert teh SD card in USB-SD card reader then Ubuntu will interpret the reader as a 'generic USB device' and the photos can be copied from the SD card.

While inconvenient, SD card readers are available at most computer shops for under $5, or come free with the SD card in some cases.

I wouldn't consider this suggestion a fix or a replacement for solving this bug, but it might reduce the urgency for some users who need to get their photos off their camera right away. If your camera has only a fixed memory instead of an SD card then this won't help.

[Walter (walter-kramer)]

The SD card reader work around does not work for me. Camera is a Leica Digilux 3 which is basically the same camera as the Panasonic DMC-L1. As all the above I had no issues with Hardy.

[SilverLoz (launchpad-loznet)]

The latest updates did _not_ fix it for my camera: Canon 400D. The following error message continues to be displayed in the import dialogue: "An error occurred in the io-library ('Could not lock the device'): Camera is already in use." It all worked flawlessly in Hardy but is broken in Intrepid. (If it makes a difference. I upgraded from Hardy). Logs attached.

[Walter (walter-kramer)]

For what it may be worth. I reinstalled Intrepid last night, keeping home intact of course. This seems to have fixed the problems I was having with my Leica and Panasonic cameras. Somehow the updates were ineffective on my system until now. This might be a last resort for Leica and Panasonic users still having problems.

[Onestar (thejournalofonestar)]

I can confirm that recent updates have NOT resolved this issue.

My camera (Olympus C-2100UZ) worked in previous releases, Hardy included, but does not work with Intrepid.

The workaround does not work for me. It is an older (but very good) camera that uses SmartMedia, and I have no external adapters for said media.

[Andres Mujica (andres.mujica)]

Hi, i've marked some dups to this bug.

Anyone has reported the issue upstream?

Are you using f-Spot or gthumb ?

Is it possible for someone to test what is explained here:

https://bugs.edge.launchpad.net/ubuntu/+source/gvfs/+bug/258083/comments/15

and post the output?

Thanks, is possible that this issue is related to that bug also.

[Sebastien Bacher (seb128)]

those who have the issue should run gvfs-mount -li and attach the log to the bug. it's likely not a gvfs issue

[steve.horsley (steve-horsley)]

I also habe a problem, with a Pentax optio 550. Worked perfectly with every version of Ubuntu until 8.10. In 8.10, the camera is recognides and I choose to browse as a folder - I always use this method. In intrepid, nautilus freezes trying to browse the camera. While the frozen window is on the screen, dragging it across desktop icons erases them and they don't repaint. Right-clicking the desktop camera icon and choosing to unmount also freezes until I power the camera off or unplug it.

gvfs-mount -li returns without printing anything.

dmesg shows these lines - they look OK to me...
[ 540.908034] usb 2-4: new full speed USB device using ohci_hcd and address 4
[ 541.129424] usb 2-4: configuration #1 chosen from 1 choice
[ 541.404169] usbcore: registered new interface driver libusual
[ 541.483984] Initializing USB Mass Storage driver...
[ 541.497650] scsi6 : SCSI emulation for USB Mass Storage devices
[ 541.502535] usbcore: registered new interface driver usb-storage
[ 541.504259] USB Mass Storage support registered.
[ 541.506317] usb-storage: device found at 4
[ 541.506326] usb-storage: waiting for device to settle before scanning

Intrepid was installed from scratch, not an upgrade although the /home partition was previously used by Hardy.

[steve.horsley (steve-horsley)]

More info. When I plug the camera in and I am logged into gnome, the camera does not work. Gnome offers to open the camera, and sometimes the folder view shows the top-level DCIM directory, but it hangs when I try to look inside that directory. I attach a screenshot of the problem (with a tail of /var/log/messages behind).
I notice that the camera does NOT show up in fdisk.

However, if I kill GDM and work in text consoles, when I turn the camera on it DOES show up in fdisk as /dev/sdb1. I am then able to mount it, launch startx and browse the camera in nautilus. This demonstrates to me that the problem is not in the kernel USB handling but is misconfiguration of whatever auto-mounts the camera filesystem. Tailing /var/log/messages, these following messages occur that don't occur when a gnome user is logged in:

Nov 28 01:18:37 StevesPC kernel: [ 444.138675] scsi7 : SCSI emulation for USB Mass Storage devices
Nov 28 01:18:42 StevesPC kernel: [ 449.148557] scsi 7:0:0:0: Direct-Access PENTAX PENTAX OPTIO 550 1.00 PQ: 0 ANSI: 2
Nov 28 01:18:42 StevesPC kernel: [ 449.163535] sd 7:0:0:0: [sdb] 4022272 512-byte hardware sectors (2059 MB)
Nov 28 01:18:42 StevesPC kernel: [ 449.181116] sd 7:0:0:0: [sdb] Write Protect is off
Nov 28 01:18:42 StevesPC kernel: [ 449.199543] sd 7:0:0:0: [sdb] 4022272 512-byte hardware sectors (2059 MB)
Nov 28 01:18:42 StevesPC kernel: [ 449.206534] sd 7:0:0:0: [sdb] Write Protect is off
Nov 28 01:18:42 StevesPC kernel: [ 449.211476] sdb: sdb1
Nov 28 01:18:42 StevesPC kernel: [ 449.229683] sd 7:0:0:0: [sdb] Attached SCSI removable disk
Nov 28 01:18:42 StevesPC kernel: [ 449.230274] sd 7:0:0:0: Attached scsi generic sg2 type 0

I read in another bug report that gphoto2 was being excluded from Hardy, and I notice that in my screenshot, the non-functional URL is a gphoto2 URL, so I am guessing that this is where the problem lies and it is suppressing the normal mass storage SCSI emulation.

[SilverLoz (launchpad-loznet)]

In addition to my previous logs, here's the output from performing the gvfs-mount -l routine as linked to in comment #27 and as requested in comment #28 by Sebastien.

[O. Emmerson (oemmerson)]

I have the same problem.
I'm using a Kodak DX6490.

I get the error message "An error occurred in the io-library ('Could not lock the device'): Camera is already in use."
and the dmesg:
[ 4607.780064] usb 3-1: new full speed USB device using uhci_hcd and address 2
[ 4607.985085] usb 3-1: configuration #1 chosen from 1 choice
[ 4613.384242] usb 1-4: usbfs: USBDEVFS_CONTROL failed cmd gvfsd-gphoto2 rqt 192 rq 1 len 1000 ret -110
[ 4617.508922] usb 1-4: usbfs: USBDEVFS_CONTROL failed cmd gthumb rqt 128 rq 6 len 1000 ret -110
[ 4630.824063] usb 3-1: USB disconnect, address 2
[ 4631.314126] gthumb[19626]: segfault at 1 ip b78fa892 sp bfe99330 error 4 in libgtk-x11-2.0.so.0.1400.4[b781e000+395000]

I could use the card reader but I had some pictures on the internal memory.
I was able to get the photos off the camera by partly following the workaround at https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/287689:
In Removable Drives and Media Preferences (System > Preferences > Removable Drives and Media > Cameras > Digital Camera), uncheck the Import digital photographs when connected.
I then unmounted the camera in Nautilus when I connect it.
However using "gphoto --import-photos" on the command line still didn't work. However adding a sudo in front of the command enabled me to import the photos.

Now trying the command again it is not working now.
I get the error "An error occurred in the io-library ('Unspecified error'): No error description available"
and dmesg:
[ 7809.352154] usb 3-1: new full speed USB device using uhci_hcd and address 15
[ 7809.570980] usb 3-1: configuration #1 chosen from 1 choice
[ 7841.184055] usb 3-1: USB disconnect, address 15
[ 7871.512116] usb 3-1: new full speed USB device using uhci_hcd and address 16
[ 7871.729874] usb 3-1: configuration #1 chosen from 1 choice

[lnxeric (eric-bahnerth)]

Don't know if this is still an issue, but I had the same problem, and found the following :
Gnome, (and probably kde as well) mounted the cam directly as an mass storage device. So by the time GTkam or gphoto2 got to the point of mounting it, it was already in use. After unmounting de cam in filemanager, it worked fine in GTkam.

regards.

Eric

[David Tombs (dgtombs)]

Here's the requested output from "gvfs-mount -li" when I have inserted the camera but am not able to mount it.

If I kill gvfs-gphoto2-volume-monitor, the issue disappears and I get the standard GUI prompt "You have just inserted a medium with digital photos..." just like in Hardy. I can then download photos using gThumb or Nautilus as normal.

Let me know if I can provide any more information.

[dmandell (dmandell)]

I can confirm that killing gvfs-gphoto2-volume-monitor allowed me to use the camera w/ FSpot, whereas if I don't kill it, the camera is inaccessible.

[Davide Capodaglio (davidecapod)]

I am using gthumb to import photos from my Canon Ixus 850IS (I don't like f-spot).
But in intrepid the camera is automatically mounted by gvfs-gphoto2-volume-monitor as a removable media (even if it uses PTP protocol), and gthumb can not access it until I manually unmount it.
After the umount everything works perfectly.

[Adam Hunt (adamandruth)]

Walter Kramer indicated above that the SD card reader solution didn't work for him.

I just picked up an SD card reader, a "USB ALL-IN-ONE FLASH CARD READER" http://factorydirect.ca/catalog/product_spec.php?pcode=CA2300

I tried it out on Hardy and it works fine, as does my Panasonic DMC-FZ2 camera. I tried the reader out on Intrepid Live CD (which is "original", no updates applied) and it works fine there as well even though the camera is not recognized.

This reader works with four different SD card formats. The packaging specifically indicates that it is Linux-compatible, as well and Mac and Windows. The unit is Chinese in origin and, humourously, the brand name on the packaging is "Enjoy Technology, Enjoy Life".

For those people who tried an SD reader and found it didn't work, the problem may have well been the type of SD card reader itself.

I should note again that I don't consider the SD card reader a solution to this problem - there is no good reason why a camera should work on Hardy and not on Intrepid, but this "stop-gap solution" may at least allow people to get their photos downloaded while this problem is addressed, since it seems it will not be a quick fix.

[Udovicic (simcha)]

gsmart mini 2 isn't working on intrepid with all updates.

I had to manually unmount it, and reload gspca in order to make it work.

$ gvfs-mount --unmount-scheme gphoto2
$ sudo /sbin/modprobe -vr gspca-sunplus
$ sudo /sbin/modprobe -v gspca-sunplus

that worked for me

[harriv (harriv)]

My analysis with up to date Ubuntu 8.10, I just stumbled to this and with help of this entry found out following:

1. gvfs-gphoto2-volume-monitor startups for each logged in user
2. If there's two logged in, I cannot contact my Canon camera
3. After killing the another gvfs-gphoto2-volume-monitor process, I can connect my camera and access the files.

[JP Foster (jeepster)]

I am seeing this same bug in Jaunty now.
Killing gvfs-gphoto2-volume-monitor allows me to access the camera.

[Sebastien Bacher (seb128)]

could you run "gphoto2 --summary" and "gvfs-mount -li" just after connecting the camera too?

[Sebastien Bacher (seb128)]

could you run "gphoto2 --summary" and "gvfs-mount -li" just after connecting the camera too (ie when you have the dialgos displayed)?

[Peter Whittaker (pwwnow)]

I performed the sequence described above. For my daughter's account, error message (-60) then gthumb photo import (her default action) is started. For my account, same result as above (error, 2 dialogues); for guest, same (error, 2 dialogues).

In all cases, despite error messages and extra dialogues, photo import works fine.

I do not believe I made any other changes to the system, but now I am doubting myself.

As for the command output you requested,

$ gphoto2 --summary
The program 'gphoto2' is currently not installed. You can install it by typing:
sudo apt-get install gphoto2
bash: gphoto2: command not found

The output of gvfs-mount -li is attached.

[Sebastien Bacher (seb128)]

could you install gphoto2 as indicated by the message before and try again to get the log?

[Peter Whittaker (pwwnow)]

On Thu, 2009-05-14 at 23:18 +0000, Sebastien Bacher wrote:
> could you install gphoto2 as indicated by the message before and try
> again to get the log?

I installed the app, tried again, but forgot to get the log. However,
the results were worse:

        Install gphoto2

        Connect camera: Error -60, error -1

        No default application, no pop-up to choose application

        Start f-spot, attempt to connect to camera, long delay, then
        error: unable to access camera, unknown error

        uninstall gphoto2, libcdk5, repeat: Same result!

So installing gphoto2 borked what used to work.

[David Tombs (dgtombs)]

Is gphoto2 still configured?

[Paolo Benvenuto (donpaolo)]

> could you run "gphoto2 --summary" and "gvfs-mount -li" just after connecting the camera too (ie when you have the dialgos displayed)?

$ LC_ALL=C gphoto2 --summary

*** Error ***
An error occurred in the io-library ('Could not lock the device'): Camera is already in use.
*** Error (-60: 'Could not lock the device') ***

For debugging messages, please use the --debug option.
Debugging messages may help finding a solution to your problem.
If you intend to send any error or debug messages to the gphoto
developer mailing list <email address hidden>, please run
gphoto2 as follows:

    env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt --summary

Please make sure there is sufficient quoting around the arguments.

$ LC_ALL=C gvfs-mount -li
Drive(0): Unit? CD-RW/DVD?RW
  Type: GProxyDrive (GProxyVolumeMonitorHal)
  ids:
   hal-udi: '/org/freedesktop/Hal/devices/storage_model_DVD_RAM_GSA_H58N'
   unix-device: '/dev/sr0'
  themed icons: [drive-optical-recorder] [drive-optical] [drive]
  is_media_removable=1
  has_media=0
  is_media_check_automatic=1
  can_poll_for_media=1
  can_eject=1
Drive(1): Unit? USB
  Type: GProxyDrive (GProxyVolumeMonitorHal)
  ids:
   hal-udi: '/org/freedesktop/Hal/devices/storage_serial_SAMSUNG_HM500LI_6830000dd6a4_0_0'
   unix-device: '/dev/sdb'
  themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive]
  is_media_removable=0
  has_media=1
  is_media_check_automatic=0
  can_poll_for_media=0
  can_eject=0
  Volume(0): EsternoFAT
    Type: GProxyVolume (GProxyVolumeMonitorHal)
    ids:
     uuid: '1500-2247'
     hal-udi: '/org/freedesktop/Hal/devices/volume_uuid_1500_2247'
     unix-device: '/dev/sdb1'
     label: 'EsternoFAT'
    uuid=1500-2247
    themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive]
    can_mount=1
    can_eject=0
    Mount(0): EsternoFAT -> file:///media/EsternoFAT
      Type: GProxyMount (GProxyVolumeMonitorHal)
      uuid=1500-2247
      themed icons: [drive-harddisk-usb] [drive-harddisk] [drive]
      can_unmount=1
      can_eject=0
      is_shadowed=0
  Volume(1): EsternoEXT3
    Type: GProxyVolume (GProxyVolumeMonitorHal)
    ids:
     uuid: 'a190eced-bda5-45d1-9724-ba84d7ec78f2'
     hal-udi: '/org/freedesktop/Hal/devices/volume_uuid_a190eced_bda5_45d1_9724_ba84d7ec78f2'
     unix-device: '/dev/sdb2'
     label: 'EsternoEXT3'
    uuid=a190eced-bda5-45d1-9724-ba84d7ec78f2
    themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive]
    can_mount=1
    can_eject=0
    Mount(0): EsternoEXT3 -> file:///media/EsternoEXT3
      Type: GProxyMount (GProxyVolumeMonitorHal)
      uuid=a190eced-bda5-45d1-9724-ba84d7ec78f2
      themed icons: [drive-harddisk-usb] [drive-harddisk] [drive]
      can_unmount=1
      can_eject=0
      is_shadowed=0
Volume(0): Canon, Inc. Canon Digital Camera
  Type: GProxyVolume (GProxyVolumeMonitorGPhoto2)
  ids:
   hal-udi: '/org/freedesktop/Hal/devices/usb_device_4a9_3126_noserial_if0'
   unix-device: '/dev/bus/usb/001/013'
  ac...

[David Tombs (dgtombs)]

Interestingly, in Jaunty I must kill gvfs-gphoto2-volume-monitor to get even my Sansa e260 mp3 player to be recognized as well. This bug is getting worse.

When gvfs-gphoto2-volume-monitor is running, I have the familiar last message in syslog: "usb-storage: waiting for device to settle before scanning"

If I can provide more information, I'd love to.

[Neil Hollow (hollowfamily)]

Definitely a bug on 8.10 no question this camera canon ixus 70 worked in 8.04 etc, the suggestion of switching the camera on then plugging in has worked for me, but this was unnecessary before. Problem seems to have gone away on Jaunty.

[Peter Whittaker (pwwnow)]

Marking this as confirmed since it is still a bug, and a well documented one given the contributions between 05-12 and 06-15.

Update: Plugged in camera today. Error -60 (as above), error -1 (as above), errors in dmesg. Found this bug report (how could I have forgotten it! :->), killed gvfs-gphoto2-etc., remounted camera, no errors, able to import photos but had to start f-spot manually.

Difference between then and now? Recent system updates must have restored sufficient sanity to unbork the system, though it still does not work as expected.

[Paolo Benvenuto (donpaolo)]

The bug has been fixed by upstream in trunk:

http://bugzilla.gnome.org/show_bug.cgi?id=583796
http://bugzilla.gnome.org/show_bug.cgi?id=560352

but unfortunatly it's not easily fixed in stable version.

Let's pray that gthumb be released soon.

[David Tombs (dgtombs)]

Sweet! So I guess the cause is that gthumb is grapping the camera before gvfs can? If so, I wonder why gthumb gets there first on some machines but everyone else (presumably Sebastian :-P) has gvfs winning.

[Lee Kelvin (lsk9)]

I'm not sure if its of any use to some, but I was having this problem and found a solution (thats nothing to do with gthumb - I dont have gthumb installed, and so after reading through this post went away to find a solution of my own!)

I was getting the same thing, plug in my camera (an iPhone in this case) and it would appear on the desktop twice, with 2 popups asking me what to do with the camera (run f-spot, do nothing etc) and 1 error -60 box as described above (no error -1). Its obvious that 2 programs are grabbing this when I plug the phone in.

I tried removing a few recently installed packages, as recently I've been trying to use itunnel to get into my iPhone filesystem. itunnel requires libiphone0 and libiphone-dev, dependencies of which are libusbmux0 and libusbmux-dev. After removing libusbmux0 and libusbmux-dev - voila, only 1 phone icon on my desktop and only 1 popup (no errors).

Does mean i cant use itunnel any more... but it wasnt working any way - boo

Hope that helps somebody with a similar problem!

[David Tombs (dgtombs)]

Well, I can't test with my camera anymore since it's broken, but my Sansa mp3 player works now in Karmic RC. Can anyone else confirm that this is fixed in Karmic?

[Christian (c-pradelli)]

I can confirm that this problem still exist in karmic, (of course not in kubuntu).

[vdbergh (michel-vandenbergh)]

Yes this problem still exists in karmic. After plugging in a camera an incomprehensible mess of error dialogs is spawned
by the foto app du jour that pops up (either f-spot of gthumb) and photo's cannot be imported.

After reading the above bug reports I realize this is because gvfs has mounted the camera before the application can
get to it.

Even after setting the default action in Nautilus to "do nothing" there is still an error dialog (Error 60 as above).
This one seems to be harmless though. I can get the pictures from the gvfs device (as if it was a regular folder).

Importing photo's worked very well in Ubuntu 7.04 so I was quite shocked by this regression.

[James (jim-warkior)]

I have also found this to be a problem with a fresh install of Karmic. I have a Canon Powershot S1IS and when I plug it in via USB I see the following:

1. New icon appears on the desktop with camera name as if it is a mounted drive.
2. gThumb importer pops up with error message An error occurred in the io-library ('Could not lock the device'): Camera is already in use.
3. Desktop icon disappears
4. Error remains and I can't import the photos.

In order to resolve this, I am able to go into the import settings by clicking on the camera icon on the importer. I then select my camera and click 'OK'. It will then successfully connect to the camera, and allow me to download the photos.

[Retief de Villiers (retief-devilliers)]

With trepidation I plugged my brand new Nikon D5000 into my Ubuntu 9.10
equipped laptop this morning to download the first pictures taken with the
camera. Great was my relief when a window popped up offering to open F-spot
or a folder. It thus seems that the issue is resolved for my current
camera/laptop combination. It also seems that this is a problem that still
must be solved. Getting an error message when plugging in a digital camera
into a USB port is like getting an error message when trying to send e-mail.
It is a function that is simply expected to work perfectly on all personal
computing equipment today.

2009/12/16 James <email address hidden>

> I have also found this to be a problem with a fresh install of Karmic.
> I have a Canon Powershot S1IS and when I plug it in via USB I see the
> following:
>
> 1. New icon appears on the desktop with camera name as if it is a mounted
> drive.
> 2. gThumb importer pops up with error message An error occurred in the
> io-library ('Could not lock the device'): Camera is already in use.
> 3. Desktop icon disappears
> 4. Error remains and I can't import the photos.
>
> In order to resolve this, I am able to go into the import settings by
> clicking on the camera icon on the importer. I then select my camera
> and click 'OK'. It will then successfully connect to the camera, and
> allow me to download the photos.
>
> --
> Ubuntu 8.10 can't mount digital camera showing a window popup message: -60
> could not lock the device message
> https://bugs.launchpad.net/bugs/285682
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[SimonWerner (simonwerner)]

I can confirm that I still get this problem on 9.10. I have installed a fresh system on new hardware (Acer Aspire 7530). But the camera is the same (Canon PowerShot S5 IS).

This is quite an embarrassing bug.

[hemna (dickfardos)]

I can also confirm this issue still exists in 9.10. I'm using a Panasonic Lumix DMC-FX01.

7425 0.191264 gphoto2-port-usb(1): Looking for USB device (vendor 0x4da, product 0x2374)... found.
7426 0.191276 gphoto2-port-usb(2): inep to look for is 82
7427 0.191288 gphoto2-port-usb(1): Detected defaults: config 1, interface 0, altsetting 0, inep 82, outep 01, intep 83, class 06, subclass 01
7428 0.191301 gphoto2-abilities-list.c(2): Found 'Panasonic DMC-FZ20' (0x4da,0x2374)
7429 0.191319 gphoto2-port(2): Freeing port...
7430 0.191333 gphoto2-port(2): Closing port...
7431 0.191871 gphoto2-camera(2): Setting abilities ('Panasonic DMC-FZ20')...
7432 0.191891 gphoto2-port-info-list(2): Looking for path 'usb:' (17 entries available)...
7433 0.191907 gphoto2-port-info-list(2): Getting info of entry 5 (17 available)...
7434 0.191921 gphoto2-camera(2): Setting port info for port 'Universal Serial Bus' at 'usb:'...
7435 0.192939 gphoto2-port(2): Setting timeout to 5000 millisecond(s)...
7436 0.192957 gphoto2-port(2): Setting settings...
7437 0.192969 libusb(2): gp_port_usb_update(old int=0, conf=-1, alt=-1), (new int=0, conf=-1, alt=-1)
7438 0.193322 gphoto2-port-usb(1): Looking for USB device (vendor 0x4da, product 0x2374)... found.
7439 0.193336 gphoto2-port-usb(2): inep to look for is 82
7440 0.193347 gphoto2-port-usb(1): Detected defaults: config 1, interface 0, altsetting 0, inep 82, outep 01, intep 83, class 06, subclass 01
7441 0.193359 gphoto2-camera(2): Loading '/usr/lib/libgphoto2/2.4.6/ptp2'...
7442 0.193625 gphoto2-port(2): Opening USB port...
7443 0.193639 libusb(2): gp_port_usb_open()
7444 0.193674 gphoto2-port(0): Camera is already in use.
7445 0.193711 context(0): An error occurred in the io-library ('Could not lock the device'): Camera is already in use.
7446 0.193794 gp-camera(2): Freeing camera...
7447 0.193808 gphoto2-port(2): Freeing port...
7448 0.193820 gphoto2-port(2): Closing port...
7449 0.193843 gphoto2-port(0): Could not release interface 0 (Invalid argument).
7450 0.193880 gphoto2-filesystem(2): resetting filesystem

[Philippe Coval (rzr)]

hi, the issue is still present but in my case using a Kodak EasyShare CX 7430
I noticed some segfault in dmesg :

[ 60.126879] gdu-notificatio[2422]: segfault at c ip 004d950e sp bfdb4200 error 4 in libgdu.so.0.0.0[4d0000+1c000]
[ 65.437093] gvfs-gdu-volume[2596]: segfault at c ip 004187da sp bf865990 error 4 in libgdu.so.0.0.0[410000+1c000]
[ 72.572339] gvfs-gdu-volume[2630]: segfault at c ip 00e707da sp bf92e970 error 4 in libgdu.so.0.0.0[e68000+1c000]
[ 101.177966] gvfs-gdu-volume[2815]: segfault at c ip 0090c7da sp bf940240 error 4 in libgdu.so.0.0.0[904000+1c000]

Workaround worked for me :

 sudo killall gvfs-gphoto2-volume-monitor

--
http://rzr.online.fr/q/gnome

[naomi (antifoundationalism)]

hi all

am afraid I'm done with ubuntu. This camera issue has killed it for me - i loved ubuntu, loved not having to use windows but now I can neither get my laptops webcam to connect (have posted about it.. no answers after months), my soundcard never worked properly and now can't get my camera to work (olympus FE-170) - the exact problem people are having here but sudo killall isn't working.

I'm a biologist not a computer person and by reply 70 my head was turned.. by the end of the thread I was near in tears. I don't care about whether this is a valid request or not (that was just bizzare) just that an answer can be given. Well like my webcam it seems an answer can't be given and I'm left with no choice but to go back to Billy G.

A 3 legged dog is still a dog but a laptop that wont do basic functions isn't a laptop.

[David Tombs (dgtombs)]

Hi naomi,

I'm sorry to hear you're leaving. If you want to give it another try the
cleanest workaround I've found is to do the following:

1) Open a terminal
2) cd /usr/share/gvfs/remote-volume-monitors/
3) sudo mv gphoto2.monitor ghoto2.monitor.ren

I'm not sure if this will break anything else, but I've been using it on
my system for 6 months and all my USB devices are working fine.

Hope it helps,
David

naomi wrote:
> hi all
>
> am afraid I'm done with ubuntu. This camera issue has killed it for me -
> i loved ubuntu, loved not having to use windows but now I can neither
> get my laptops webcam to connect (have posted about it.. no answers
> after months), my soundcard never worked properly and now can't get my
> camera to work (olympus FE-170) - the exact problem people are having
> here but sudo killall isn't working.
>
> I'm a biologist not a computer person and by reply 70 my head was
> turned.. by the end of the thread I was near in tears. I don't care
> about whether this is a valid request or not (that was just bizzare)
> just that an answer can be given. Well like my webcam it seems an answer
> can't be given and I'm left with no choice but to go back to Billy G.
>
> A 3 legged dog is still a dog but a laptop that wont do basic functions
> isn't a laptop.
>

[michaehl (michaehl)]

Hi all,
almost similar to naomi I quit using any ubuntu versions younger than 8.04.
My reasons are
First:
I experienced the same (very well documented) troubles with a digital camera; in my case a Kodak EasyShare DX6340. I managed it with a different workaround but my girlfriend (just a normal computer user) don't know nothing about shell commands. Who could blame her for that?
Second:
The recovery mode grub offers at startup doesn't work on my machine (at least with 9.10 but I suppose even since 8.10). In case of big trouble (i.e. Gnome doesn't start) I'm totally lost and I'm obviously not the only one (see Bug #39991). Funny this bug is marked as NEW (July 2009).
Third:
In 8.04 my USB WLAN stick worked perfectly. Plugging it in and out anytime no matter how often produced the expected behaviour (network or no network respectively). In 9.10 plugging it out freezes the whole machine(!). My first experience of that kind on Linux!
Furthermore in 9.10 the whole functionality of network connection seems to be personally bound to each GNOME session. Starting the machine starts the WLAN stick and connects to the WLAN rather quickly but after GNOME begins to start and the login prompt is shown the connection vanished. After logging in correctly the connection is established again. Strange behaviour; a recource that is used by every user and should be provided by the system(!) is driven by user processes. A matter of software architecture I guess.

At the end I decided to go back to 8.04. The downgrade process worked rather flawlessly, because with the decission of manually partitioning every personal data (i.e. /home) was not touched.

So I am still a happy ubuntu user (although not really up to date - but who cares).

[David Tombs (dgtombs)]

This is a thread to discuss the bug, not a thread to discuss general issues, please.

[David Tombs (dgtombs)]

OK, I'm going to try to get some debug information on this issue. Could someone experiencing the problem please do the following:

1) Install version of gvfs from my PPA <https://launchpad.net/~dgtombs/+archive/ppa>. I have uncommented some debug output in the source.
2) killall gvfs-gphoto2-volume-monitor
3) /usr/lib/gvfs/gvfs-gphoto2-volume-monitor | tee g-g-v-m.log
4) Plug in your camera to reproduce the error.
5) Unplug camera.
6) Upload g-g-v-m.log here.

Thanks!

[David Tombs (dgtombs)]

Oh, please note you should probably reboot after installing my PPA version of gvfs, I had some issues with it before I did.

Sorry for the spam.

[Curtis White (soaro77)]

I'm having this same problem. I played around with it some and think I have an idea what the problem might be but I don't understand why. I tried three combinations of two different scenarios.

Scenario 1
1) Go into Preferences -> Removable Drives and Media
2) Set it to use gthumb (probably can be any photos program but I use gthumb so that's what I tested)

Scenario 2
1) Go into the File Browser
2) Select Edit -> Preferences
3) Go to the Media tab
4) Set it to gthumb (again can probably be any photos program)

I tried three combinations of the scenarios. First I tried enabling Scenario 1 while disabling Scenario 2. Then I tried enabling Scenario 2 and disabling Scenario 1. Finally I tried enabling both Scenarios at the same time.

When only Scenario 1 is enabled and I plug in the camera, it displays the Camera Import dialog box that has Import Photos and Ignore buttons. It also mounts the camera and an icon appears on the desktop with the name of the camera. If I press the Import Photos button I get the Import Photos dialog with the error listed in this bug. If I right click the camera mount icon on the desktop and select Unmount before I press the Import Photos button on the Camera Import dialog, everything works fine.

When I enable only Scenario 2, I never receive the Camera Import dialog with the Import Photos and Ignore buttons. It just directly displays the Import Photos dialog which contains the error. I briefly see the camera mount icon appear on the desktop and then vanish. I am not able to import the pictures no matter what I do when only this scenario is enabled.

When I enable both scenarios at the same time, both the Camera Import dialog with the Import Photos and Ignore buttons appears as well as the Import Photos dialog. The Import Photos dialog contains the error. The camera mount icon appears briefly on the screen and then vanishes as soon as I do anything at all. At this point I cannot do anything with the Import Photos dialog but close it since it contains the error. But if I choose the Import Photos button on the Camera Import dialog everything works just fine.

So all said, it appears to me that something is mounting the camera when you plug it in and then is not unmounting it properly. This then causes the error saying the camera is in use. But it seems the Import Photos dialog unmounts the camera and everything works fine after it has displayed the error.

[knarf (launchpad-ubuntu-f)]

Do you happen to have a media player like rhythmbox running in the background? Some of those also try to mount MTP devices and will happily mount your camera making it inaccessible to other programs.

For rhythmbox the solution is simple: disable the MTP plugin.

[Paul Crawford (psc-sat)]

Sounds a bit like bug #301731 and/or bug #74279 that I have been ranting on about, and also here:
https://sourceforge.net/tracker/?func=detail&atid=108874&aid=3004614&group_id=8874
and here:
https://bugzilla.gnome.org/show_bug.cgi?id=619538

[Brad (5t6554l)]

This revision/patch http://gphoto.svn.sourceforge.net/viewvc/gphoto?view=revision&revision=13117 may be a fix for this bug.

To test if if you are affected by the bug that this patch addresses, killall gvfs-gphoto2-volume-monitor (you may want to chmod -x /usr/lib/gvfs/gvfs-gphoto2-volume-monitor and reboot to make sure it's not running ) and then from the terminal: gphoto2 --storage-info

If gphoto2 --storage-info errors then this patch may be a fix for you.

The patch is a small one:

http://gphoto.svn.sourceforge.net/viewvc/gphoto/branches/libgphoto2-2_4/libgphoto2/camlibs/ptp2/library.c?view=patch&r1=13117&r2=13116&pathrev=13117

Rebuild libgphoto2-2 and apply the patch ( or make the changes by hand to storage_info_func() in library.c )

[wvarner (winshipvarner)]

I have a Nikon coolpix s203 camera and was running into a similar problem: dmesg:

[277743.548038] usb 3-4: new high speed USB device using ehci_hcd and address 12
[277743.682292] usb 3-4: configuration #1 chosen from 1 choice
[277744.980142] usb 3-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[277745.980162] usb 3-3: usbfs: USBDEVFS_CONTROL failed cmd gvfs-gphoto2-vo rqt 128 rq 6 len 1000 ret -110
[277748.012082] usb 3-4: usbfs: USBDEVFS_CONTROL failed cmd gvfs-gphoto2-vo rqt 128 rq 6 len 255 ret -110
[277749.320144] usb 3-3: usbfs: USBDEVFS_CONTROL failed cmd gvfs-gphoto2-vo rqt 128 rq 6 len 1000 ret -110
[277752.028052] usb 3-4: reset high speed USB device using ehci_hcd and address 12

As suggested in #106, I disable the MTP plugin in Rhythmbox, plugged my camera back in, and it was properly mounted. That seemed to be the problem for me. I'm using Ubuntu 10.04 with all updates installed.

[Zoubidoo (zoubidoo)]

Possible upstream: https://bugzilla.gnome.org/show_bug.cgi?id=623809

[Pander (pander)]

This is also the case for 12.04 when connecting an Samsung Galaxy S II. This results in
  Unable to mount SANSUNG_Android
and
  Error initializing camera: -60: Could not lock the device

This happends for store_00010001 and store_00010002 for which it is possible to have nautulis open a file browser.

[Pander (pander)]

Please confirm for the earlier reporters, does it mount with 12.04 but do you still get the error message?

[Kevin Wortman (kwortman)]

I still have the same problematic behavior with a Kodak EasyShare Z730 on 12.04. There is the -60 error message dialog, and two instances of the "Choose what application to launch" dialog. Shotwell is still able to import the photos despite all that.

[Philippe Lefevre (ph-l)]

This issue is still alive with ubuntu 10.04 and 11.04 for a Canon EOS 1000D
I just had to uninstall rhythmbox and gphoto2 works well now.

[Pander (pander)]

Meanwhile on Prcise 12.04 I get this error:
  Unable to mount SAMSUNG_Android
  Error initializing camera: -53: Could not claim the USB device

Two nautilus file eplorers get opened but only show the top-level directories. When navigating inside these directories, nothing can be found. In the /media and /mnt nothing is found either.

When ejecting via nautilus, this error occurs:
  Unable to unmount SAMSUNG_Android
  DBus error org.freedesktop.DBus.Error.UnknownMethod: Method "Unmount" with signature "sou" on interface "org.gtk.vfs.Mount" doesn't exist

[Janno2 (jan-kijlstra)]

I was using Entangle for tethered shooting in Ubuntu 12.04 with my Nikon D5000.

Has been working fine for some time, but for some months now) this is no longer the case.

In order to try to find a solution I stumbled upon this thread.

I do have the same errors as described in this thread.

The developper of Entangle was not able to solve the problem,
On www.gphoto2.org I was informed that my problem looks like the old gvfs-problem,

I'm tired of this problem, and about to stop using Ubuntu. I do not have a problem when a bug (re)occurs.
But if nobody seemes to be able a bug I for sure do have a serious problem.

[Janno2 (jan-kijlstra)]

Of course the last sentence has to be read: " But if nobody seems to be able to fix this bug I for sure do have a serious problem".

And I really do not understand why this problem is existing since 2008, and never a good solution was found.

It's almost like we are back in the old Microsoft times....