Description of problem: I was closing a window of Files then all windows closed. Version-Release number of selected component: nautilus-3.30.0-2.fc29 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: gtk_widget_get_ancestor executable: /usr/bin/nautilus journald_cursor: s=f52ed9316a6d491abd360208e2885fe2;i=a4b54;b=485ea2053c6c4fe998c61f52342ee6f2;m=313f23dbb;t=57749ec03dfc5;x=5e8851d2e77cc108 kernel: 4.18.11-300.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_widget_get_ancestor at gtkwidget.c:11585 #1 button_data_file_changed at ../src/nautilus-pathbar.c:1436 #6 nautilus_file_emit_changed at ../src/nautilus-file.c:8357 #7 nautilus_directory_emit_change_signals at ../src/nautilus-directory.c:1030 #8 nautilus_file_changed at ../src/nautilus-file.c:8309 #9 nautilus_file_emit_changed at ../src/nautilus-file.c:8386 #10 nautilus_directory_emit_change_signals at ../src/nautilus-directory.c:1030 #11 nautilus_file_changed at ../src/nautilus-file.c:8309 #12 count_children_done at ../src/nautilus-directory-async.c:2470 #13 count_more_files_callback at ../src/nautilus-directory-async.c:2530
Created attachment 1490231 [details] File: backtrace
Created attachment 1490232 [details] File: cgroup
Created attachment 1490233 [details] File: core_backtrace
Created attachment 1490234 [details] File: cpuinfo
Created attachment 1490235 [details] File: dso_list
Created attachment 1490236 [details] File: environ
Created attachment 1490237 [details] File: exploitable
Created attachment 1490238 [details] File: limits
Created attachment 1490239 [details] File: maps
Created attachment 1490240 [details] File: mountinfo
Created attachment 1490241 [details] File: open_fds
Created attachment 1490242 [details] File: proc_pid_status
Similar problem has been detected: Usually, copy file from one folder to another by selecting file, right click select copy, and then navigate to new folder. Nautilus will crash during navigation to new folder. reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: gtk_widget_get_ancestor executable: /usr/bin/nautilus journald_cursor: s=cc8e6028fa7d4a12849a61d8a64b65d6;i=277f7;b=204eaf0c72a4469b883dc71b3eb8bf11;m=2382b1e5d;t=577e1d5d1a7f0;x=38e3770d21bcc5b5 kernel: 4.18.12-300.fc29.x86_64 package: nautilus-3.30.1-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.