Description of problem: Searching for a file in nautilus Version-Release number of selected component: nautilus-3.22.1-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: nautilus_files_view_activate_files executable: /usr/bin/nautilus global_pid: 31457 kernel: 4.8.12-300.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 (10 frames) #0 nautilus_files_view_activate_files at nautilus-files-view.c:1176 #1 nautilus_files_view_activate_selection at nautilus-files-view.c:1149 #2 query_editor_activated_callback at nautilus-window-slot.c:357 #9 g_signal_emitv at gsignal.c:3129 #10 gtk_binding_entry_activate at gtkbindings.c:646 #11 binding_activate at gtkbindings.c:1446 #12 gtk_bindings_activate_list at gtkbindings.c:1505 #13 gtk_bindings_activate_event at gtkbindings.c:1592 #14 gtk_entry_key_press at gtkentry.c:4824 #15 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
Created attachment 1231682 [details] File: backtrace
Created attachment 1231683 [details] File: cgroup
Created attachment 1231684 [details] File: core_backtrace
Created attachment 1231685 [details] File: dso_list
Created attachment 1231686 [details] File: environ
Created attachment 1231687 [details] File: exploitable
Created attachment 1231688 [details] File: limits
Created attachment 1231689 [details] File: maps
Created attachment 1231690 [details] File: mountinfo
Created attachment 1231691 [details] File: namespaces
Created attachment 1231692 [details] File: open_fds
Created attachment 1231693 [details] File: proc_pid_status
Created attachment 1231694 [details] File: var_log_messages
This happens for me with a stray yubikey input. See bugs https://bugzilla.redhat.com/show_bug.cgi?id=1401074 https://bugzilla.gnome.org/show_bug.cgi?id=776304
Similar problem has been detected: Type smb:\\ at the address entry. But that seems not reproducible. reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: nautilus_files_view_activate_files executable: /usr/bin/nautilus global_pid: 2669 kernel: 4.9.4-201.fc25.x86_64 package: nautilus-3.22.2-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1460887 has been marked as a duplicate of this bug. ***
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.