I installed Seahorse, but I have no idea what I’m supposed to be looking, unfortunately…
Under Login tab I only have Chrome Safe Storage and Chrome Safe Storage Control…
But this did ring a bell, one thing that I did similar to this is enabling SSH for GitHub, and I was starting this SSH agent, because the tutorial said I’m supposed too.
How do I access options from your ss?
EDIT: Found the options, they are same as yours.
Sorry, what does “ss” mean ? 
If you do not see anything related to your samba share in seahorse, then, here is the issue.
You should have your samba credentials there.
Check if it’s enable at startup : Settings → Session and Startup : check anything related to “Gnome Keyring”.
Then reboot
So you have to check the boxes related to gnome keyring, reboot
ss = screenshot, sorry about that.
I did check those three options before the last, but after reboot nothing is changed, still doesn’t accept entered authentication. Seahorse still doesn’t show anything samba related though…
I found this in the arch wiki :
Troubleshooting
Passwords are not remembered
If you get a password prompt every time you login, and you find that passwords are not saved, you might need to create/set a default keyring.
Ensure that the seahorse package is installed, open it (“Passwords and Keys” in system settings) and select View > By Keyring. If there is no keyring in the left column (it will be marked with a lock icon), go to File > New > Password Keyring and give it a name. You will be asked to enter a password. If you do not give the keyring a password it will be unlocked automatically, even when using autologin, but passwords will not be stored securely. Finally, right-click on the keyring you just created and select “Set as default”.
https://wiki.archlinux.org/index.php/GNOME/Keyring
What do you have in your folder /home/$HOME/.config/autostart/ ?
Do you have something beginning by gnome-keyring…?
gvfs and gvfs-smb are well installed in your system ?
Please - one question to remain - are you using password protected access to the share connected to the router?
I have one more
What are the permissions of your /home/$HOME/.local/share/keyrings folder ?
Yes, I do have those three entries I checked (gnome-keyring-pkcs11.desktop, gnome-keyring-secrets.desktop and gnome-keyring-ssh.desktop).
I will check the link from Wiki you shared, but I my problem is not I have to enter the password every time, it’s I can’t access share at all (via Thunar’s network tab, with smbclient and with cifs mounting I can). I think I have to read a bit on this concept of keyrings…
Yes, those are the credentials Thunar asks when I try to access it and that it doesn’t accept anymore for some reason, sorry if this is important and I wasn’t clear :’(
rwx------ myuser myuser
@linux-aarhus : From Manjaro as a client, is it OK if the server is on SMBv1 ?
@MrTanguero : Maybe you could try and older version of samba client to see if it changes something
https://wiki.manjaro.org/index.php/Downgrading_packages
@yannssolo I successfully can access shares using smbclient, you think this version might not play well with Thunar? Or what you’re proposing has nothing to do with smbclient command?
Yeah, something like that, i know SMBv1 is deprecated now. So, it’s possible that smbclient can have access to SMBv1 server and Thunar can’t, i do no know what is the samba component of Thunar to be honest.
Maybe @linux-aarhus knows it
→ Could you try another file managers ? Nautilus, Dolphin, Nemo
Nautilus behaves absolutely the same, I can see the shares, but it doesn’t accept credentials (just show the window to enter share credentials again).
With Dolphin something weird happened, when I first tried, it sent me to some further encryption methods dialog, but after it failed, I couldn’t recreate it, started behaving the same like the first two file managers.
Could it be that wrong authentication is stored somewhere and it keeps trying to supply that to the server (and fails) because in Dolphin when I tried to access the shares with different account (I created for testing purposes) it fails and brings me back to the first one?
Smb4k works, but if I understand correctly it uses cifs for mounting, I got that working from command line as well…
Credentials are stored in /home/$HOME/.local/share/keyrings/
I think we have no other choice to downgrade samba to see if you are luckier with an older version.
You could also look at the logs on your server, it should show something
I have two files in that folder: login.keyring and user.keystore.
But when I try opening them with Mousepad, I get bunch of giberish, and a warning that document is not UTF-8 valid. It lets me pick an encoding, but none from the list makes the text human-readable.
Is this normal?
yes. You can delete them, and then, do logout/login
got same issue after latest amba and smbclient update to v.4.14.0.1 on testing branch.
A recurrent prompt for credentials was popping-up when trying to connect to a network share that was perfectly connecting using the previous samba version (4.13.5.1).
I had to restore a snapshot of my pc using timeshift (rollback of samba or restore of the old samba.cfg did not work for me). Now added samba and smbclient to the ignore list of pamac waiting for a solution. FYI: running Mnjaro Cinnamon Edition on testing branch. Using Caja and Nemo file managers. Network share points to the home router HDD.
Hope this helps…
I got the same problem with recent samba update. Can’t login to shared samba mount from both thunar and pcmanfm. I’ve tried to list directory using smbclient and it is working: smbclient "//server/Documents" -U username -c "ls"
The server is old and need “client min protocol = CORE” to be connected to.
Maybe related to this issue : 1903955 – cannot connect to samba NT1 share with gvfs
Downgading samba and smbclient to 4.13.5 fix the problem for me. (was 4.14.2)
pacman -U https://archive.archlinux.org/packages/s/samba/samba-4.13.5-1-x86_64.pkg.tar.zst
pacman -U https://archive.archlinux.org/packages/s/smbclient/smbclient-4.13.5-1-x86_64.pkg.tar.zst