[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Oh if that matters: gvfs is currently version amd64/mantic 1.52.0-1 on my side, and Nautilus is version amd64 1:45~rc-1ubuntu1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
For what it's worth, I *think* I have the same bug. Recently set up a home server with vanilla Ubuntu 23.10, up to date, using Samba (currently samba:amd64 2:4.18.6+dfsg-1ubuntu2.1). To access the shares from Windows 10 machines, for some reason I had to activate CIFS/SMB1.0 client functionality. On Ubuntu machines, also running up-to-date Ubuntu 23.10, Nautilus wants me to log into the server (before listing the shares, even if guest login is enabled on Samba) but fails anyway, not displaying shares. I for one am glad I found @bloodyiron's workaround (killall gvfsd-smb- browse) -- it does fix the issue, the shares instantly become visible and accessible with guest/anonymous login. My previous workaround was to ctrl-L to access the address bar and use smb://path_to_server/share to access the shares using a GUI. I get that the bug is originating from upstream. But on the other hand, in my case, I set up Samba shares from the most recent Ubuntu release, and cannot access it by default, using the default file browser of another up-to-date Ubuntu install. I would have thought that this would be a common use case, and hence rather important to fix one way or the other. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
This is mostly a "mee too" post. Using a GTX 1060. The upgrade to 19.10 did not go well, stuck with graphical artifacts after a reboot. Further reboots were met with kernel panics. Finally managed to boot kernel 5.0 in safe mode and finish the installation by choosing the "repair packages" option. Was met with this autologin bug after (thanks to the thread starter for noting that -- it was not clear autologin was the culprit). An additional detail: now I seem stuck with the 430 drivers. I cannot upgrade to 435 because of "unmet dependencies" errors. Not sure if this could be related given that clearly the nVidia drivers are involved in this mess. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
