Description of problem: Connect to samba server, get a dialog for authentication, entered credentials, crash. Version-Release number of selected component: nautilus-3.24.1-1.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: gtk_stack_set_visible_child_name executable: /usr/bin/nautilus journald_cursor: s=92cd7786809847a6b045c105dce30083;i=14b484;b=80b3e020d8104cbe918abcf63ae1fe69;m=2d5bd2bf6;t=55322050f6068;x=b7b197a09939eced kernel: 4.11.7-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_stack_set_visible_child_name at gtkstack.c:1839 #1 populate_servers at gtk/nautilusgtkplacesview.c:534 #2 ffi_call_unix64 at ../src/x86/unix64.S:76 #3 ffi_call at ../src/x86/ffi64.c:525 #4 g_cclosure_marshal_generic_va at gclosure.c:1604 #5 _g_closure_invoke_va at gclosure.c:867 #8 g_file_monitor_emit_event at gfilemonitor.c:290 #9 g_file_monitor_source_dispatch at glocalfilemonitor.c:546 #13 g_main_context_iteration at gmain.c:4033 #14 g_application_run at gapplication.c:2381 Potential duplicate: bug 1448631
Created attachment 1293000 [details] File: backtrace
Created attachment 1293001 [details] File: cgroup
Created attachment 1293002 [details] File: core_backtrace
Created attachment 1293003 [details] File: cpuinfo
Created attachment 1293004 [details] File: dso_list
Created attachment 1293005 [details] File: environ
Created attachment 1293006 [details] File: exploitable
Created attachment 1293007 [details] File: limits
Created attachment 1293008 [details] File: maps
Created attachment 1293009 [details] File: open_fds
Created attachment 1293010 [details] File: proc_pid_status
Created attachment 1293011 [details] File: var_log_messages
Seems to happen first attempt following a reboot. So reboot, go to Nautilus, the try to connect to samba server (Fedora 26 server) -> crash. If I go to Nautilus and do other things and close that window, it doesn't appear to happen. So it's something about the directness of going right to connecting to a server and it crashes. Upon relaunch, there's no need to try to connect, Nautilus shows the share is already connected.
*** Bug 1479338 has been marked as a duplicate of this bug. ***
*** Bug 1480974 has been marked as a duplicate of this bug. ***
*** Bug 1483162 has been marked as a duplicate of this bug. ***
*** Bug 1494222 has been marked as a duplicate of this bug. ***
*** Bug 1496682 has been marked as a duplicate of this bug. ***
*** Bug 1499571 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.