[Bug 903422] Re: Ubuntu does not work with Samsung Galaxy phones (needs update to libmtp)
H.-Dirk Schmitt
dirk at computer42.org
Mon Dec 24 16:06:10 UTC 2012
As described in bug #696301 the problem still exists in precise.
I also tested it with backported version from raring for libmtp (1.1.5) and mtpfs (1.1.2)
( --> https://launchpad.net/~dirk-computer42/+archive/c42-edge )
$ 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=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 5
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
** Tags added: quantal raring
** Summary changed:
- Ubuntu does not work with Samsung Galaxy phones (needs update to libmtp)
+ Ubuntu does not work with Samsung Galaxy phones ( Unable to open raw device 0)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to udev in Ubuntu.
https://bugs.launchpad.net/bugs/903422
Title:
Ubuntu does not work with Samsung Galaxy phones ( Unable to open raw
device 0)
Status in GVFS:
In Progress
Status in “gmtp” package in Ubuntu:
Invalid
Status in “libmtp” package in Ubuntu:
Confirmed
Status in “udev” package in Ubuntu:
Invalid
Status in “gmtp” source package in Precise:
Invalid
Status in “libmtp” source package in Precise:
Confirmed
Status in “udev” source package in Precise:
Invalid
Status in “gmtp” source package in Quantal:
Invalid
Status in “libmtp” source package in Quantal:
Confirmed
Status in “udev” source package in Quantal:
Invalid
Bug description:
If your device is not supported please open a new bug specifying:
* device in question (make / model / release)
* output of `mtp-detect` when the device is attached
* output of `lsusb` when the device is attached
This bug will be a catch all for recent Samsung Nexus & Nexus 7, or
please comment what other recent Andorid 4.x devices are affected.
Yes there is a lag in providing support for the most recent devices.
As soon as the fixes are available, SRUs will follow.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/903422/+subscriptions
More information about the foundations-bugs
mailing list