Hide Forgot
Description of problem: Copy/paste (or drag/drop) from Dolphin window where Android mobile phone (Sony Xperia S) camera image directory is opened. The process randomly (not always) crashes. With enough retrying image copying succeeds Version-Release number of selected component: kdelibs-4.11.3-1.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: 'kdeinit4: kio_mtp [kdeinit] mtp local:/tmp/ks' '' '' crash_function: MTPSlave::copy executable: /usr/bin/kdeinit4 kernel: 3.11.8-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 MTPSlave::copy at /usr/src/debug/kio_mtp-0.75/kio_mtp.cpp:777 #1 KIO::SlaveBase::dispatch at /usr/src/debug/kdelibs-4.11.3/kio/kio/slavebase.cpp:1106 #2 KIO::SlaveBase::dispatchLoop at /usr/src/debug/kdelibs-4.11.3/kio/kio/slavebase.cpp:289 #3 kdemain at /usr/src/debug/kio_mtp-0.75/kio_mtp.cpp:59 #4 launch at /usr/src/debug/kdelibs-4.11.3/kinit/kinit.cpp:726 #5 handle_launcher_request at /usr/src/debug/kdelibs-4.11.3/kinit/kinit.cpp:1218 #6 handle_requests at /usr/src/debug/kdelibs-4.11.3/kinit/kinit.cpp:1411
Created attachment 831231 [details] File: backtrace
Created attachment 831232 [details] File: cgroup
Created attachment 831233 [details] File: core_backtrace
Created attachment 831234 [details] File: dso_list
Created attachment 831235 [details] File: environ
Created attachment 831236 [details] File: limits
Created attachment 831237 [details] File: maps
Created attachment 831238 [details] File: open_fds
Created attachment 831239 [details] File: proc_pid_status
Created attachment 831240 [details] File: var_log_messages
You might consider testing, https://admin.fedoraproject.org/updates/FEDORA-2013-22214/kio_mtp-0.75-4.20131020git2063e75.fc19 which may help here
I suspect some temporary USB related problem. Failed to reproduce in another USB port (USB 3.0 directly to PC instead of USB 2.0 through hub) with both old and new versions. Rebooted and retested through the same USB 2.0 port where I got earlier problems and failed to reproduce them even when downgraded kio_mtp back. kio_mtp should not crash even if there is some USB related communication problem. It may however be difficult to investigate problem more if it cannot be reproduced. I also saw huge number of messages like Dec 1 19:34:29 ap kernel: [556280.486808] usb 2-1.2.7: usbfs: process 3642 (kio_mtp) did not claim interface 0 before use when I got the problem but not any more after rebooting (with old kio_mtp-0.75-2.20130323gitcc6b195.fc19.x86_64). That is the same type of message as for bug 1019620.
*** Bug 1069742 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.