Access to Samsung fails in file manager

Bug #1803856 reported by Kev Bowring on 2018-11-18
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libmtp (Ubuntu)
Undecided
Unassigned

Bug Description

Trying to connect to smartphone with a file manager and it hangs there.

Seems to work fine in 18.04.1, using a 18.10 live session it fails to work.

journalctl -f output from when I try to connect to the phone gives this:

Nov 18 09:14:03 wolf-wolf gvfsd[1615]: Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Nov 18 09:14:10 wolf-wolf gvfsd[1615]: Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Nov 18 09:14:10 wolf-wolf gvfsd[1615]: Received event PTP_EC_StoreAdded in session 1
Nov 18 09:14:18 wolf-wolf systemd-timesyncd[627]: Synchronized to time server [2001:67c:1560:8003::c7]:123 (ntp.ubuntu.com).
Nov 18 09:14:25 wolf-wolf gvfsd[1615]: LIBMTP PANIC: Could not open session! (Return code 8194)
Nov 18 09:14:25 wolf-wolf gvfsd[1615]: Try to reset the device.
Nov 18 09:14:26 wolf-wolf gvfsd[1615]: Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Nov 18 09:14:29 wolf-wolf gvfsd[1615]: LIBMTP PANIC: Could not open session! (Return code 8194)
Nov 18 09:14:29 wolf-wolf gvfsd[1615]: Try to reset the device.
Nov 18 09:14:30 wolf-wolf gvfsd[1615]: LIBMTP PANIC: Could not open session! (Return code 8194)
Nov 18 09:14:30 wolf-wolf gvfsd[1615]: Try to reset the device.
Nov 18 09:14:30 wolf-wolf gvfsd[1615]: Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Nov 18 09:14:31 wolf-wolf gvfsd[1615]: Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).

mtp-detect gives me this:

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 3, dev 7
Attempting to connect device(s)
LIBMTP PANIC: Could not open session! (Return code 8194)
  Try to reset the device.
Unable to open raw device 0
OK.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gvfs 1.38.1-1ubuntu2
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu14
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Nov 18 09:15:38 2018
InstallationDate: Installed on 2018-08-27 (82 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180824)
SourcePackage: gvfs
UpgradeStatus: Upgraded to disco on 2018-10-14 (34 days ago)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2018-09-21T16:30:23.845026

Kev Bowring (flocculant) wrote :
Kev Bowring (flocculant) on 2018-11-18
description: updated
affects: gvfs (Ubuntu) → libmtp (Ubuntu)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers