Comment 3 for bug 481528

Revision history for this message
Martin Pitt (pitti) wrote : Re: Automounted digital camera mounts with incorrect name and does not create camera icon on desktop in Karmic as it did in Jaunty

I reproduced this with a "fake" mass storage camera by adding a DCIM/ folder with some images to my USB stick. I confirm that gvfs detects the MIME type just fine, but doesn't set a camera icon:

  Volume(0): PittiTest
    Type: GProxyVolume (GProxyVolumeMonitorGdu)
    ids:
     uuid: '49C5-8913'
     unix-device: '/dev/sdb1'
     label: 'PittiTest'
    themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive]
    can_mount=1
    can_eject=1
    should_automount=1
    Mount(0): PittiTest -> file:///media/PittiTest
      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

Now, there are devices (like my mobile phone) which have more than one MIME type, so for those a camera icon isn't appropriate. But if the only MIME type that we detect is x-content/image-dcf, then gvfs should indeed set a camera icon.

As for the "no icon on desktop", this is because your camera wasn't automounted after all; your gvfs-mount output has "should_automount=0". Did you already have it plugged in when starting the GNOME session? If so, that's bug 472937.