Bug 1770549

Summary: Unable to access "Networks" locations with "Files", since Fedora 31
Product: [Fedora] Fedora Reporter: laurent.chrismann
Component: sambaAssignee: Matthias Clasen <mclasen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 31CC: abokovoy, anoopcs, asn, caillon+fedoraproject, cosimo.cecchi, gdeschner, gnome-sig, iboukris, jarrpa, john.j5live, jstephen, lmohanty, madam, mclasen, philip.wyett, rhughes, sandmann, sbose, ssorce
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-02 15:14:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Popup when clicked "my server" none

Description laurent.chrismann 2019-11-10 12:24:34 UTC
Created attachment 1634554 [details]
Popup when clicked "my server"

Description of problem:


Version-Release number of selected component (if applicable):

Linux : 5.3.8-300.fc31.x86_64 #1 SMP Tue Oct 29 14:28:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Gnome shell : 3.34.1
Nautilus : "3.34.1 - stable" ("about" window)


How reproducible:
Always

Steps to Reproduce:
1. Open Nautilus
2. "Other places"
3. "Networks" -> "my server" or "Windows network" (in this case, it results in : "directory empty")

Actual results:
"Unable to access location" popup

Expected results:
Nautilus proposes authentication options "anonymous", "login/pwd", etc.

Additional info:
Used to work until FC 30 (and the corresponding Gnome-shell version) ; seems linked to Gnome, because when I boot (with grub) back with a FC 30 version but with the FC 31's Gnome version, it doesn't work, either.

Comment 1 laurent.chrismann 2020-02-02 15:14:57 UTC

*** This bug has been marked as a duplicate of bug 1768117 ***