Ubuntu
linux package

automounting MTP or USB storage devices no longer works.

Bug #1789518 reported by b on 2018-08-28

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

After upgrading from xenial to bionic, USB (both MTP and mass storage) devices will not automount.

syslog shows the usb device is found and recognized as a storage device:

Aug 28 16:49:18 insitu kernel: [ 4412.072025] usb 1-8: new high-speed USB device number 18 using ehci-pci
Aug 28 16:49:19 insitu kernel: [ 4412.229198] usb 1-8: New USB device found, idVendor=0421, idProduct=01c7
Aug 28 16:49:19 insitu kernel: [ 4412.229202] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 28 16:49:19 insitu kernel: [ 4412.229204] usb 1-8: Product: N900 (Storage Mode)
Aug 28 16:49:19 insitu kernel: [ 4412.229206] usb 1-8: Manufacturer: Nokia
Aug 28 16:49:19 insitu kernel: [ 4412.229211] usb 1-8: SerialNumber: 372041756775
Aug 28 16:49:19 insitu kernel: [ 4412.231642] usb-storage 1-8:1.0: USB Mass Storage device detected
Aug 28 16:49:19 insitu kernel: [ 4412.233887] scsi host7: usb-storage 1-8:1.0
Aug 28 16:49:19 insitu mtp-probe: checking bus 1, device 18: "/sys/devices/pci0000:00/0000:00:10.4/usb1/1-8"
Aug 28 16:49:19 insitu mtp-probe: bus: 1, device: 18 was not an MTP device
Aug 28 16:49:19 insitu upowerd[1485]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:10.4/usb1/1-8/1-8:1.0
Aug 28 16:49:19 insitu upowerd[1485]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:10.4/usb1/1-8
Aug 28 16:49:20 insitu kernel: [ 4413.251860] scsi 7:0:0:0: Direct-Access Nokia N900 031 PQ: 0 ANSI: 2
Aug 28 16:49:20 insitu kernel: [ 4413.252743] scsi 7:0:0:1: Direct-Access Nokia N900 031 PQ: 0 ANSI: 2
Aug 28 16:49:20 insitu kernel: [ 4413.254638] sd 7:0:0:0: Attached scsi generic sg3 type 0
Aug 28 16:49:20 insitu kernel: [ 4413.254946] sd 7:0:0:1: Attached scsi generic sg4 type 0
Aug 28 16:49:20 insitu kernel: [ 4413.255201] sd 7:0:0:0: Power-on or device reset occurred
Aug 28 16:49:20 insitu kernel: [ 4413.255822] sd 7:0:0:1: Power-on or device reset occurred
Aug 28 16:49:20 insitu kernel: [ 4413.260481] sd 7:0:0:1: [sdd] Attached SCSI removable disk
Aug 28 16:49:20 insitu kernel: [ 4413.261109] sd 7:0:0:0: [sdc] Attached SCSI removable disk
Aug 28 16:49:26 insitu kernel: [ 4419.523221] sd 7:0:0:0: [sdc] 56631296 512-byte logical blocks: (29.0 GB/27.0 GiB)
Aug 28 16:49:26 insitu kernel: [ 4419.523952] sd 7:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug 28 16:49:26 insitu kernel: [ 4419.719652] sdc:

sdc is never mounted; I can mount it manually with:

sudo mount /dev/sdc /mnt/

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-32-generic 4.15.0-32.35
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: bbogart 1490 F.... pulseaudio
CurrentDesktop: XFCE
Date: Tue Aug 28 16:45:48 2018
GvfsMonitorError:
This tool has been deprecated, use 'gio mount' instead.
See 'gio help mount' for more info.
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HibernationDevice: RESUME=UUID=13df1544-3ecd-4a0b-bea6-347f3f27871d
HotplugNewDevices:

HotplugNewMounts:

InstallationDate: Installed on 2010-11-05 (2853 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
IwConfig:
lo no wireless extensions.

eth0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=0ab4bde0-8376-4cbe-9bc0-af6c3a7936bd ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-32-generic N/A
linux-backports-modules-4.15.0-32-generic N/A
linux-firmware 1.173.1
RfKill:

SourcePackage: linux
Symptom: storage
UpgradeStatus: Upgraded to bionic on 2018-08-16 (12 days ago)
dmi.bios.date: 10/06/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1015.002
dmi.board.name: A8V Deluxe
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1015.002:bd10/06/2005:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnA8VDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Tags:

Revision history for this message

b (ben-ekran) wrote on 2018-08-28:

AlsaInfo.txt Edit (23.0 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (468 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (69.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.7 KiB, text/plain; charset="utf-8")
HookError_medibuntu.txt Edit (305 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (17.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (834 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (781 bytes, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (781 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (115 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.0 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (23.3 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (148.5 KiB, text/plain; charset="utf-8")
UdevMonitorLog.txt Edit (24.9 KiB, text/plain; charset="utf-8")
UdisksMonitorLog.txt Edit (6.2 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (92.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2018-08-29: Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2018-08-29:

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc1/

Changed in linux (Ubuntu):
importance:	Undecided → Medium
status:	Confirmed → Incomplete

Revision history for this message

b (ben-ekran) wrote on 2018-08-29:

Issue persists in linux 4.19.0-041900rc1-generic

tags:	added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

b (ben-ekran) on 2018-08-29

Changed in linux (Ubuntu):
status:	Confirmed → Invalid
status:	Invalid → Confirmed

Revision history for this message

b (ben-ekran) wrote on 2018-08-29:

Download full text (6.6 KiB)

Update: I can now see that USB storage devices are automounted. This was resolved by installing gvfs:

sudo apt-get install gvfs
[sudo] password for bbogart:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  gvfs-daemons gvfs-libs
Suggested packages:
  gvfs-backends
The following NEW packages will be installed:
  gvfs gvfs-daemons gvfs-libs
0 upgraded, 3 newly installed, 0 to remove and 41 not upgraded.
Need to get 323 kB of archives.
After this operation, 1,305 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://mirrors.accretive-networks.net/ubuntu bionic-updates/main amd64 gvfs-libs amd64 1.36.1-0ubuntu1.1 [95.1 kB]
Get:2 http://mirrors.accretive-networks.net/ubuntu bionic-updates/main amd64 gvfs-daemons amd64 1.36.1-0ubuntu1.1 [116 kB]
Get:3 http://mirrors.accretive-networks.net/ubuntu bionic-updates/main amd64 gvfs amd64 1.36.1-0ubuntu1.1 [111 kB]
Fetched 323 kB in 1s (393 kB/s)
Selecting previously unselected package gvfs-libs:amd64.
(Reading database ... 333054 files and directories currently installed.)
Preparing to unpack .../gvfs-libs_1.36.1-0ubuntu1.1_amd64.deb ...
Unpacking gvfs-libs:amd64 (1.36.1-0ubuntu1.1) ...
Selecting previously unselected package gvfs-daemons.
Preparing to unpack .../gvfs-daemons_1.36.1-0ubuntu1.1_amd64.deb ...
Unpacking gvfs-daemons (1.36.1-0ubuntu1.1) ...
Selecting previously unselected package gvfs:amd64.
Preparing to unpack .../gvfs_1.36.1-0ubuntu1.1_amd64.deb ...
Unpacking gvfs:amd64 (1.36.1-0ubuntu1.1) ...
Processing triggers for libglib2.0-0:amd64 (2.56.1-2ubuntu1) ...
Setting up gvfs-libs:amd64 (1.36.1-0ubuntu1.1) ...
Setting up gvfs-daemons (1.36.1-0ubuntu1.1) ...
Setting up gvfs:amd64 (1.36.1-0ubuntu1.1) ...

It is unclear to me why gvfs was not installed during the do-release-upgrade. Is there a way I can file a bug against do-release-upgrade?

MTP USB mounting still does not work:

Update: I can now see that USB storage devices are automounted. This was resolved by installing gvfs:

sudo apt-get install gvfs
[sudo] password for bbogart: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  gvfs-daemons gvfs-libs
Suggested packages:
  gvfs-backends
The following NEW packages will be installed:
  gvfs gvfs-daemons gvfs-libs
0 upgraded, 3 newly installed, 0 to remove and 41 not upgraded.
Need to get 323 kB of archives.
After this operation, 1,305 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://mirrors.accretive-networks.net/ubuntu bionic-updates/main amd64 gvfs-libs amd64 1.36.1-0ubuntu1.1 [95.1 kB]
Get:2 http://mirrors.accretive-networks.net/ubuntu bionic-updates/main amd64 gvfs-daemons amd64 1.36.1-0ubuntu1.1 [116 kB]
Get:3 http://mirrors.accretive-networks.net/ubuntu bionic-updates/main amd64 gvfs amd64 1.36.1-0ubuntu1.1 [111 kB]
Fetched 323 kB in 1s (393 kB/s)
Selecting previously unselected package gvfs-libs:amd64.
(Reading database ... 333054 files and directories currently installed.)
Preparing to unpack .../gvfs-libs_1.36.1-0ubuntu1.1_amd64.deb ...
Unpacking gvfs-libs:amd64 (1.36.1-0ubuntu1.1) ...
Selecting previously unselected package gvfs-daemons.
Preparing to unpack .../gvfs-daemons_1.36.1-0ubuntu1.1_amd64.deb ...
Unpacking gvfs-daemons (1.36.1-0ubuntu1.1) ...
Selecting previously unselected package gvfs:amd64.
Preparing to unpack .../gvfs_1.36.1-0ubuntu1.1_amd64.deb ...
Unpacking gvfs:amd64 (1.36.1-0ubuntu1.1) ...
Processing triggers for libglib2.0-0:amd64 (2.56.1-2ubuntu1) ...
Setting up gvfs-libs:amd64 (1.36.1-0ubuntu1.1) ...
Setting up gvfs-daemons (1.36.1-0ubuntu1.1) ...
Setting up gvfs:amd64 (1.36.1-0ubuntu1.1) ...

It is unclear to me why gvfs was not installed during the do-release-upgrade. Is there a way I can file a bug against do-release-upgrade?

MTP USB mounting still does not work:

Aug 29 10:37:26 insitu kernel: [ 3013.040023] usb 1-8: new high-speed USB device number 10 using ehci-pci
Aug 29 10:37:26 insitu kernel: [ 3013.198520] usb 1-8: New USB device found, idVendor=04e8, idProduct=6860
Aug 29 10:37:26 insitu kernel: [ 3013.198524] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 29 10:37:26 insitu kernel: [ 3013.198526] usb 1-8: Product: SAMSUNG_Android
Aug 29 10:37:26 insitu kernel: [ 3013.198527] usb 1-8: Manufacturer: SAMSUNG
Aug 29 10:37:26 insitu kernel: [ 3013.198529] usb 1-8: SerialNumber: dd8450b3050d150f
Aug 29 10:37:26 insitu upowerd[1596]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:10.4/usb1/1-8
Aug 29 10:37:26 insitu dbus-daemon[1442]: [session uid=1000 pid=1442] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.166' (uid=1000 pid=5547 comm="thunar-volman --device-added /sys/devices/pci0000:" label="unconfined")
Aug 29 10:37:26 insitu systemd[1412]: Starting Virtual filesystem service - digital camera monitor...
Aug 29 10:37:27 insitu upowerd[1596]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:10.4/usb1/1-8/1-8:1.0
Aug 29 10:37:27 insitu upowerd[1596]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:10.4/usb1/1-8/1-8:1.0
Aug 29 10:37:27 insitu dbus-daemon[1442]: [session uid=1000 pid=1442] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Aug 29 10:37:27 insitu systemd[1412]: Started Virtual filesystem service - digital camera monitor.
Aug 29 10:37:27 insitu dbus-daemon[1442]: [session uid=1000 pid=1442] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.166' (uid=1000 pid=5547 comm="thunar-volman --device-added /sys/devices/pci0000:" label="unconfined")
Aug 29 10:37:27 insitu systemd[1412]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Aug 29 10:37:27 insitu dbus-daemon[1442]: [session uid=1000 pid=1442] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Aug 29 10:37:27 insitu systemd[1412]: Started Virtual filesystem service - Media Transfer Protocol monitor.
Aug 29 10:37:27 insitu dbus-daemon[1442]: [session uid=1000 pid=1442] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.166' (uid=1000 pid=5547 comm="thunar-volman --device-added /sys/devices/pci0000:" label="unconfined")
Aug 29 10:37:27 insitu systemd[1412]: Starting Virtual filesystem service - Apple File Conduit monitor...
Aug 29 10:37:27 insitu gvfs-afc-volume-monitor[5563]: Volume monitor alive
Aug 29 10:37:27 insitu dbus-daemon[1442]: [session uid=1000 pid=1442] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Aug 29 10:37:27 insitu systemd[1412]: Started Virtual filesystem service - Apple File Conduit monitor.
Aug 29 10:37:27 insitu dbus-daemon[1442]: [session uid=1000 pid=1442] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.166' (uid=1000 pid=5547 comm="thunar-volman --device-added /sys/devices/pci0000:" label="unconfined")
Aug 29 10:37:27 insitu systemd[1412]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
Aug 29 10:37:27 insitu dbus-daemon[1442]: [session uid=1000 pid=1442] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Aug 29 10:37:27 insitu systemd[1412]: Started Virtual filesystem service - GNOME Online Accounts monitor.
Aug 29 10:37:30 insitu kernel: [ 3017.125447] usb 1-8: USB disconnect, device number 10
Aug 29 10:37:30 insitu upowerd[1596]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:10.4/usb1/1-8
Aug 29 10:37:30 insitu kernel: [ 3017.472017] usb 1-8: new high-speed USB device number 11 using ehci-pci
Aug 29 10:37:30 insitu kernel: [ 3017.633007] usb 1-8: New USB device found, idVendor=04e8, idProduct=6860
Aug 29 10:37:30 insitu kernel: [ 3017.633012] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 29 10:37:30 insitu kernel: [ 3017.633013] usb 1-8: Product: SAMSUNG_Android
Aug 29 10:37:30 insitu kernel: [ 3017.633015] usb 1-8: Manufacturer: SAMSUNG
Aug 29 10:37:30 insitu kernel: [ 3017.633017] usb 1-8: SerialNumber: dd8450b3050d150f
Aug 29 10:37:30 insitu upowerd[1596]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:10.4/usb1/1-8

I can't seem to mount manually:

$ mtpfs mnt
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 11
Attempting to connect device
Listing File Information on Device with name: Tabby

$ ls mnt 
ls: cannot access 'mnt': Transport endpoint is not connected

Revision history for this message

b (ben-ekran) wrote on 2018-10-05:

Tried again today and MTP automounts fine. No idea what was wrong before.

Changed in linux (Ubuntu):
status:	Confirmed → Invalid

Brad Figg (brad-figg) on 2019-07-24

tags:

added: cscc

Revision history for this message

utkatubuntu (just-utkarsh) wrote on 2020-07-12:

getting this now unable to mount any USB device.

lsusb shows the device but not lsblk

Jul 13 00:49:26 kernel: [14879.503628] usb 2-3.3: new high-speed USB device number 12 using xhci_hcd
Jul 13 00:49:26 kernel: [14879.612502] usb 2-3.3: New USB device found, idVendor=0781, idProduct=5590
Jul 13 00:49:26 kernel: [14879.612510] usb 2-3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 13 00:49:26 kernel: [14879.612514] usb 2-3.3: Product: Ultra
Jul 13 00:49:26 kernel: [14879.612518] usb 2-3.3: Manufacturer: SanDisk
Jul 13 00:49:26 kernel: [14879.612522] usb 2-3.3: SerialNumber: 4C530001170213117083
Jul 13 00:49:26 mtp-probe: checking bus 2, device 12: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.3"
Jul 13 00:49:26 mtp-probe: bus: 2, device: 12 was not an MTP device
Jul 13 00:49:26 upowerd[2078]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.3

Revision history for this message

You-Sheng Yang (vicamo) wrote on 2020-07-13:

@utkatubuntu that mtp-probe error message indicates your device might just doesn't declare necessary interface for MTP. Please file a new bug if you're still interested in it, and please attach `sudo lsusb -v -v -v` there.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntulinux package

automounting MTP or USB storage devices no longer works.

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package