Version-Release number of selected component: nemo-2.6.7-1.fc22 Additional info: reporter: libreport-2.6.1 backtrace_rating: 4 cmdline: nemo -n crash_function: strcmp executable: /usr/bin/nemo global_pid: 1920 kernel: 4.0.8-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 strcmp at ../sysdeps/x86_64/strcmp.S:209 #1 nemo_action_get_visibility at nemo-action.c:1359 #2 bookmarks_check_popup_sensitivity at nemo-places-sidebar.c:2291 #3 _g_closure_invoke_va at /lib64/libgobject-2.0.so.0 #5 g_signal_emit_by_name at /lib64/libgobject-2.0.so.0 #6 gtk_tree_view_row_deleted at gtktreeview.c:9359 #11 gtk_tree_model_filter_row_deleted at gtktreemodelfilter.c:2667 #16 gtk_tree_store_remove at gtktreestore.c:1226 #17 gtk_tree_store_clear_traverse at gtktreestore.c:1851 #20 gtk_tree_store_clear at gtktreestore.c:1879 Potential duplicate: bug 1027467
Created attachment 1057239 [details] File: backtrace
Created attachment 1057240 [details] File: cgroup
Created attachment 1057241 [details] File: core_backtrace
Created attachment 1057242 [details] File: dso_list
Created attachment 1057243 [details] File: environ
Created attachment 1057244 [details] File: limits
Created attachment 1057245 [details] File: maps
Created attachment 1057246 [details] File: mountinfo
Created attachment 1057247 [details] File: namespaces
Created attachment 1057248 [details] File: open_fds
Created attachment 1057249 [details] File: proc_pid_status
Created attachment 1057250 [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.