Version-Release number of selected component: nautilus-3.14.0-2.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 3 cmdline: /usr/bin/nautilus --gapplication-service crash_function: nautilus_window_sync_location_widgets executable: /usr/bin/nautilus kernel: 3.16.3-302.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 nautilus_window_sync_location_widgets at nautilus-window.c:1029 #1 real_active at nautilus-window-slot.c:482 #5 g_signal_emit_by_name at gsignal.c:3405 #10 gtk_notebook_switch_page at gtknotebook.c:6778 #11 gtk_notebook_real_remove at gtknotebook.c:5049 #12 gtk_notebook_remove at gtknotebook.c:4213 #13 nautilus_notebook_remove at nautilus-notebook.c:465 #14 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:1312 #15 _g_closure_invoke_va at gclosure.c:831 #18 gtk_container_remove at gtkcontainer.c:1615 Potential duplicate: bug 1067854
Created attachment 943976 [details] File: backtrace
Created attachment 943977 [details] File: cgroup
Created attachment 943978 [details] File: core_backtrace
Created attachment 943979 [details] File: dso_list
Created attachment 943980 [details] File: environ
Created attachment 943981 [details] File: exploitable
Created attachment 943982 [details] File: limits
Created attachment 943983 [details] File: maps
Created attachment 943984 [details] File: open_fds
Created attachment 943985 [details] File: proc_pid_status
Created attachment 943986 [details] File: var_log_messages
Encountered this bug by closing all folder windows while two folder move operations were in progress. The move operations were cancelled.
Similar to Jeremy Visser, I mounted my HTC one to transfer files, but the moving operation was finished, and Nautilus crashed when closing one of the two open windows.
Just adding that for me ABRT has reported this 7 times recently. May be linked to connecting a moto g 2 device via mtp.
N.B. have had no problems transferring files etc via mtp, seems much better than it was back in Fedora 19
I cannot say when this crashes, but when it does, I cannot open Nautilus again until I log out and in. This is the most annoying bug for me in all Fedora 21.
Closed Nautilus while saving/writing a file in LibreOffice to the opened directory in Nautilus, and I got this error. Can't say if there's causality between those two events though. As opposed to @Yajo, I'm able to open Nautilus again without having to log out and in. I'm also running Fedora 21.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.