Description of problem: I was change name of some files, and the window closed. Version-Release number of selected component: nautilus-3.24.2.1-1.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: gtk_widget_unparent executable: /usr/bin/nautilus journald_cursor: s=ed608ac535c8430695d1b4474682057f;i=fa1b;b=26e2e3706fe647b5a26d91379d4cb796;m=57f3671f3;t=555f29fe92f09;x=49ec263662397c00 kernel: 4.11.11-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_widget_unparent at gtkwidget.c:4622 #1 _gtk_window_remove_popover at gtkwindow.c:12255 #2 _gtk_popover_parent_hierarchy_changed at gtkpopover.c:1822 #3 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:2102 #4 _g_closure_invoke_va at gclosure.c:867 #7 gtk_widget_propagate_hierarchy_changed_recurse at gtkwidget.c:9910 #8 _gtk_widget_propagate_hierarchy_changed at gtkwidget.c:9952 #9 gtk_widget_unparent at gtkwidget.c:4659 #10 gtk_box_remove at gtkbox.c:2629 #11 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:2102 Potential duplicate: bug 1257003
Created attachment 1309167 [details] File: backtrace
Created attachment 1309168 [details] File: cgroup
Created attachment 1309169 [details] File: core_backtrace
Created attachment 1309170 [details] File: cpuinfo
Created attachment 1309171 [details] File: dso_list
Created attachment 1309172 [details] File: environ
Created attachment 1309173 [details] File: exploitable
Created attachment 1309174 [details] File: limits
Created attachment 1309175 [details] File: maps
Created attachment 1309176 [details] File: open_fds
Created attachment 1309177 [details] File: proc_pid_status
Created attachment 1309178 [details] File: var_log_messages
Similar problem has been detected: I was renaming a file and I think I hit รง or another close key on keyboard along with "Enter" reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: gtk_widget_unparent executable: /usr/bin/nautilus journald_cursor: s=96d41cb7b6514df7addc57660f399da6;i=c34b;b=30327ba5c1f14324b3c40246584e1b94;m=1f1d352b3;t=5597342bfad6b;x=711a9f79ef5560a1 kernel: 4.12.11-300.fc26.x86_64 package: nautilus-3.24.2.1-1.fc26 reason: nautilus killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.