Description of problem: Pressed Shift-Delete on a folder. I believe the folder was about 21 Mb with perhaps 70-100 children at the top level and in subfolders Version-Release number of selected component: nemo-2.2.4-1.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: nemo -n crash_function: nemo_file_emit_changed executable: /usr/bin/nemo kernel: 3.16.7-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #3 nemo_file_emit_changed at nemo-file.c:7325 #4 nemo_directory_emit_change_signals at nemo-directory.c:744 #5 call_files_changed_common at nemo-directory.c:836 #6 call_files_changed_unref_free_list at nemo-directory.c:855 #7 g_hash_table_foreach at ghash.c:1526 #8 nemo_directory_notify_files_removed at nemo-directory.c:1106 #9 nemo_file_changes_consume_changes at nemo-file-changes-queue.c:315 #10 delete_job_done at nemo-file-operations.c:1867 #11 mainloop_proxy_func at gioscheduler.c:204 #15 g_main_context_iteration at gmain.c:3774
Created attachment 956508 [details] File: backtrace
Created attachment 956509 [details] File: cgroup
Created attachment 956510 [details] File: core_backtrace
Created attachment 956511 [details] File: dso_list
Created attachment 956512 [details] File: environ
Created attachment 956513 [details] File: exploitable
Created attachment 956514 [details] File: limits
Created attachment 956515 [details] File: maps
Created attachment 956516 [details] File: open_fds
Created attachment 956517 [details] File: proc_pid_status
Created attachment 956518 [details] File: var_log_messages
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.