Description of problem: I was copying files to my Android phone when I got this crash Version-Release number of selected component: kf5-kio-core-5.59.0-1.fc30 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cmdline: /usr/libexec/kf5/kiod5 crash_function: LIBMTP_Get_Filemetadata executable: /usr/libexec/kf5/kiod5 journald_cursor: s=6671bf964b3d42608d7812ce9bad0bde;i=5d225;b=844df530944446609a426ab30cdacb6f;m=6a472094;t=59310bd16fd52;x=4e0a2df8d0ede747 kernel: 5.2.15-200.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 LIBMTP_Get_Filemetadata at libmtp.c:4355 #1 MTPStorage::getFileFromPath at /usr/include/qt5/QtCore/qobject.h:408 #2 MTPStorage::getFileMetadata at /usr/src/debug/kio-extras-19.04.2-1.fc30.x86_64/mtp/kiod_module/mtpstorage.cpp:477 #3 StorageAdaptor::getFileMetadata at /usr/include/qt5/QtCore/qobject.h:408 #4 StorageAdaptor::qt_static_metacall at /usr/src/debug/kio-extras-19.04.2-1.fc30.x86_64/x86_64-redhat-linux-gnu/mtp/kiod_module/storageadaptor.moc:188 #5 StorageAdaptor::qt_metacall at /usr/src/debug/kio-extras-19.04.2-1.fc30.x86_64/x86_64-redhat-linux-gnu/mtp/kiod_module/storageadaptor.moc:273 #6 QDBusConnectionPrivate::deliverCall at qdbusintegrator.cpp:991 #7 QDBusConnectionPrivate::activateCall at qdbusintegrator.cpp:901 #9 QDBusConnectionPrivate::activateObject at qdbusintegrator.cpp:1478 #11 QDBusActivateObjectEvent::placeMetaCall at qdbusintegrator.cpp:1598
Created attachment 1617515 [details] File: backtrace
Created attachment 1617516 [details] File: cgroup
Created attachment 1617517 [details] File: core_backtrace
Created attachment 1617518 [details] File: cpuinfo
Created attachment 1617519 [details] File: dso_list
Created attachment 1617520 [details] File: environ
Created attachment 1617521 [details] File: exploitable
Created attachment 1617522 [details] File: limits
Created attachment 1617523 [details] File: maps
Created attachment 1617524 [details] File: mountinfo
Created attachment 1617525 [details] File: open_fds
Created attachment 1617526 [details] File: proc_pid_status
Created attachment 1617527 [details] File: var_log_messages
upstream bugreport https://bugs.kde.org/show_bug.cgi?id=412159
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. 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 30 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 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.