Description of problem: I plugged sd-card and External HDD when I try to delete file from external HDD It's simply crashed and I had re-open the HDD and happened Version-Release number of selected component: nautilus-3.17.91-1.fc23 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: report_delete_progress executable: /usr/bin/nautilus global_pid: 6883 kernel: 4.2.0-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #2 report_delete_progress at nautilus-file-operations.c:1552 #3 delete_file at nautilus-file-operations.c:1726 #15 delete_job at nautilus-file-operations.c:1834 #17 io_job_thread at gioscheduler.c:85 #18 g_task_thread_pool_thread at gtask.c:1283 #20 g_thread_proxy at gthread.c:778
Created attachment 1075272 [details] File: backtrace
Created attachment 1075273 [details] File: cgroup
Created attachment 1075274 [details] File: core_backtrace
Created attachment 1075275 [details] File: dso_list
Created attachment 1075276 [details] File: environ
Created attachment 1075277 [details] File: exploitable
Created attachment 1075278 [details] File: limits
Created attachment 1075279 [details] File: maps
Created attachment 1075280 [details] File: mountinfo
Created attachment 1075281 [details] File: namespaces
Created attachment 1075282 [details] File: open_fds
Created attachment 1075283 [details] File: proc_pid_status
Another user experienced a similar problem: When trying to permanently delete big directory. About 20000+ files and 80 GiB. reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: report_delete_progress executable: /usr/bin/nautilus global_pid: 8157 kernel: 4.2.1-300.fc23.x86_64 package: nautilus-3.18.0-1.fc23 reason: nautilus killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Same here, while working with F23 TC1, I tried several times to delete folders on ext2,ext3,ext4,FAT32 and NTFS volumes and every time nautilus crashed.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.