Hide Forgot
Description of problem: An error occurs when right-clicking an item and choosing "Move to..." item. After picking the destination in the dialog box and confirming it, the entire Nautilus session crashes. However, the in the end, the file is moved to its final destination. I think file manager cannot be that unstable and unreliable when it comes to performing its basic functions. If there's any more info that I can provide or tests I can perform, please let me know. Version-Release number of selected component: nautilus-3.20.3-1.fc24 Additional info: reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: nautilus -n crash_function: filesystem_info_stop executable: /usr/bin/nautilus global_pid: 1653 kernel: 4.7.7-200.local.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 filesystem_info_stop at nautilus-directory-async.c:3928 #5 start_or_stop_io at nautilus-directory-async.c:4232 #6 nautilus_directory_async_state_changed at nautilus-directory-async.c:4305 #7 call_files_changed_common at nautilus-directory.c:907 #8 call_files_changed_free_list at nautilus-directory.c:917 #9 g_hash_table_foreach at ghash.c:1608 #10 nautilus_directory_notify_files_moved at nautilus-directory.c:1390 #11 nautilus_file_changes_consume_changes at nautilus-file-changes-queue.c:319 #12 g_task_return_now at gtask.c:1107 #13 complete_in_idle_cb at gtask.c:1121 Potential duplicate: bug 927039
Created attachment 1215314 [details] File: backtrace
Created attachment 1215315 [details] File: cgroup
Created attachment 1215316 [details] File: core_backtrace
Created attachment 1215317 [details] File: dso_list
Created attachment 1215318 [details] File: environ
Created attachment 1215319 [details] File: limits
Created attachment 1215320 [details] File: maps
Created attachment 1215321 [details] File: mountinfo
Created attachment 1215322 [details] File: namespaces
Created attachment 1215323 [details] File: open_fds
Created attachment 1215324 [details] File: proc_pid_status
Created attachment 1215325 [details] File: var_log_messages
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.