Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Kio_mtp won't start

  1. #1

    Default Kio_mtp won't start

    I have the latest kio_mtp slave installed, but when I connect my phone (Samsung SII i9100M), the process will not start.

    I can I force kio_mtp to start?

    Thanks

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,291
    Blog Entries
    1

    Default Re: Kio_mtp won't start

    Quote Originally Posted by 8ofspades View Post
    I have the latest kio_mtp slave installed, but when I connect my phone (Samsung SII i9100M), the process will not start.

    I can I force kio_mtp to start?

    Thanks
    1. Have you tried entering 'mtp:/' in the Dolphin location bar?

    2. Look at the device notifier settings. Maybe that needs configuring first.

    3. Attach the phone, then open a terminal and examine
    Code:
    dmesg|tail

  3. #3

    Default Re: Kio_mtp won't start

    1. When I type mtp:/ i get the error "The process for the mtp protocol died unexpectedly."

    2. As far as the device notifier goes, there weren't many options. The only thing I could try is to mount removable media, but that did not help.

    3. This is my dmesg | tail output:

    Code:
    [86515.164783] usb 3-1: usbfs: process 14669 (kio_kamera) did not claim interface 0 before use
    [86515.164788] usb 3-1: usbfs: process 14669 (kio_kamera) did not claim interface 0 before use
    [86515.164792] usb 3-1: usbfs: process 14669 (kio_kamera) did not claim interface 0 before use
    [86565.051337] usb 3-1: USB disconnect, device number 28
    [86571.396061] usb 3-1: new high-speed USB device number 29 using xhci_hcd
    [86571.413210] usb 3-1: New USB device found, idVendor=04e8, idProduct=6860
    [86571.413215] usb 3-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
    [86571.413218] usb 3-1: Product: SAMSUNG_Android
    [86571.413220] usb 3-1: Manufacturer: SAMSUNG
    [86571.413223] usb 3-1: SerialNumber: 0019c2370c356e

  4. #4

    Default Re: Kio_mtp won't start

    So I plugged in my phone, and the kio_mtp process started, however the only thing that changed was my dmesg | tail output.

    Code:
    [130852.815499] usb 3-1: usbfs: process 12581 (kio_kamera) did not claim interface 0 before use                                                                                     
    [130852.815502] usb 3-1: usbfs: process 12581 (kio_kamera) did not claim interface 0 before use                                                                                     
    [130912.926406] usb 3-1: reset high-speed USB device number 29 using xhci_hcd                                                                                                       
    [130912.946039] xhci_hcd 0000:07:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880401d85480                                                                             
    [130912.946045] xhci_hcd 0000:07:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880401d85440                                                                             
    [130912.946048] xhci_hcd 0000:07:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880401d854c0                                                                             
    [131009.631955] usb 3-1: reset high-speed USB device number 29 using xhci_hcd
    [131009.650276] xhci_hcd 0000:07:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880401d85480
    [131009.650281] xhci_hcd 0000:07:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880401d85440
    [131009.650284] xhci_hcd 0000:07:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880401d854c0
    Any clue what this means?

    Thanks

  5. #5
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,291
    Blog Entries
    1

    Default Re: Kio_mtp won't start

    Quote Originally Posted by 8ofspades View Post
    So I plugged in my phone, and the kio_mtp process started, however the only thing that changed was my dmesg | tail output.

    Code:
    [130852.815499] usb 3-1: usbfs: process 12581 (kio_kamera) did not claim interface 0 before use
    [130852.815502] usb 3-1: usbfs: process 12581 (kio_kamera) did not claim interface 0 before use                                                                                     
    [130912.926406] usb 3-1: reset high-speed USB device number 29 using xhci_hcd                                                                                                       
    [130912.946039] xhci_hcd 0000:07:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880401d85480                                                                             
    [130912.946045] xhci_hcd 0000:07:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880401d85440                                                                             
    [130912.946048] xhci_hcd 0000:07:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880401d854c0                                                                             
    [131009.631955] usb 3-1: reset high-speed USB device number 29 using xhci_hcd
    [131009.650276] xhci_hcd 0000:07:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880401d85480
    [131009.650281] xhci_hcd 0000:07:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880401d85440
    [131009.650284] xhci_hcd 0000:07:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880401d854c0
    Any clue what this means?

    Thanks
    Not entirely sure what the problem is, although I note you're using a USB3 intterface, and I wonder whther that is impacting in some way. The following message
    Code:
     usb 3-1: usbfs: process 12581 (kio_kamera) did not claim interface 0 before use
    probably means that kio-kamera attempted to communicate with the phone, but the interface was claimed already. It is not clear by what, so I can only speculate. Pperhaps because the device is appearing as a USB storage device, or maybe because you attempted to communicate with 'mtp:/' instead. Did you try to open Dolphin with 'camera:/' yet?

    For reference, if I connect my iPhone, my KDE notifier detects my phone as 'Portable Media Player' and I have two options for 'Open with File Manager',. One is for 'camera:/', and one is for 'mtp:/'. If I use MTP, then the following is reported
    Code:
    [23489.539078] usb 2-6: usbfs: interface 1 claimed by usbfs while 'kio_mtp' sets config #1
    [23491.512033] usb 2-6: usbfs: interface 1 claimed by usbfs while 'kio_mtp' sets config #1
    and that is the type of message you should be seeing.

  6. #6

    Default Re: Kio_mtp won't start

    I have the same options as you, however when I try to open mtp:/ a popup screen gives me this error:

    "The process for the mtp protocol died unexpectedly."

    I tried plugging it into a usb 2.0 port (instead of 3.0) and I get this more my dmesg | tail output:

    Code:
    [44773.595192] usb 2-1.1: reset high-speed USB device number 24 using ehci_hcd
    [44773.681426] usb 2-1.1: usbfs: process 14566 (kio_mtp) did not claim interface 0 before use
    [44773.681532] usb 2-1.1: usbfs: process 2250 (ThreadWeaver::T) did not claim interface 0 before use
    [44773.681576] usb 2-1.1: usbfs: process 2250 (ThreadWeaver::T) did not claim interface 0 before use
    [44773.681615] usb 2-1.1: usbfs: process 2250 (ThreadWeaver::T) did not claim interface 0 before use
    [44773.681656] usb 2-1.1: usbfs: process 2250 (ThreadWeaver::T) did not claim interface 0 before use
    [44773.681694] usb 2-1.1: usbfs: process 2250 (ThreadWeaver::T) did not claim interface 0 before use
    [44773.682264] usb 2-1.1: usbfs: process 2250 (ThreadWeaver::T) did not claim interface 0 before use
    [44773.682325] usb 2-1.1: usbfs: process 2250 (ThreadWeaver::T) did not claim interface 0 before use
    [44773.682405] usb 2-1.1: usbfs: process 14566 (kio_mtp) did not claim interface 0 before use
    It seems like the device doesn’t actually mount. Is there a way to mount mtp devices?

  7. #7
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,291
    Blog Entries
    1

    Default Re: Kio_mtp won't start

    All I know is that kio-mtp does not always play nicely with particular hardware devices. MTP devices do not get mounted as such, but the MTP KIO plugin is supposed to make the device appear as regular storage device for KDE applications and the Dolphin file manager. The plugin hides the complexities of the underlying communication process, but various hardware manufacturers implement if differently, so there are numerous threads and bug reports discussing connectivity issues with MTP devices. Anyway, there are alternative MTP methods available. The following wiki is a good place to start

    https://wiki.archlinux.org/index.php/Mtp

    FWIW, here's another similar thread

    https://forums.opensuse.org/english/...e-kio_mtp.html

  8. #8

    Default Re: Kio_mtp won't start

    Thanks, I followed the Arch wiki and got it to work using libmtp. It seems that kio_mtp does not support or work with my device, which is strange since kio_mtp seems to be based off of libmtp.

  9. #9
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,291
    Blog Entries
    1

    Default Re: Kio_mtp won't start

    Quote Originally Posted by 8ofspades View Post
    Thanks, I followed the Arch wiki and got it to work using libmtp. It seems that kio_mtp does not support or work with my device, which is strange since kio_mtp seems to be based off of libmtp.
    Glad to read of the progress. I think a KDE bug report is in order. (It's the only way it will get fixed.)

  10. #10

    Default Re: Kio_mtp won't start

    Just found out that if I connect my phone through libmtp, I can browse my phone through kio_mtp.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •