up vote 17 down vote favorite
2

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.

share|improve this question
up vote 27 down vote

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

[auth] 
password-stores =

then save and try again. All the best.

credit

share|improve this answer
    
This fixed my problem. – Fred Campos Jul 29 '13 at 9:58
    
can you considering accept ? – Ten-Coin Jul 29 '13 at 11:51
1  
thanks! had similar problem, got fixed with your snippet – foobar Nov 11 '13 at 16:09
    
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. – Ten-Coin Oct 30 '14 at 18:12
up vote 4 down vote

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

share|improve this answer
up vote 3 down vote

run the below command:

seahorse

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

share|improve this answer
    
This helped me with this problem. – vsevik Jul 11 '14 at 11:05
up vote 2 down vote

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.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.