Hide Forgot
Version-Release number of selected component: nautilus-3.10.1-2.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/nautilus --no-default-window crash_function: _g_log_abort executable: /usr/bin/nautilus kernel: 3.11.9-300.fc20.i686 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #3 _g_log_abort at gmessages.c:255 #6 directory_count_stop at nautilus-directory-async.c:2302 #7 start_or_stop_io at nautilus-directory-async.c:4448 #8 nautilus_directory_async_state_changed at nautilus-directory-async.c:4530 #9 nautilus_directory_cancel_loading_file_attributes at nautilus-directory-async.c:4741 #10 nautilus_directory_notify_files_moved at nautilus-directory.c:1418 #11 nautilus_file_changes_consume_changes at nautilus-file-changes-queue.c:321 #12 move_job_done at nautilus-file-operations.c:5144 #13 mainloop_proxy_func at gioscheduler.c:204 #18 g_main_context_iteration at gmain.c:3774
Created attachment 830907 [details] File: backtrace
Created attachment 830908 [details] File: cgroup
Created attachment 830909 [details] File: core_backtrace
Created attachment 830910 [details] File: dso_list
Created attachment 830911 [details] File: environ
Created attachment 830912 [details] File: limits
Created attachment 830913 [details] File: maps
Created attachment 830914 [details] File: open_fds
Created attachment 830915 [details] File: proc_pid_status
Created attachment 830916 [details] File: var_log_messages
This happens to me from time to time when using the move to feature of nautilus. Just after the destination is picked and files are being moved nautilus crashes. I my cases I was probably moving files to an NTFS partition and all or most of the files will have been moved when it crashes (none have been lost or corrupted I believe). ABRT mentions the bug as 'Desktop Icons crashed'.
Still happens occasionally with nautilus-3.12.0-2.fc20 from the rhughes copr repo.
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.