[kio-extras] [Bug 415241] Trouble opening an MTP device

[Enrico Tagliavini]

https://bugs.kde.org/show_bug.cgi?id=415241

Enrico Tagliavini <enrico.tagliavini at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
                 CC|                            |enrico.tagliavini at gmail.com
             Status|REPORTED                    |CONFIRMED

--- Comment #5 from Enrico Tagliavini <enrico.tagliavini at gmail.com> ---
This looks like a problem possibly generated in the KIO module.

Running mtp-detect:

$ mtp-detect
libmtp version: 1.1.16

Listing raw device(s)
Device 0 (VID=2a70 and PID=f003) is a OnePlus OnePlus 2 A2005.
   Found 1 device(s):
   OnePlus: OnePlus 2 A2005 (2a70:f003) @ bus 1, dev 17
Attempting to connect device(s)
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to
initialize device
Unable to open raw device 0
OK.


Running the android file transfer utrility claims the device is already in use:

# aft-mtp-mount $HOME/mtpfs/
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
Device::Find failed:Device is already used by another process
connect failed: no MTP device found


stracing mtp-detect shows
ioctl(3, USBDEVFS_CLAIMINTERFACE, 0x7ffd33ff178c) = -1 EBUSY (Device or
resource busy)


so it looks like the KDE kio module is locking the USB device and not releasing
it at some point early right after the USB cable is connected


killall kiod5, seems to help, after running it the MTP file system is
accessible with any libmtp based software (e.g. mtp-detect, gvfs-mtp, jmtpfs
and so on) except the KDE one. Trying to access the phone with a KIO based
application causes the device to be locked again and kiod5 needs to be killed
again to make it accessible.

-- 
You are receiving this mail because:
You are on the CC list for the bug.