mtpfs : "Transport endpoint is not connected"

Bug #573524 reported by Daniel S.
74
This bug affects 16 people
Affects Status Importance Assigned to Milestone
mtpfs (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: mtpfs

Kubuntu 10.04 "lucid lynx"
mtpfs 0.9-2
libmtp8 1.0.2-1ubuntu1

When I mount my Samsung MP3-Player with mtpfs (sudo mtpfs -o allow_other /media/mp3) and then do ls /media/mp3, the following error appears:
Transport endpoint is not connected.

With Amarok or mtp-tools I can connect and send files.
With Kubuntu 9.10 it worked, after the update to 10.04 it stopped to work.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: mtpfs 0.9-2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic-pae 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun May 2 10:49:22 2010
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: mtpfs

Revision history for this message
Daniel S. (kingdread) wrote :
tags: added: mtpfs
summary: - After mount the message "Transport endpoint is not connected" appears
+ mtpfs : "Transport endpoint is not connected"
Revision history for this message
Fergal Daly (fergal) wrote :

Same with my Creative Zen (041e:4157). Worked fine on hardy but is broken on lucid.

Revision history for this message
Seth (bugs-sehe) wrote :

I concur: it was broken.

I noticed that gnome is 'aggressively' mounting the mtp (don't know whith what). The dialog that asks me what to do, also offers an 'unmount' button.

After doing that, I could 'mtpfs -s -f /tmp/mtp' with success,

HTH

Revision history for this message
Fergal Daly (fergal) wrote :

After much trouble with alternatives (also crashing), I recently just downloaded the source, installed all the necessary dev packages and built it myself and it works just fine.

I still don't understand why though because both version are 0.9 and the packaged version doesn't seem to have any patches. Perhaps the build options are different e.g. optimisation flags.

Revision history for this message
Paul Abrahams (abrahams) wrote :

Same problem here with a Sansa Clip+, but with a twist. The first time I did it the mount worked correctly, but after that I got the transport endpoint error.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mtpfs (Ubuntu):
status: New → Confirmed
Revision history for this message
Asraniel (asraniel) wrote :

Same problem, galaxy s3, kubuntu 12.04

Revision history for this message
Ed Harcourt (edharcourt) wrote :

I was able to get my new Galaxy S3 to connect in Ubuntu 10.04 using the procedure described at

http://www.omgubuntu.co.uk/2011/12/how-to-connect-your-android-ice-cream-sandwich-phone-to-ubuntu-for-file-access

Revision history for this message
Tomáš Hledík (tomas-hledik) wrote :

Same here with nexus7 and ubuntu 12.04.

Revision history for this message
Dingar (cndingar) wrote :

same, galaxy s3, ubuntu 12.04

Revision history for this message
robinharvey (harvey-robin) wrote :

I realise I'm late to the party here, but I thought this may be of interest. Running in debug mode on 16.04 gives some useful output, looks like there's a mutex handling error:

root@centaurus:~# mtpfs -d /mnt
Listing raw device(s)
Device 0 (VID=0bb4 and PID=0c93) is a HTC EVO 4G LTE/One V (ID1).
   Found 1 device(s):
   HTC: EVO 4G LTE/One V (ID1) (0bb4:0c93) @ bus 3, dev 5
Attempting to connect device
Android device detected, assigning default bug flags
Listing File Information on Device with name: (NULL)
FUSE library version: 2.9.4
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.23
flags=0x0003f7fb
max_readahead=0x00020000
   INIT: 7.19
   flags=0x00000010
   max_readahead=0x00020000
   max_write=0x00020000
   max_background=0
   congestion_threshold=0
   unique: 1, success, outsize: 40

unique: 2, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 20357
getattr /
Attempt to unlock mutex that was not locked
Aborted (core dumped)

b3nmore (b3nmore)
tags: added: trusty yakkety
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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