Bug 379680

Please run 'kdeinit5' in a terminal, try again and copy here any relevant output about mtp.

If you can provide the information requested in comment #1, please add it.

To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment.

Created attachment 106085 [details]
attachment-28033-0.html

Have run kdeinit5 nothing relevant information came up with that. Best
guess right now it that there needs to be a look into the protocols that
samsung lg and other brands are using for their devices. Since they cater
to Microsoft they are using something the runs on a Microsoft driver and or
protocol.

On Jun 13, 2017 11:09 AM, "Christoph Feck" <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=379680
>
> --- Comment #3 from Christoph Feck <cfeck@kde.org> ---
> To further investigate this issue, KDE developers need the information
> requested in comment #1. If you can provide it, or need help with finding
> that
> information, please add a comment.
>
> --
> You are receiving this mail because:
> You reported the bug.

Thanks for the update; maybe someone has other ideas to debug the issue.

A few logs, while trying to browse a Samsung Galaxy S5

Note: VID and PID have been edited to avoid any privacy problem

$ Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
ERROR: Could not close session!
inep: usb_get_endpoint_status(): Device or resource busy
outep: usb_get_endpoint_status(): Device or resource busy
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
ERROR: Could not close session!
inep: usb_get_endpoint_status(): Device or resource busy
outep: usb_get_endpoint_status(): Device or resource busy
ERROR: Could not close session!
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
ERROR: Could not close session!
inep: usb_get_endpoint_status(): Device or resource busy
outep: usb_get_endpoint_status(): Device or resource busy
ERROR: Could not close session!
Device 0 (VID=01xu and PID=6123) is a Samsung Galaxy models (MTP).
Android device detected, assigning default bug flags
Android device detected, assigning default bug flags
ERROR: Could not close session!
inep: usb_get_endpoint_status(): Device or resource busy
outep: usb_get_endpoint_status(): Device or resource busy
ERROR: Could not close session!

OK this affectr me too. I'm using Linux Mint KDE 18.2.
1) I connect my Samsung J7 Prime
2) I tap "Allow" in the message that pops up at the cellphone
2) I choose one of the two "Open with File Manager" options at the notifications.

From here anything can happen.

Sometimes I just get the accursed error that says "Kio client error: mtp protocol process ended unexpectedly" or another annoying similar message like "maybe you should unlock your device" (but I just did that! and whats' worse, the dumb phone is showing the "unlock me allow connection" message again!)

It is even possible that everything seems to work fine, until I double click a file and I get the annoying error message again "MTP protocol died unexpectedly"

Here's a screenshot
https://photos.google.com/share/AF1QipNpYjrf7O2eXkV0dEJhSUKtmI5gFaFgje83TjkIJgwGJGkxohtF0yMi5Ds7StjSWw/photo/AF1QipMZS7gihGOoP4XMeczaPPGD-l0K0NvottTdMPI?key=bHhXVkZXT1JydzF5ZlVSUFNFSmNFdU85WXgyRFRn


Right clicking a file shows that I can't cut or rename files.
Sometimes I can't even paste files. Other times I was able to paste files to the memory card, but not always. Heck! there was even a time in which it died amidst  copying a folder with several files!!!

Another screenshot:
https://photos.google.com/share/AF1QipNdCbs8pKqCxYD-b9zJCPRXdZFxsmsZ2Lm7GtpZIhVoyRWwQqeEBDVA4y_OA4XusQ/photo/AF1QipP4jzetNXyuzfz2JtsyHYwtV8pgGsPCuvcdgJE?key=WXFlMnhoSnZTM25waXhXSjgyMUY5a1dJY0UzM21R

Here are the results of running kdeinit5

$ kdeinit5
kdeinit5: Shutting down running client.
kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 9048, result = 0
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit5: opened connection to :0

Running it with the phone connected

kdeinit5
kdeinit5: Shutting down running client.
kdeinit5: Got termination request (PID 9046).
klauncher: Exiting on signal 15
kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 9116, result = 0
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit5: opened connection to :0

Same thing.

Created attachment 106746 [details]
attachment-25229-0.html

try looking into the newer protocols that are being used for phones and
tablets, i have found that they are forever changing.

On Wed, Jul 19, 2017 at 8:40 PM, <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=379680
>
> jc_josue3773@hotmail.com changed:
>
>            What    |Removed                     |Added
> ------------------------------------------------------------
> ----------------
>                  CC|                            |jc_josue3773@hotmail.com
>
> --- Comment #7 from jc_josue3773@hotmail.com ---
> OK this affectr me too. I'm using Linux Mint KDE 18.2.
> 1) I connect my Samsung J7 Prime
> 2) I tap "Allow" in the message that pops up at the cellphone
> 2) I choose one of the two "Open with File Manager" options at the
> notifications.
>
> From here anything can happen.
>
> Sometimes I just get the accursed error that says "Kio client error: mtp
> protocol process ended unexpectedly" or another annoying similar message
> like
> "maybe you should unlock your device" (but I just did that! and whats'
> worse,
> the dumb phone is showing the "unlock me allow connection" message again!)
>
> It is even possible that everything seems to work fine, until I double
> click a
> file and I get the annoying error message again "MTP protocol died
> unexpectedly"
>
> Here's a screenshot
> https://photos.google.com/share/AF1QipNpYjrf7O2eXkV0dEJhSUKtmI
> 5gFaFgje83TjkIJgwGJGkxohtF0yMi5Ds7StjSWw/photo/
> AF1QipMZS7gihGOoP4XMeczaPPGD-l0K0NvottTdMPI?key=
> bHhXVkZXT1JydzF5ZlVSUFNFSmNFdU85WXgyRFRn
>
>
> Right clicking a file shows that I can't cut or rename files.
> Sometimes I can't even paste files. Other times I was able to paste files
> to
> the memory card, but not always. Heck! there was even a time in which it
> died
> amidst  copying a folder with several files!!!
>
> Another screenshot:
> https://photos.google.com/share/AF1QipNdCbs8pKqCxYD-
> b9zJCPRXdZFxsmsZ2Lm7GtpZIhVoyRWwQqeEBDVA4y_OA4XusQ/photo/
> AF1QipP4jzetNXyuzfz2JtsyHYwtV8pgGsPCuvcdgJE?key=
> WXFlMnhoSnZTM25waXhXSjgyMUY5a1dJY0UzM21R
>
> Here are the results of running kdeinit5
>
> $ kdeinit5
> kdeinit5: Shutting down running client.
> kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/
> libexec/kf5/klauncher'
> kdeinit5: Launched KLauncher, pid = 9048, result = 0
> Connecting to deprecated signal
> QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
> kdeinit5: opened connection to :0
>
> Running it with the phone connected
>
> kdeinit5
> kdeinit5: Shutting down running client.
> kdeinit5: Got termination request (PID 9046).
> klauncher: Exiting on signal 15
> kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/
> libexec/kf5/klauncher'
> kdeinit5: Launched KLauncher, pid = 9116, result = 0
> Connecting to deprecated signal
> QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
> kdeinit5: opened connection to :0
>
> Same thing.
>
> --
> You are receiving this mail because:
> You reported the bug.
>

This is bug #396527

*** This bug has been marked as a duplicate of bug 396527 ***