Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Software versions in use:

  • Eclipse Galileo
    • SVN Team Core Provider 1.6.5
    • Subversion client adapter
    • Subversion JavaHL 1.6.5
  • svn, version 1.6.5 (r38866)
  • Ubuntu karmic

When I select Checkout from SVN I select the HTTPS repository, but it stays at Pending... forever. When I remove any information from ~/.subversion I get asked for the self-signed certificate, accept it permanently and also check to store my credentials.

I can close the dialog, but Eclipse won't respond anymore and I need to kill it.

I used jconsole to inspect what's going on and found one of the worker threads with this stack trace:

Name: Worker-0
Total blocked: 78  Total waited: 183

Stack trace: 
org.tigris.subversion.javahl.SVNClient.list(Native Method)

Only when I not accept my self-signed certificate permanently (I get asked to accept the certificate every time e.g. when I open a node to select for checkout) it "works".

share|improve this question
up vote 1 down vote accepted

From the JavaHL FAQ :

There is currently a bug in the new support for GNOME keyring in Subversion 1.6. It works OK when using the command line, but not when other users of the libraries use it. Until this is fixed, you can workaround the problem by turning off this feature.

The solution is to put the line

password-stores =

in ~/.subversion/config, effectively disabling the keyring.

This was from an answer from the subclipse mailing list.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .