Description of problem: In nautilus, just clicked on "Browse Network" than double-clicked on "Windows Network" Version-Release number of selected component: nautilus-3.6.3-4.fc18 Additional info: backtrace_rating: 4 cmdline: nautilus crash_function: compare_by_display_name executable: /usr/bin/nautilus kernel: 3.7.2-201.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 compare_by_display_name at nautilus-file.c:2872 #1 nautilus_file_compare_for_sort at nautilus-file.c:3149 #2 g_list_sort_merge at glist.c:1059 #3 g_list_sort_real at glist.c:1105 #4 g_list_sort_with_data at glist.c:1174 #5 sort_files at nautilus-view.c:3362 #6 process_new_files at nautilus-view.c:3440 #7 done_loading_callback at nautilus-view.c:3835 #8 _g_closure_invoke_va at gclosure.c:840 #11 nautilus_directory_emit_done_loading at nautilus-directory.c:833
Created attachment 683197 [details] File: backtrace
Created attachment 683198 [details] File: build_ids
Created attachment 683199 [details] File: cgroup
Created attachment 683200 [details] File: core_backtrace
Created attachment 683201 [details] File: dso_list
Created attachment 683202 [details] File: environ
Created attachment 683203 [details] File: limits
Created attachment 683204 [details] File: maps
Created attachment 683205 [details] File: open_fds
Created attachment 683206 [details] File: proc_pid_status
Created attachment 683207 [details] File: smolt_data
Created attachment 683208 [details] File: var_log_messages
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Attempting to open windows networked drives in nautilus.Navigated to network (in sidebar), double clicked on available Windows Network followed by crash. Repeated process and recreated the issue. reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: nautilus '/home/akenmore/Sublime Text 2' crash_function: compare_by_display_name executable: /usr/bin/nautilus kernel: 3.9.5-201.fc18.x86_64 package: nautilus-3.6.3-4.fc18 reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
opened nautilus, tried to browse a "windows network" reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: nautilus crash_function: compare_by_display_name executable: /usr/bin/nautilus kernel: 3.10.4-100.fc18.x86_64 package: nautilus-3.6.3-5.fc18 reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.