Description of problem: I went to click one of the links on the left-hand sidebar Version-Release number of selected component: nemo-2.4.4-4.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: nemo crash_function: __strcmp_sse2_unaligned executable: /usr/bin/nemo kernel: 3.19.1-201.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at Fri 2015-02-27 23:48:34 GMT, end at Tue 2015-03-24 01:30:17 GMT. -- Truncated backtrace: Thread no. 1 (10 frames) #0 __strcmp_sse2_unaligned at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:29 #1 nemo_action_get_visibility at nemo-action.c:1360 #2 bookmarks_check_popup_sensitivity at nemo-places-sidebar.c:2286 #3 _g_closure_invoke_va at gclosure.c:831 #6 _gtk_tree_selection_internal_select_node at gtktreeselection.c:1594 #7 gtk_tree_view_real_set_cursor at gtktreeview.c:13286 #8 gtk_tree_view_multipress_gesture_pressed at gtktreeview.c:3287 #9 ffi_call_unix64 at ../src/x86/unix64.S:76 #10 ffi_call at ../src/x86/ffi64.c:525 #11 g_cclosure_marshal_generic_va at gclosure.c:1541
Created attachment 1005614 [details] File: backtrace
Created attachment 1005615 [details] File: cgroup
Created attachment 1005616 [details] File: core_backtrace
Created attachment 1005617 [details] File: dso_list
Created attachment 1005618 [details] File: environ
Created attachment 1005619 [details] File: exploitable
Created attachment 1005620 [details] File: limits
Created attachment 1005621 [details] File: maps
Created attachment 1005622 [details] File: open_fds
Created attachment 1005623 [details] File: proc_pid_status
Another user experienced a similar problem: Not sure how it happened. I was looking at files in a directory on an external drive when it crashed. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: nemo -n crash_function: __strcmp_sse2_unaligned executable: /usr/bin/nemo kernel: 3.19.5-200.fc21.x86_64 package: nemo-2.4.5-2.fc21 reason: nemo killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.