mtp filesystem can't mount

Bug #1044747 reported by Typhoe
68
This bug affects 15 people
Affects Status Importance Assigned to Milestone
libmtp (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hi,

I tried to connect my phone (Samsung GT-I9300 / Galaxy S3 on CyanogenMod 9.1) to my notebook.

Quantal doesn't seem to be able to mount the 2 filesystems availble on the phone (internal storage and external one, microSD).

In Nautilus, the mount points appear and disappear every few seconds.

I don'tget this behaviour on an other Quantal PC, so maybe it's due to the USB3 available on this notebook (the other PC is USB2 only, and on it, I can connect my phone).

Regards.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: mtp-tools 1.1.4-1
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
CheckboxSubmission: 07c1b2f1302af9a0aa8bf3fa10951319
CheckboxSystem: 4c773cd91921f9618cc2f1893bc1a87a
Date: Sat Sep 1 17:56:32 2012
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.3)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: libmtp
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Typhoe (spamistrash) wrote :
Revision history for this message
Typhoe (spamistrash) wrote :
Download full text (7.2 KiB)

In syslog, these lines are repeted again and again:

Sep 1 18:07:31 g75vw kernel: [ 1075.064067] usb 3-2.1.2: new high-speed USB device number 108 using xhci_hcd
Sep 1 18:07:31 g75vw kernel: [ 1075.080955] usb 3-2.1.2: New USB device found, idVendor=04e8, idProduct=6860
Sep 1 18:07:31 g75vw kernel: [ 1075.080962] usb 3-2.1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Sep 1 18:07:31 g75vw kernel: [ 1075.080966] usb 3-2.1.2: Product: GT-I9300
Sep 1 18:07:31 g75vw kernel: [ 1075.080969] usb 3-2.1.2: Manufacturer: samsung
Sep 1 18:07:31 g75vw kernel: [ 1075.080971] usb 3-2.1.2: SerialNumber: 4df1b2e6569d5f8d
Sep 1 18:07:31 g75vw kernel: [ 1075.081206] usb 3-2.1.2: ep 0x82 - rounding interval to 32768 microframes, ep desc says 0 microframes
Sep 1 18:07:31 g75vw kernel: [ 1075.081214] usb 3-2.1.2: ep 0x4 - rounding interval to 32768 microframes, ep desc says 0 microframes
Sep 1 18:07:31 g75vw kernel: [ 1075.081222] usb 3-2.1.2: ep 0x85 - rounding interval to 32768 microframes, ep desc says 0 microframes
Sep 1 18:07:31 g75vw kernel: [ 1075.081228] usb 3-2.1.2: ep 0x7 - rounding interval to 32768 microframes, ep desc says 0 microframes
Sep 1 18:07:31 g75vw kernel: [ 1075.122317] usb 3-2.1.2: USB disconnect, device number 108

mtp-detect doesn't always detect my phone:

typhoe@g75vw:~$ sudo mtp-detect
libmtp version: 1.1.4

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 7.7/10.1/S2/S3/Nexus/Note/Y.
   Found 1 device(s):
   Samsung: GT P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 7.7/10.1/S2/S3/Nexus/Note/Y (04e8:6860) @ bus 3, dev 90
Attempting to connect device(s)
ignoring usb_claim_interface = -99PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
usb_clear_halt() on IN endpoint: No such device
usb_clear_halt() on OUT endpoint: No such device
usb_clear_halt() on INTERRUPT endpoint: No such device
usb_open(): No such device
LIBMTP PANIC: Could not init USB on second attempt
Unable to open raw device 0
OK.

then again, the same command:

typhoe@g75vw:~$ sudo mtp-detect
libmtp version: 1.1.4

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 7.7/10.1/S2/S3/Nexus/Note/Y.
   Found 1 device(s):
   Samsung: GT P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 7.7/10.1/S2/S3/Nexus/Note/Y (04e8:6860) @ bus 3, dev 9
Attempting to connect device(s)
Android device detected, assigning default bug flags
Error 7: Found a bad handle, trying to ignore it.
Error 7: Found a bad handle, trying to ignore it.
Error 7: Found a bad handle, trying to ignore it.
< repeat for more than 300 times >
Error 7: Found a bad handle, trying to ignore it.
Error 2: PTP Layer error 02ff: get_handles_recursively(): could not get object handles.
Error 2: Error 02ff: PTP: I/O error
USB low-level info:
   Interface has a kernel driver attached.
   bcdUSB: 512
   bDeviceClass: 0
   bDeviceSubClass: 0
   bDeviceProtocol: 0
   idVendor: 04e8
   idProduct: 6860
   IN...

Read more...

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

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

Changed in libmtp (Ubuntu):
status: New → Confirmed
Revision history for this message
Giovanni Mellini (merlos) wrote :

Hi all
I fount this post where and seems that 1,1.5 version fix the issue (1.1.5 is in 13.04)
http://sourceforge.net/mailarchive/forum.php?set=custom&viewmonth=&viewday=&forum_name=libmtp-discuss&style=nested&max_rows=100&submit=Change+View

I compiled from source and installed in 12.10 libmpt1-1.5 and now I can mount my Galaxy S2 storage (so I can copy files) but I still have problems with Openshot and Rhythmbox.
I think that I should try with 13.04 and see if it works fine

Ciao
Giovanni

Revision history for this message
Michael Egger (michael-egger) wrote :

Hi
I have the same problem here with Galaxy S2 (I9100) on Ubuntu 13.04.
Using Cyanogenmod 9.1 (android 4.0.4) with kernel 3.0.32-CM

Nautilus shows up the android device, but i can't mount it.

$ mtp-detect
Error: Unable to open ~/.mtpz-data for reading.
libmtp version: 1.1.5

Listing raw device(s)
Device 0 (VID=04e8 and PID=685e) is a Samsung Galaxy Y.
   Found 1 device(s):
   Samsung: Galaxy Y (04e8:685e) @ bus 2, dev 6
Attempting to connect device(s)
LIBMTP PANIC: Unable to find interface & endpoints of device
Unable to open raw device 0
OK.

regards
Michael

Revision history for this message
andrea manconi (andymnc) wrote :

with 1.1.6 (in 13.10) and with USB-debug ON (on android -> settings -> developer ), it seems to solve at least the errors as per post #2

Revision history for this message
poikiloid (efelthauser) wrote :

I have this problem in Kubuntu 14.4's Dolphin and Konqueror file browsers, even with USB-debugging on.

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.