Update to Samba 4.15.7
sudo dnf upgrade --refresh --advisory=FEDORA-2022-5c64120636
This update has been submitted for testing by gd.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by gd.
This update has been pushed to stable.
Somehow I get the "Invalid Argument"-bug now on Fedora 35 after I updated my system related to this in Fedora 36 https://bugzilla.redhat.com/show_bug.cgi?id=2068976
I am also getting the invalid argument when trying to connect to Samba server. Might want to roll this one back.
Same problem mentioned on previous comments
Guess I should have negative karma comment...
Same problem. Can't mount smb shares after the update.
it broke samba access via nautilus
This update to gvfs should solve this problem:
should
FEDORA-2022-45c9d57591
Or upgrade to gvfs-1.51.1-1 in the Fedora 36 testing repo.
Please login to add feedback.
Confirm request to re-trigger tests.
This update has been submitted for testing by gd.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by gd.
This update has been pushed to stable.
Somehow I get the "Invalid Argument"-bug now on Fedora 35 after I updated my system related to this in Fedora 36 https://bugzilla.redhat.com/show_bug.cgi?id=2068976
I am also getting the invalid argument when trying to connect to Samba server. Might want to roll this one back.
Same problem mentioned on previous comments
Guess I should have negative karma comment...
Same problem. Can't mount smb shares after the update.
it broke samba access via nautilus
This update to gvfs
shouldsolve this problem:FEDORA-2022-45c9d57591
Or upgrade to gvfs-1.51.1-1 in the Fedora 36 testing repo.