Hide Forgot
Description of problem: I closed Nautilus during copying in progress (from a NFS mounted using autofs). Nautilus crashed and some files were not copied. I can easily reproduce. Version-Release number of selected component: nautilus-3.10.0-1.fc20 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: nautilus --new-window crash_function: nautilus_location_entry_set_special_text executable: /usr/bin/nautilus kernel: 3.11.2-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 nautilus_location_entry_set_special_text at nautilus-location-entry.c:767 #1 nautilus_location_entry_set_location at nautilus-location-entry.c:201 #2 nautilus_window_sync_location_widgets at nautilus-window.c:1020 #3 real_active at nautilus-window-slot.c:475 #7 g_signal_emit_by_name at gsignal.c:3426 #8 nautilus_window_set_active_slot at nautilus-window.c:1776 #9 notebook_switch_page_cb at nautilus-window.c:272 #14 gtk_notebook_switch_page at gtknotebook.c:6597 #15 gtk_notebook_real_remove at gtknotebook.c:4939 #16 gtk_notebook_remove at gtknotebook.c:4109
Created attachment 809746 [details] File: backtrace
Created attachment 809747 [details] File: cgroup
Created attachment 809748 [details] File: core_backtrace
Created attachment 809749 [details] File: dso_list
Created attachment 809750 [details] File: environ
Created attachment 809751 [details] File: exploitable
Created attachment 809752 [details] File: limits
Created attachment 809754 [details] File: maps
Created attachment 809755 [details] File: open_fds
Created attachment 809756 [details] File: proc_pid_status
Created attachment 809757 [details] File: var_log_messages
Another user experienced a similar problem: Unmount android device reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: nautilus --new-window crash_function: nautilus_location_entry_set_special_text executable: /usr/bin/nautilus kernel: 3.12.6-300.fc20.x86_64 package: nautilus-3.10.1-2.fc20 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.