On Tue, Nov 3, 2009 at 9:38 PM, Sebastien Bacher <[email protected]> wrote:
> Thank you for your bug report, are you sure you are using the right > keymap with no capslock enabled? could you run ssh -vvv and get details > on what is happening there? > That was a quick response! i'm not using SSH here - the svn repos having this problem are https rather than svn+ssh (e.g. Google Code), authenticated against credentials the svn client stored 1+ years ago. If i use kdesvn i do not get prompted for login info and can commit normally. If i use the command-line client, the keyring manager wants something from me and i have no idea what. i have verified that it's happening on all of my repos which use https, e.g.: step...@jareth:~/cvs/qboard/trunk$ svn ci -m "just testing gnome-keyring thingie" config.qmake Password for 'login' GNOME keyring: Password for 'login' GNOME keyring: svn: Commit failed (details follow): svn: OPTIONS of 'https://qboard.googlecode.com/svn/trunk': authorization failed: Could not authenticate to server: rejected Basic challenge ( https://qboard.googlecode.com) step...@jareth:~/cvs/qboard/trunk$ svn info Path: . URL: https://qboard.googlecode.com/svn/trunk Repository Root: https://qboard.googlecode.com/svn ... i've tried killing the keyring manager process, but that doesn't solve the problem - it's apparently getting re-started as part of the authentication process. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ -- gnome-keyring demands unspecified password, breaking svn commits https://bugs.launchpad.net/bugs/473139 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
