desktop-packages team mailing list archive

[Roger Lipscombe <roger@xxxxxxxxxxxxxxxx>]

I'm having the same problem with both my 2012 Nexus 7 and my HTC One M8.

If I connect the device, I get the error message "Unable to mount
Android Phone: Unable to open MTP device '[usb:005,120]'" for my HTC One
M8. The message changes to "Unable to mount Nexus 7" when I plug the
Nexus 7 in. The '[usb:005,120]' identifier also changes.

(All of the following was done with the HTC phone...)

But here's the interesting part: if I run "lsusb" with the error message
on the screen, the device is detected one ID higher. Right now, "lsusb"
is showing "Bus 005 Device 121: ID 0bb4:061a HTC (High Tech Computer
Corp.)" for the phone. Using "ls -l /dev/bus/usb/X/Y" gives:

$ ls -l /dev/bus/usb/005/120
ls: cannot access /dev/bus/usb/005/120: No such file or directory
$ ls -l /dev/bus/usb/005/121
crw-rw----+ 1 root audio 189, 632 Jan 15 20:59 /dev/bus/usb/005/121

dmesg gives the following:

$ dmesg
[ 3202.628185] usb 5-2: new high-speed USB device number 122 using xhci_hcd
[ 3202.650762] usb 5-2: New USB device found, idVendor=0bb4, idProduct=061a
[ 3202.650769] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3202.650773] usb 5-2: Product: Android Phone
[ 3202.650777] usb 5-2: Manufacturer: HTC
[ 3202.653957] usb-storage 5-2:1.2: USB Mass Storage device detected
[ 3202.654251] scsi11 : usb-storage 5-2:1.2
[ 3202.796549] usb 5-2: USB disconnect, device number 122
[ 3203.576177] usb 5-2: new high-speed USB device number 123 using xhci_hcd
[ 3203.598656] usb 5-2: New USB device found, idVendor=0bb4, idProduct=061a
[ 3203.598663] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3203.598667] usb 5-2: Product: Android Phone
[ 3203.598670] usb 5-2: Manufacturer: HTC

(I've deleted the 'SerialNumber' lines; I don't know if they're
sensitive or not)

Another time I tried to reproduce the dmesg output, I got:

[ 3271.638047] xhci_hcd 0000:08:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88056c19e040
[ 3271.638049] xhci_hcd 0000:08:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88056c19e000
[ 3271.638051] xhci_hcd 0000:08:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88057ad043c0
[ 3271.638052] xhci_hcd 0000:08:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88056c19e080
[ 3271.638053] xhci_hcd 0000:08:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88057ad041c0
[ 3271.638055] xhci_hcd 0000:08:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88057ad04380
[ 3271.638056] xhci_hcd 0000:08:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff88057ad04180

I don't know if that's related. It doesn't always appear in dmesg.

I'm actually using Linux Mint, as follows:

$ uname -a
Linux roger-pc 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID:	LinuxMint
Description:	Linux Mint 17 Qiana
Release:	17
Codename:	qiana
$ lsb_release -au
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04 LTS
Release:	14.04
Codename:	trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1314556

Title:
  Unable to mount Android MTP device

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  I have the same problem on 3 computers with 14.04:

  So I tried,
   mtp-detect 
  Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6

  Listing raw device(s)
  Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
     Found 1 device(s):
     Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10
  Attempting to connect device(s)
  ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
  LIBMTP libusb: Attempt to reset device
  inep: usb_get_endpoint_status(): Resource temporarily unavailable
  outep: usb_get_endpoint_status(): Device or resource busy
  ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt
  Unable to open raw device 0
  OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs-backends 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 30 11:18:12 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfs-mtp-volume-monitor
  InstallationDate: Installed on 2013-02-12 (441 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   XDG_RUNTIME_DIR=<set>
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to trusty on 2014-04-02 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+subscriptions