After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 642827 - gvfs tries to mount Kodak EasyShare C813 camera twice, giving error "Error initialising camera: -60: Could not lock the device"
gvfs tries to mount Kodak EasyShare C813 camera twice, giving error "Error in...
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: gphoto backend
1.6.x
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2011-02-20 18:38 UTC by Stuart Langridge
Modified: 2018-09-21 17:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stuart Langridge 2011-02-20 18:38:10 UTC
When plugging in my Kodak EasyShare C813 camera, I get an error dialog saying "Error initialising camera: -60: Could not lock the device". This appears to be because the camera has two mountpoints; one for the internal storage, and one for the external (SD card) storage. gvfs then mounts the first with gphoto, and then tries to mount the second with gphoto and can't (because it's conflicting with itself somehow).

Relevant output:

$ gvfs-mount -li
Drive(0): CD/DVD Drive
  Type: GProxyDrive (GProxyVolumeMonitorGdu)
  ids:
   unix-device: '/dev/sr0'
  themed icons:  [drive-optical]  [drive]
  is_media_removable=1
  has_media=0
  is_media_check_automatic=1
  can_poll_for_media=1
  can_eject=0
  can_start=0
  can_stop=0
  start_stop_type=unknown
Volume(0): KODAK EasyShare C813 Zoom Digital Camera
  Type: GProxyVolume (GProxyVolumeMonitorGPhoto2)
  ids:
   unix-device: '/dev/bus/usb/002/006'
  activation_root=gphoto2://[usb:002,006]/store_00010001
  themed icons:  [camera-photo]
  can_mount=1
  can_eject=0
  should_automount=1
  Mount(0): KODAK EasyShare C813 Zoom Digital Camera -> gphoto2://[usb:002,006]/store_00010001
    Type: GProxyShadowMount (GProxyVolumeMonitorGPhoto2)
    default_location=gphoto2://[usb:002,006]/store_00010001
    themed icons:  [camera-photo]
    x_content_types: x-content/image-dcf
    can_unmount=1
    can_eject=0
    is_shadowed=0
Volume(1): KODAK EasyShare C813 Zoom Digital Camera
  Type: GProxyVolume (GProxyVolumeMonitorGPhoto2)
  ids:
   unix-device: '/dev/bus/usb/002/006'
  activation_root=gphoto2://[usb:002,006]/store_00020001
  themed icons:  [camera-photo]
  can_mount=1
  can_eject=0
  should_automount=1
  Mount(0): KODAK EasyShare C813 Zoom Digital Camera -> gphoto2://[usb:002,006]/store_00020001
    Type: GProxyShadowMount (GProxyVolumeMonitorGPhoto2)
    default_location=gphoto2://[usb:002,006]/store_00020001
    themed icons:  [camera-photo]
    x_content_types: x-content/image-dcf
    can_unmount=1
    can_eject=0
    is_shadowed=0
Mount(2): KODAK EasyShare C813 Zoom Digital Camera -> gphoto2://[usb:002,006]/
  Type: GDaemonMount
  default_location=gphoto2://[usb:002,006]/
  themed icons:  [camera-photo]  [camera]
  x_content_types: x-content/image-dcf
  can_unmount=1
  can_eject=0
  is_shadowed=1
Comment 1 damien moore 2011-04-13 16:13:18 UTC
I've running across these issues in the past, but not consistently enough to want to fix it (mostly part because I usually just plug in SD cards instead of attaching the camera).

Some related bugs:

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

^^^^ says problem occurs only on cameras with multiple "drives".

https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/258083

^^^^ says the problem is caused by race conditions between apps (e.g. Nautilus, F-spot) trying to lock the device.

Seems like these "Lock Device" issues are longstanding and affect many users.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/331681
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/285682
https://bugzilla.redhat.com/show_bug.cgi?id=533691
Comment 2 GNOME Infrastructure Team 2018-09-21 17:08:45 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/163.