WS Discovery is irrelevant for storage systems that don't even have WS capabilities at all. Please take note that the relevant component gvfsd- smb-browse already clearly has the capability to work here but _requires_ a kill/restart of the component after a fresh reboot to fix. This could easily be solved with adjusting the internal code to instead of fail as it does, just re-init itself in similar logical vein (but better than killing it).
So yet again to say explicitly WS DISCOVERY AND RELATED WS ASPECTS ARE NOT THE SOLUTION HERE. How many times do I need to say that here and elsewhere before it gets noticed and read? I am glad that you chimed in Sebastien Bacher, as this is now approaching 5 years outstanding as an issue, despite there being a clearly simple solution (within the code). And I do hear you on the always limited resources. But I genuinely believe someone could bang out a solution to this (as I describe-ish) very quickly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
