[kio-extras] [Bug 379680] MTP protocol died unexpectedly

[Sebastian Kügler]

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

Sebastian Kügler  changed:

   What|Removed |Added

 CC||se...@kde.org
   Assignee|plasma-devel@kde.org|plasma-b...@kde.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 379680] MTP protocol died unexpectedly

[Germano Massullo]

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

--- Comment #6 from Germano Massullo  ---
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!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 379680] MTP protocol died unexpectedly

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #5 from Christoph Feck  ---
Thanks for the update; maybe someone has other ideas to debug the issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 379680] MTP protocol died unexpectedly

[bugzilla_noreply]

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

--- Comment #4 from lordgearian2...@gmail.com ---
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"  wrote:

> https://bugs.kde.org/show_bug.cgi?id=379680
>
> --- Comment #3 from Christoph Feck  ---
> 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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 379680] MTP protocol died unexpectedly

[Christoph Feck]

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

--- Comment #3 from Christoph Feck  ---
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 are the assignee for the bug.

[kio-extras] [Bug 379680] MTP protocol died unexpectedly

[Christoph Feck]

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

--- Comment #2 from Christoph Feck  ---
If you can provide the information requested in comment #1, please add it.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kio-extras] [Bug 379680] MTP protocol died unexpectedly

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
   Assignee|dolphin-bugs-n...@kde.org   |plasma-devel@kde.org
Version|15.12.3 |unspecified
Product|dolphin |kio-extras
 Status|UNCONFIRMED |NEEDSINFO
  Component|general |default
 CC||elvis.angelac...@kde.org

--- Comment #1 from Elvis Angelaccio  ---
Please run 'kdeinit5' in a terminal, try again and copy here any relevant
output about mtp.

-- 
You are receiving this mail because:
You are the assignee for the bug.