Description of problem: Simply tried to open caja from the task-bar icon. Then got the same result when I tried to open it from the command line. Version-Release number of selected component: caja-1.10.3-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: caja crash_function: g_hash_table_lookup_node executable: /usr/bin/caja global_pid: 12438 kernel: 4.1.4-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 g_hash_table_lookup_node at ghash.c:373 #5 g_hash_table_remove_internal at ghash.c:1352 #6 caja_directory_finalize at caja-directory.c:169 #8 caja_directory_unref at caja-directory.c:159 #9 finalize at caja-file.c:790 #11 caja_file_info_list_free at caja-file-info.c:63 #12 free_selected at na-tracker.c:570 #13 instance_dispose at na-tracker.c:353 #15 free_module_objects at caja-module.c:230 #16 eel_debug_shut_down at eel-debug.c:115
Created attachment 1064951 [details] File: backtrace
Created attachment 1064952 [details] File: cgroup
Created attachment 1064953 [details] File: core_backtrace
Created attachment 1064954 [details] File: dso_list
Created attachment 1064955 [details] File: environ
Created attachment 1064956 [details] File: limits
Created attachment 1064957 [details] File: maps
Created attachment 1064958 [details] File: mountinfo
Created attachment 1064959 [details] File: namespaces
Created attachment 1064960 [details] File: open_fds
Created attachment 1064961 [details] File: proc_pid_status
Created attachment 1064962 [details] File: var_log_messages
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.