Comment 60 for bug 1828107

I am still having this issue every time I reboot, on Ubuntu Desktop v23.10.

The "gvfs" package installed is version "1.52.0-1".

This issue is 100% reproducible, and my work-around still demonstrates that the package itself (gvfs) has the capabilities of solving this itself. Instead of failing, producing a not-helpful error, it should simply re-init the relevant components that re-init when I do the "killall gvfsd-smb-browse" after trying to browser the SMB Server. While I have not looked at the code, I know programming well-enough that a basic re-init in this scenario should be a trivial amount of code to write, as a basic work-around until a proper solution is identified.

Either way, is this even going anywhere? Are any Devs reading this at all? (Canonical or otherwise)

This issue is coming up to 5 years old, and frankly the UX here is unacceptable, potentially even threatening the usability in professional settings. Can we please get a proper solution here? Or at minimum, a built-in stop-gap solution as I have roughly described?