Description of problem: Open Nautilus, ask to browse network (Samba). Version-Release number of selected component: nautilus-3.16.2-1.fc22 Additional info: reporter: libreport-2.6.0 backtrace_rating: 4 cmdline: nautilus --no-default-window --force-desktop crash_function: compare_by_display_name executable: /usr/bin/nautilus global_pid: 2540 kernel: 4.0.6-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 compare_by_display_name at nautilus-file.c:2881 #1 nautilus_file_compare_for_sort at nautilus-file.c:3144 #2 g_list_sort_merge at glist.c:1134 #3 g_list_sort_real at glist.c:1180 #4 g_list_sort_with_data at glist.c:1250 #5 sort_files at nautilus-view.c:2929 #6 process_new_files at nautilus-view.c:3007 #7 done_loading_callback at nautilus-view.c:3397 #8 _g_closure_invoke_va at gclosure.c:831 #11 nautilus_directory_emit_done_loading at nautilus-directory.c:818 Potential duplicate: bug 901881
Created attachment 1050402 [details] File: backtrace
Created attachment 1050403 [details] File: cgroup
Created attachment 1050404 [details] File: core_backtrace
Created attachment 1050405 [details] File: dso_list
Created attachment 1050406 [details] File: environ
Created attachment 1050407 [details] File: limits
Created attachment 1050408 [details] File: maps
Created attachment 1050409 [details] File: mountinfo
Created attachment 1050410 [details] File: namespaces
Created attachment 1050411 [details] File: open_fds
Created attachment 1050412 [details] File: proc_pid_status
Created attachment 1050413 [details] File: var_log_messages
Another user experienced a similar problem: Double-clicked on a network share (smb://fubar) and then the SIGSEGV happened. reporter: libreport-2.6.0 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: compare_by_display_name executable: /usr/bin/nautilus global_pid: 3974 kernel: 4.0.7-300.fc22.x86_64 package: nautilus-3.16.2-2.fc22 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.