Hide Forgot
Version-Release number of selected component: nautilus-3.22.1-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 3 cmdline: /usr/bin/nautilus --gapplication-service crash_function: nautilus_file_new_from_filename executable: /usr/bin/nautilus global_pid: 22056 kernel: 4.8.4-301.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #4 nautilus_file_new_from_filename at nautilus-file.c:580 #5 nautilus_file_get_internal at nautilus-file.c:759 #6 nautilus_file_get_by_uri at nautilus-file.c:809 #7 nautilus_drag_build_selection_list at nautilus-dnd.c:225 #8 nautilus_canvas_container_dropped_canvas_feedback at nautilus-canvas-dnd.c:432 #9 drag_data_received_callback at nautilus-canvas-dnd.c:1801 #10 ?? #11 ??
Created attachment 1215621 [details] File: backtrace
Created attachment 1215622 [details] File: cgroup
Created attachment 1215623 [details] File: core_backtrace
Created attachment 1215624 [details] File: dso_list
Created attachment 1215625 [details] File: environ
Created attachment 1215626 [details] File: limits
Created attachment 1215627 [details] File: maps
Created attachment 1215628 [details] File: mountinfo
Created attachment 1215629 [details] File: namespaces
Created attachment 1215630 [details] File: open_fds
Created attachment 1215631 [details] File: proc_pid_status
Created attachment 1215632 [details] File: var_log_messages
*** Bug 1448663 has been marked as a duplicate of this bug. ***
Similar problem has been detected: 1. I opened a file manager window by double clicking on a folder icon on my desktop. 2. I then navigated to a subdirectory. 3. I single clicked on a file in Nautilus (with my configuration double click is required to open a file or folder). Nautilus immediately crashed causing the file manager window to disappear. 4. I repeated the above process several times but could not duplicate. reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: nautilus_file_new_from_filename executable: /usr/bin/nautilus global_pid: 4473 kernel: 4.11.5-200.fc25.x86_64 package: nautilus-3.22.3-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: nautilus killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Created attachment 1290792 [details] File: backtrace
Similar problem has been detected: I tried to link a folder from a nautlus window to the desktop reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: nautilus-desktop crash_function: nautilus_file_new_from_filename executable: /usr/bin/nautilus-desktop global_pid: 2254 kernel: 4.10.12-200.fc25.x86_64 package: nautilus-3.22.3-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: nautilus-desktop killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.