[Bug 1044747] Re: mtp filesystem can't mount

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044747

Title:
  mtp filesystem can't mount

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1044747/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1044747] Re: mtp filesystem can't mount

2014-01-07 Thread andrea manconi
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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044747

Title:
  mtp filesystem can't mount

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1044747/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1044747] Re: mtp filesystem can't mount

2013-02-07 Thread Michael Egger
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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044747

Title:
  mtp filesystem can't mount

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1044747/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1044747] Re: mtp filesystem can't mount

2012-11-11 Thread Giovanni Mellini
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=customviewmonth=viewday=forum_name=libmtp-discussstyle=nestedmax_rows=100submit=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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044747

Title:
  mtp filesystem can't mount

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1044747/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1044747] Re: mtp filesystem can't mount

2012-09-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libmtp (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044747

Title:
  mtp filesystem can't mount

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1044747/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1044747] Re: mtp filesystem can't mount

2012-09-01 Thread Typhoe
-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044747

Title:
  mtp filesystem can't mount

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1044747/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1044747] Re: mtp filesystem can't mount

2012-09-01 Thread Typhoe
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 endpoint maxpacket: 512 bytes
   OUT endpoint maxpacket: 512 bytes
   Raw device info:
  Bus location: 3
  Device number: 9
  Device entry info:
 Vendor: Samsung
 Vendor id: 0x04e8
 Product: GT P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 
7.7/10.1/S2/S3/Nexus/Note/Y
 Vendor id: 0x6860
 Device flags: 0x48008107
Device info:
   Manufacturer: samsung
   Model: GT-I9300
   Device version: 1.0
   Serial number: 4df1b2e6569d5f8d
   Vendor extension ID: 0x0006
   Vendor extension description: microsoft.com: 1.0; android.com: 1.0;
   Detected object size: 64 bits
   Extensions:
microsoft.com: 1.0
android.com: 1.0
Supported operations:
   1001: get device info
   1002: Open session
   1003: Close session
   1004: Get storage IDs
   1005: Get storage info
   1006: Get number of objects
   1007: Get object handles
   1008: Get object info
   1009: Get object
   100a: Get thumbnail
   100b: Delete object
   100c: Send object info
   100d: Send object
   1014: Get device property description
   1015: Get device property value
   1016: Set device property value
   1017: Reset device property value
   101b: Get partial object
   9801: Get object properties supported
   9802: Get object property description
   9803: Get object property value
   9804: Set object property value
   9805: Get object property list
   9810: Get object references
   9811: Set object references
   95c1: Unknown (95c1)
   95c2: Unknown (95c2)
   95c3: Unknown (95c3)
   95c4: Unknown (95c4)
   95c5: Unknown (95c5)
Events supported:
   0x4002
   0x4003
   0x4004
   0x4005
Device Properties Supported:
   0xd401: Synchronization Partner
   0xd402: Friendly Device Name
   0x5003: Image Size
Playable File (Object) Types and