How to fix the following issue:
$ svn update
Password for 'default' GNOME keyring:
svn: GNOME Keyring is locked and we are non-interactive
I have googled around but can't seem to find a satisfactory answer.
Add a comment
|
4 Answers
Edit the ~/.subversion/config with gedit or nano , and add the following
[auth]
password-stores =
then save and try again. All the best.
-
-
Unfortunately, adding this line gives me:
svn: ~/.subversion/config:17: Option expectedandsvnrefuses to proceed... what worked for me wasmv ~/.gnome2/keyrings/login.keyring ~/.gnome2/keyrings/_login.keyringas per Being prompted for '(null)' GNOME keyring - Stack Overflow; but then SVN insists on storing the password, once it passes, to a new Gnome keyring - which I don't want (I want to be asked each time, as when I use SVN over ssh), but that's another issue...– sdaauOct 30, 2014 at 17:52 -
You have moved the the file from where currently gnome will fetch. so its keep on asking everytime.– Raja GOct 30, 2014 at 18:12
-
It's worth nothing that this means disabling the encrypted storage of SVN passwords which you might not want to do. Jul 9, 2018 at 14:18
run the below command:
seahorse
and then delete all items in the menu. The problem wil be gone
-
This was very helpful for a similar problem where svn would hang. Running seahorse showed me that the keyring was locked. Unlocked it, and svn is back to normal.– poleguyMar 1, 2021 at 17:53
Solution 1
In my case the problem persisted until I deleted the default keyring. Using Mate Linux you can use this command to delete the default key file:
rm ~/.config/mate/keyrings/default
That solved the problem for me...
None of the solutions googled (removing keyrings from ~/.gnome2, blanking password-stores from ~/.subversion/config, ...) worked for me. I had to unset environment variables GNOME_KEYRING_CONTROL GNOME_KEYRING_PID in my startup files (~/.xsession or whatever) in order to prevent their values being inherited from the desktop/login environment.
