Description of problem: Version-Release number of selected component: nautilus-3.24.1-1.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/nautilus journald_cursor: s=d5ff60c0c4d64df29c42275b0058be36;i=4a5e89;b=05d0d07531ed4cc8983dfd687151224b;m=2b132432d;t=550a0d9340a9d;x=9d6336e7b4fffb76 kernel: 4.11.3-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_is_fundamentally_a at gtype.c:4023 #1 g_object_ref at gobject.c:3051 #2 g_list_copy_deep at glist.c:680 #3 nautilus_files_view_set_selection at nautilus-files-view.c:3090 #4 load_new_location at nautilus-window-slot.c:1794 #5 setup_view at nautilus-window-slot.c:1722 #6 got_file_info_for_view_selection_callback at nautilus-window-slot.c:1599 #7 call_ready_callbacks_at_idle at nautilus-directory-async.c:2010 #12 g_main_context_iteration at gmain.c:4029 #13 g_application_run at gapplication.c:2381 Potential duplicate: bug 1303196
Created attachment 1287359 [details] File: backtrace
Created attachment 1287360 [details] File: cgroup
Created attachment 1287361 [details] File: core_backtrace
Created attachment 1287362 [details] File: cpuinfo
Created attachment 1287363 [details] File: dso_list
Created attachment 1287364 [details] File: environ
Created attachment 1287365 [details] File: exploitable
Created attachment 1287366 [details] File: limits
Created attachment 1287367 [details] File: maps
Created attachment 1287368 [details] File: open_fds
Created attachment 1287369 [details] File: proc_pid_status
Created attachment 1287370 [details] File: var_log_messages
*** Bug 1470245 has been marked as a duplicate of this bug. ***
*** Bug 1485607 has been marked as a duplicate of this bug. ***
*** Bug 1487746 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I was copying files from my ext4 home directory to an ntfs partition reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/nautilus journald_cursor: s=541ebfc9dcd14d49bb7e3604e7cd6e4c;i=6939d;b=5ff930ddda1d45c69655dfa51c040604;m=254b18278e;t=55977512a25ac;x=51a6980bdd85b250 kernel: 4.12.9-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
*** Bug 1496831 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I had a folder view open in nautilus which contained three sub-folders, and also a gnome-terminal shell with the CWD == .. of the folder view in nautilus. I then issued a bash command which recursively deleted the folder being viewed in nautilus and all of its contents (rm -rfv). At that point, nautilus crashed. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/nautilus journald_cursor: s=e3fd3b1d9e024a9ea29d28008cf48bc7;i=1c25;b=b8f5c307406843b987bea62c9142160b;m=3a1fabd7;t=55b96460813b2;x=a195e5c082ce380e kernel: 4.13.5-200.fc26.x86_64 package: nautilus-3.24.2.1-1.fc26 reason: nautilus killed by SIGSEGV 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.
This should be reopened. I just experienced the same crash in Fedora 28. ABRT says that the crash duplicates this bug. And the backtrace sure looks like it. This bug is not fixed and is still open in F28.