gvfs-gphoto2 mount 4 devices when plugin one camera

Bug #326029 reported by Saivann Carignan
10
Affects Status Importance Assigned to Milestone
gvfs
Fix Released
High
gvfs (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gvfs

In Jaunty alpha4, when I plug my Canon PowerShot A700 Camera (a PTP camera mounted by gphoto2 gvfs backend), the camera appear 3 times (and sometime even 4 times) in nautilus left panel like if I had 3 cameras at the same time.

Each of these 3 devices in nautilus bring to a different folder inside the camera as described here :

Camera 1 : gphoto2://[usb:002,015]/
Camera 2 : gphoto2://[usb:002,015]/store_80000001
Camera 3 : gphoto2://[usb:002,015]/store_00010001

When I unplug the camera, two of the cameras in nautilus does not disappears until I reboot the computer. If I don't insert a SD card in the camera, gphoto2://[usb:002,015]/store_80000001 still appears and give a error message when trying to access it (normal since the card isn't even available).

"gphoto2 --auto-detect" output :
Canon PowerShot A700 (PTP mode) usb:
Canon PowerShot A700 (PTP mode) usb:002,006

lsusb output :
Bus 002 Device 006: ID 04a9:3117 Canon, Inc. PowerShot A700
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x04a9 Canon, Inc.
  idProduct 0x3117 PowerShot A700
  bcdDevice 0.02
  iManufacturer 1 Canon Inc.
  iProduct 2 Canon Digital Camera
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 39
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xc0
      Self Powered
    MaxPower 2mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 3
      bInterfaceClass 6 Imaging
      bInterfaceSubClass 1 Still Image Capture
      bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470)
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x83 EP 3 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0008 1x 8 bytes
        bInterval 10
Device Qualifier (for other device speed):
  bLength 10
  bDescriptorType 6
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  bNumConfigurations 1
Device Status: 0x0001
  Self Powered

Related branches

Revision history for this message
Saivann Carignan (oxmosys) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, could you run gvfs-mount -li and add the log to the bug?

Changed in gvfs:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Saivann Carignan (oxmosys) wrote :

Here is the requested log!

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is an upstream one and should be sent to bugzilla.gnome.org by somebody having the hardware to trigger the bug

Changed in gvfs:
status: Incomplete → New
Revision history for this message
Saivann Carignan (oxmosys) wrote :

Reported upstream, thanks!

Changed in gvfs:
status: New → Triaged
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug has been fixed upstream now

Changed in gvfs:
status: Triaged → Fix Committed
Changed in gvfs:
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gvfs - 1.1.8-0ubuntu1

---------------
gvfs (1.1.8-0ubuntu1) jaunty; urgency=low

  * New upstream version:
    - Fix crashers and leaks (lp: #201519)
    - Handle file:// uris with anchors in gvfs-open
    - fuse: Support ftruncate to the current file size (lp: #234532)
    - escape/unescape hostname part in uris, allowing spaces in e.g. smb domains
    - hal: Fix "No mount object" error on mount
    - Change details of the new .xdg-volume-info file format
    - Fix races in cancellation of gvfs streams
    - Remove debug spew from backends
    - ftp: Fix anonymous login (lp: #334540)
    - gphoto2: Ignore broken storages with no capacity (lp: #326029)
    - Don't globally modify COMP_WORDBREAKS in bash completion script
      (lp: #290784)
    - Don't ask for username when getting ssh key passphrase
  * debian/patches/91_upstream_change_fix_trash_crasher.patch:
    - the change is in the new version

 -- Sebastien Bacher <email address hidden> Tue, 10 Mar 2009 13:02:47 +0100

Changed in gvfs:
status: Fix Committed → Fix Released
Changed in gvfs:
status: New → Fix Released
Changed in gvfs:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.