MTP device fails to mount

[Ken Sharp]

Yesterday I could access my Motorola Moto G (2013) Android phone via MTP (mtp-probe). Today I cannot.

May 6 16:44:27 kernel: [ 613.641980] usb 1-3: USB disconnect, device number 5
May 6 16:44:30 kernel: [ 616.504041] usb 1-3: new high-speed USB device number 6 using ehci-pci
May 6 16:44:30 kernel: [ 616.637429] usb 1-3: New USB device found, idVendor=22b8, idProduct=2e82
May 6 16:44:30 kernel: [ 616.637437] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 6 16:44:30 kernel: [ 616.637442] usb 1-3: Product: XT1039
May 6 16:44:30 kernel: [ 616.637445] usb 1-3: Manufacturer: motorola
May 6 16:44:30 mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-3"
May 6 16:44:30 mtp-probe: bus: 1, device: 6 was an MTP device

*Was* an MTP device?

This may be due to libmtp* but they were not upgraded yesterday.

Start-Date: 2015-05-05 13:54:40
Commandline: /usr/bin/apt-get dist-upgrade
Install: libphysfs1:i386 (2.0.2-5, automatic)
Upgrade: update-manager:i386 (0.156.14.18, 0.156.14.19), gvfs-fuse:i386 (1.12.1-0ubuntu1.2ppa8~precise3, 1.12.1-0ubuntu1.3), hedgewars-data:i386 (0.9.21.1-4~ubuntu12.04.1, 0.9.21.1-6~precise1), update-manager-core:i386 (0.156.14.18, 0.156.14.19), gvfs-libs:i386 (1.12.1-0ubuntu1.2ppa8~precise3, 1.12.1-0ubuntu1.3), dosfstools:i386 (3.0.12-1ubuntu1.1, 3.0.12-1ubuntu1.2), gvfs-bin:i386 (1.12.1-0ubuntu1.2ppa8~precise3, 1.12.1-0ubuntu1.3), gvfs-common:i386 (1.12.1-0ubuntu1.2ppa8~precise3, 1.12.1-0ubuntu1.3), linux-libc-dev:i386 (3.2.0-82.119, 3.2.0-83.120), gvfs-daemons:i386 (1.12.1-0ubuntu1.2ppa8~precise3, 1.12.1-0ubuntu1.3), libcurl3-gnutls:i386 (7.22.0-3ubuntu4.12, 7.22.0-3ubuntu4.14), hedgewars:i386 (0.9.17-1, 0.9.21.1-6~precise1), libcurl3:i386 (7.22.0-3ubuntu4.12, 7.22.0-3ubuntu4.14), libxml-libxml-perl:i386 (1.89+dfsg-1, 1.89+dfsg-1ubuntu0.1), usb-creator-gtk:i386 (0.2.38.3ubuntu0.1, 0.2.38.3ubuntu0.2), usb-creator-common:i386 (0.2.38.3ubuntu0.1, 0.2.38.3ubuntu0.2), curl:i386 (7.22.0-3ubuntu4.12, 7.22.0-3ubuntu4.14), linux-doc:i386 (3.2.0-82.119, 3.2.0-83.120), google-chrome-stable:i386 (42.0.2311.90-1, 42.0.2311.135-1), gvfs:i386 (1.12.1-0ubuntu1.2ppa8~precise3, 1.12.1-0ubuntu1.3), gvfs-backends:i386 (1.12.1-0ubuntu1.2ppa8~precise3, 1.12.1-0ubuntu1.3), libcurl3-nss:i386 (7.22.0-3ubuntu4.12, 7.22.0-3ubuntu4.14)
End-Date: 2015-05-05 13:58:52

I tried a downgrade and a purge and downgrade, and multiple reboots but it made no difference.

Start-Date: 2015-05-06 16:40:49
Commandline: /usr/bin/apt-get purge gvfs/precise-updates gvfs-fuse/precise-updates gvfs-bin/precise-updates
Purge: nautilus:i386 (3.4.2-0ubuntu9), gvfs-fuse:i386 (1.12.1-0ubuntu1.2), gvfs-bin:i386 (1.12.1-0ubuntu1.2), nautilus-share:i386 (0.7.3-1ubuntu2), gnome-applets:i386 (3.4.1-0ubuntu1), brasero:i386 (3.4.1-0ubuntu1.1), gvfs:i386 (1.12.1-0ubuntu1.2), gnome-session:i386 (3.2.1-0ubuntu8), nautilus-sendto:i386 (3.0.1-2ubuntu2)
End-Date: 2015-05-06 16:41:26

Start-Date: 2015-05-06 16:42:45
Commandline: /usr/bin/apt-get install gvfs/precise-updates gvfs-fuse/precise-updates gvfs-bin/precise-updates
Install: gvfs-fuse:i386 (1.12.1-0ubuntu1.2), gvfs-bin:i386 (1.12.1-0ubuntu1.2), gvfs:i386 (1.12.1-0ubuntu1.2)
End-Date: 2015-05-06 16:42:49

Nothing has changed on the phone, but I tried restarting a couple of times anyway just in case.

I can no longer access the files on my phone.

I'll try Trusty and update.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gvfs-common 1.12.1-0ubuntu1.3
ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
Uname: Linux 3.11.0-26-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: i386
Date: Wed May 6 16:07:53 2015
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gvfs
UpgradeStatus: Upgraded to precise on 2014-12-07 (150 days ago)

[Ken Sharp (kennybobs)]

The 14.04.2 live CD fails for other reasons but with an "apt-get upgrade" to 1.1.6-20-g1b9f164-1ubuntu2 it starts working, so Trusty does not appear to have this problem.