Version-Release number of selected component: nautilus-3.18.1-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: nautilus_list_model_is_empty executable: /usr/bin/nautilus global_pid: 2667 kernel: 4.2.3-300.fc23.x86_64+debug runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 nautilus_list_model_is_empty at nautilus-list-model.c:962 #1 nautilus_files_view_is_empty at nautilus-files-view.c:762 #2 real_update_actions_state at nautilus-files-view.c:6375 #3 nautilus_files_view_update_toolbar_menus at nautilus-files-view.c:6709 #4 done_loading at nautilus-files-view.c:3120 #6 nautilus_files_view_stop_loading at nautilus-files-view.c:7193 #7 nautilus_files_view_destroy at nautilus-files-view.c:2811 #12 gtk_widget_dispose at gtkwidget.c:12010 #14 gtk_widget_destroy at gtkwidget.c:4656 #15 nautilus_window_slot_dispose at nautilus-window-slot.c:2276
Created attachment 1084516 [details] File: backtrace
Created attachment 1084517 [details] File: cgroup
Created attachment 1084518 [details] File: core_backtrace
Created attachment 1084519 [details] File: dso_list
Created attachment 1084520 [details] File: environ
Created attachment 1084521 [details] File: exploitable
Created attachment 1084522 [details] File: limits
Created attachment 1084523 [details] File: maps
Created attachment 1084524 [details] File: mountinfo
Created attachment 1084525 [details] File: open_fds
Created attachment 1084526 [details] File: proc_pid_status
Created attachment 1084527 [details] File: var_log_messages
Another user experienced a similar problem: Refreshing home directory, showing and hiding hidden files. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: nautilus_list_model_is_empty executable: /usr/bin/nautilus global_pid: 19337 kernel: 4.2.3-300.fc23.x86_64 package: nautilus-3.18.1-1.fc23 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
I think this is related to *** This bug has been marked as a duplicate of bug 1277625 ***