Bug 579424 - gthumb can't import photos because hal mounted the camera's storage
Summary: gthumb can't import photos because hal mounted the camera's storage
Keywords:
Status: CLOSED DUPLICATE of bug 447290
Alias: None
Product: Fedora
Classification: Fedora
Component: gthumb
Version: 12
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-05 05:39 UTC by Michael Styer
Modified: 2010-06-08 12:25 UTC (History)
7 users (show)

Fixed In Version:
Clone Of: 447290
Environment:
Last Closed: 2010-06-08 12:25:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michael Styer 2010-04-05 05:39:26 UTC
+++ This bug was initially created as a clone of Bug #447290 +++

Description of problem:

gthumb cannot import photos from Nikon Coolpix 2100

Version-Release number of selected component (if applicable):
2.10.11

How reproducible:
always

Steps to Reproduce:
1. plug in camera through usb, turn on
2. choose gthumb to import
3.
  
Actual results:

gthumb import dialog shows:

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



Expected results:


This should Just Work.

Additional info:

Immediately after attaching the camera, gvfs-mount gives this info:

22:33:35 [michael@tablet ~]$ gvfs-mount -l -i
Drive(0): NIKON NIKON DSC E2100
  Type: GProxyDrive (GProxyVolumeMonitorGdu)
  ids:
   unix-device: '/dev/sdb'
  themed icons:  [drive-removable-media-usb]  [drive-removable-media]  [drive-removable]  [drive]
  is_media_removable=1
  has_media=1
  is_media_check_automatic=1
  can_poll_for_media=1
  can_eject=1
  can_start=0
  can_stop=1
  start_stop_type=shutdown
  Volume(0): 16 MB Filesystem
    Type: GProxyVolume (GProxyVolumeMonitorGdu)
    ids:
     uuid: '12E0-1D1C'
     unix-device: '/dev/sdb1'
    themed icons:  [drive-removable-media-usb]  [drive-removable-media]  [drive-removable]  [drive]
    can_mount=1
    can_eject=1
    should_automount=1
    Mount(0): 16 MB Filesystem -> file:///media/12E0-1D1C
      Type: GProxyMount (GProxyVolumeMonitorGdu)
      themed icons:  [drive-removable-media-usb]  [drive-removable-media]  [drive-removable]  [drive]
      x_content_types: x-content/image-dcf
      can_unmount=1
      can_eject=1
      is_shadowed=0

After I unmount the camera from Nautilus, gThumb gives the same error. I get this from gvfs-mount:

22:33:41 [michael@tablet ~]$ gvfs-mount -l -i
Drive(0): NIKON NIKON DSC E2100
  Type: GProxyDrive (GProxyVolumeMonitorGdu)
  ids:
   unix-device: '/dev/sdb'
  themed icons:  [drive-removable-media-usb]  [drive-removable-media]  [drive-removable]  [drive]
  is_media_removable=1
  has_media=1
  is_media_check_automatic=1
  can_poll_for_media=1
  can_eject=1
  can_start=0
  can_stop=1
  start_stop_type=shutdown
  Volume(0): 16 MB Filesystem
    Type: GProxyVolume (GProxyVolumeMonitorGdu)
    ids:
     uuid: '12E0-1D1C'
     unix-device: '/dev/sdb1'
    themed icons:  [drive-removable-media-usb]  [drive-removable-media]  [drive-removable]  [drive]
    can_mount=1
    can_eject=1
    should_automount=0

After I eject the camera in Nautlius, I get the same error message, and this from gvfs-mount:

22:34:49 [michael@tablet ~]$ gvfs-mount -l -i
Drive(0): NIKON NIKON DSC E2100
  Type: GProxyDrive (GProxyVolumeMonitorGdu)
  ids:
   unix-device: '/dev/sdb'
  themed icons:  [drive-removable-media-usb]  [drive-removable-media]  [drive-removable]  [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=1
  start_stop_type=shutdown

Finally, after I choose Safely Remove Drive, I get this error message: "An error occurred in the io-library ('Bad parameters'): No error description available" and nothing from gvfs-mount regarding the camera.

Comment 1 Michael J. Chudobiak 2010-06-08 12:25:54 UTC

*** This bug has been marked as a duplicate of bug 447290 ***


Note You need to log in before you can comment on or make changes to this bug.