Description of problem: tried to drag and drop Pirith folder in to pirith folder Version-Release number of selected component: nautilus-3.17.3-1.fc23 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: directory_count_stop executable: /usr/bin/nautilus global_pid: 2461 kernel: 4.2.0-0.rc5.git0.2.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 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:882 #8 call_files_changed_free_list at nautilus-directory.c:892 #9 g_hash_table_foreach at ghash.c:1607 #10 nautilus_directory_notify_files_moved at nautilus-directory.c:1365 #11 nautilus_file_changes_consume_changes at nautilus-file-changes-queue.c:319 #12 link_job_done at nautilus-file-operations.c:5738 #13 mainloop_proxy_func at gioscheduler.c:200 Potential duplicate: bug 727399
Created attachment 1063475 [details] File: backtrace
Created attachment 1063476 [details] File: cgroup
Created attachment 1063477 [details] File: core_backtrace
Created attachment 1063478 [details] File: dso_list
Created attachment 1063479 [details] File: environ
Created attachment 1063480 [details] File: limits
Created attachment 1063481 [details] File: maps
Created attachment 1063482 [details] File: mountinfo
Created attachment 1063483 [details] File: namespaces
Created attachment 1063484 [details] File: open_fds
Created attachment 1063485 [details] File: proc_pid_status
Created attachment 1063486 [details] File: var_log_messages
Another user experienced a similar problem: Tried to move a directory to a new location by using the "move to" context menu item. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: directory_count_stop executable: /usr/bin/nautilus global_pid: 19212 kernel: 4.2.6-301.fc23.x86_64 package: nautilus-3.18.2-2.fc23 reason: nautilus killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I was transferring files back and forth between my fedora pc and windows 7 pc while bittorrenting in the background via transmission *my adsl router was bottlenecked at that point of course* however i used to do the same thing using nautilus 3.16 on fedora 22 with no problem. Thank you. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: directory_count_stop executable: /usr/bin/nautilus global_pid: 24485 kernel: 4.2.6-301.fc23.x86_64 package: nautilus-3.18.2-2.fc23 reason: nautilus killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
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.