Description of problem: I tried to delete a file on my android phone (which I believe was accessed via MTP) and it seems the file was already gone and Nautilus wasn't aware. I got an error box mentioning something with MTP (sadly didn't write it down) right before it crashed completely Version-Release number of selected component: nautilus-3.28.1-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: idle_callback executable: /usr/bin/nautilus journald_cursor: s=069664f74efa4c88b7e7426d95994899;i=3d92f;b=da697b84a36242edb0a940c8651e4ca4;m=1f9fbaeb1;t=57432699e66bf;x=f20d2955c3379062 kernel: 4.17.11-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1486599
Created attachment 1478616 [details] File: backtrace
Created attachment 1478617 [details] File: cgroup
Created attachment 1478618 [details] File: core_backtrace
Created attachment 1478619 [details] File: cpuinfo
Created attachment 1478620 [details] File: dso_list
Created attachment 1478621 [details] File: environ
Created attachment 1478622 [details] File: limits
Created attachment 1478623 [details] File: maps
Created attachment 1478624 [details] File: mountinfo
Created attachment 1478625 [details] File: open_fds
Created attachment 1478626 [details] File: proc_pid_status
Similar problem has been detected: i was copying a large file to a samba share and while it was being copied I refreshed the window and then deleted the deleted the destination file wile the copy was running. reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: idle_callback executable: /usr/bin/nautilus journald_cursor: s=3bb417ed9676491caff783971df6768c;i=83550;b=9f7012abf3fa49d7b9b4e64aee8ae774;m=13803677f1;t=5764f22579f04;x=5eec3160965ec46d kernel: 4.18.7-200.fc28.x86_64 package: nautilus-3.28.1-1.fc28 reason: nautilus killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1640863 has been marked as a duplicate of this bug. ***
*** Bug 1668003 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.