SVN and GNOME Keyring

Question

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.

score 32 · Answer 1 · edited Dec 01 '14 at 16:35

32

Edit the ~/.subversion/config with gedit or nano , and add the following

[auth] 
password-stores =

then save and try again. All the best.

credit

edited Dec 01 '14 at 16:35

Community

1

answered Oct 26 '12 at 06:51

Raja G

105,627
107
263
332

can you considering accept ? – Raja G Jul 29 '13 at 11:51
Unfortunately, adding this line gives me: svn: ~/.subversion/config:17: Option expected and svn refuses to proceed... what worked for me was mv ~/.gnome2/keyrings/login.keyring ~/.gnome2/keyrings/_login.keyring as 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... – sdaau Oct 30 '14 at 17:52
You have moved the the file from where currently gnome will fetch. so its keep on asking everytime. – Raja G Oct 30 '14 at 18:12
It's worth nothing that this means disabling the encrypted storage of SVN passwords which you might not want to do. – Michael Mior Jul 09 '18 at 14:18

score 5 · Answer 2 · answered Jan 03 '14 at 17:19

5

run the below command:

seahorse

and then delete all items in the menu. The problem wil be gone

answered Jan 03 '14 at 17:19

Bill Zhao

121

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. – poleguy Mar 01 '21 at 17:53

Stefan · Answer 3 · 2016-01-27T17:21:05.097

4

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...

edited Jan 27 '16 at 17:21

answered Jul 28 '13 at 09:13

Stefan

161

score 2 · Answer 4 · answered Oct 02 '13 at 18:45

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.

SVN and GNOME Keyring

4 Answers4

Solution 1