Description of problem: I was moving a file through 'move to' in nautilus. Version-Release number of selected component: nautilus-3.16.1-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: directory_count_stop executable: /usr/bin/nautilus global_pid: 27764 kernel: 4.0.1-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1002 Truncated backtrace: Thread no. 1 (10 frames) #4 directory_count_stop at nautilus-directory-async.c:2245 #5 start_or_stop_io at nautilus-directory-async.c:4217 #6 nautilus_directory_async_state_changed at nautilus-directory-async.c:4297 #7 call_files_changed_common at nautilus-directory.c:901 #8 call_files_changed_free_list at nautilus-directory.c:911 #9 g_hash_table_foreach at ghash.c:1607 #10 nautilus_directory_notify_files_moved at nautilus-directory.c:1442 #11 nautilus_file_changes_consume_changes at nautilus-file-changes-queue.c:319 #12 link_job_done at nautilus-file-operations.c:5490 #13 mainloop_proxy_func at gioscheduler.c:200 Potential duplicate: bug 727399
Created attachment 1021521 [details] File: backtrace
Created attachment 1021522 [details] File: cgroup
Created attachment 1021523 [details] File: core_backtrace
Created attachment 1021524 [details] File: dso_list
Created attachment 1021525 [details] File: environ
Created attachment 1021526 [details] File: limits
Created attachment 1021527 [details] File: maps
Created attachment 1021528 [details] File: mountinfo
Created attachment 1021529 [details] File: namespaces
Created attachment 1021530 [details] File: open_fds
Created attachment 1021531 [details] File: proc_pid_status
Created attachment 1021532 [details] File: var_log_messages
I was moving a folder, that's more accurate.
I think this is reproduceable. I was encountered this bug again when I was moving a folder. But the move operation itself is completed successfully.
Same thing over here, move-to intermittently crashes Nautilus. This has been happening since the new move-to/copy-to functionality was introduced (for F21 there was a Bugzilla report but it was hidden from public so I'm not sure what happened with that). It can be very easy to reproduce: 1: Use Nautilus to create a new directory (filesystem or location do not seem to matter, but I tested it with ~/Downloads on BTRFS) enter the folder and create another one inside it. 2: Go back to the start directory and use the move-to function to move the new folders to another location (I chose ~/Documents). 3: Nautilus has a high probability of crashing as soon as the move-to action is confirmed. The failproof workaround for this is to use the copy-to function and then afterwards manually remove the original directories.
Another user experienced a similar problem: I wanted to move one sub-directory from one directory to another one reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: directory_count_stop executable: /usr/bin/nautilus global_pid: 31266 kernel: 4.0.4-303.fc22.x86_64 package: nautilus-3.16.2-1.fc22 reason: nautilus killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.