Version-Release number of selected component: nautilus-3.17.90-1.fc23 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: nautilus_file_is_in_trash executable: /usr/bin/nautilus global_pid: 23265 kernel: 4.2.0-0.rc8.git0.1.fc23.x86_64+debug runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 nautilus_file_is_in_trash at nautilus-file.c:6979 #5 get_default_column_order at nautilus-list-view.c:2115 #6 set_columns_settings_from_metadata_and_preferences at nautilus-list-view.c:2164 #11 g_settings_real_change_event at gsettings.c:398 #12 ffi_call_unix64 at ../src/x86/unix64.S:76 #13 ffi_call at ../src/x86/ffi64.c:525 #14 g_cclosure_marshal_generic_va at gclosure.c:1594 #15 _g_closure_invoke_va at gclosure.c:864 #18 settings_backend_changed at gsettings.c:484 #19 g_settings_backend_invoke_closure at gsettingsbackend.c:267 Potential duplicate: bug 1207673
Created attachment 1068752 [details] File: backtrace
Created attachment 1068753 [details] File: cgroup
Created attachment 1068754 [details] File: core_backtrace
Created attachment 1068755 [details] File: dso_list
Created attachment 1068756 [details] File: environ
Created attachment 1068757 [details] File: limits
Created attachment 1068758 [details] File: maps
Created attachment 1068759 [details] File: mountinfo
Created attachment 1068760 [details] File: namespaces
Created attachment 1068761 [details] File: open_fds
Created attachment 1068762 [details] File: proc_pid_status
Created attachment 1068763 [details] File: var_log_messages
Another user experienced a similar problem: Clicked the application menu in the Top Bar --> Preferences --> BOOM! reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: nautilus_file_is_in_trash executable: /usr/bin/nautilus global_pid: 3325 kernel: 4.2.3-300.fc23.x86_64 package: nautilus-3.18.1-1.fc23 reason: nautilus killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
*** This bug has been marked as a duplicate of bug 1277625 ***