*** This bug is a duplicate of bug 416825 ***
https://bugs.launchpad.net/bugs/416825
See bug duplicate for more complete information but posting for
posterity (and because I found this through the same SVN problem -- even
if that's not the root cause).
1) Run the "Passwords and keys" utility
*** This bug is a duplicate of bug 416825 ***
https://bugs.launchpad.net/bugs/416825
I hit this (or very similar) problem on 2 machines, after i have been
using & storing password in gnome-keyring
I think my problem is because i changed password on the user using the "passwd"
command,
and it
*** This bug is a duplicate of bug 416825 ***
https://bugs.launchpad.net/bugs/416825
Well, if i leave out other parameters it does show the keyring message
again even if i provide the login credentials.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
*** This bug is a duplicate of bug 416825 ***
https://bugs.launchpad.net/bugs/416825
To be perfectly clear about this: I used the --password and --username
parameters and it still fails. In that case it should NOT use anything
related to the keyring.
--
You received this bug notification bec
*** This bug is a duplicate of bug 416825 ***
https://bugs.launchpad.net/bugs/416825
Got the issue with Ubuntu 11.10. And I only see the gnome keyring
message if I don't provide my own login parameters in the command. I
tried some parameters in the ~/.subversion/config but no working svn so
fa
*** This bug is a duplicate of bug 416825 ***
https://bugs.launchpad.net/bugs/416825
I am seeing this as "Password for '(null)' GNOME keyring".
I have no idea what is a keyring in general, and what is the '(null)' keyring
in particular.
I typed in my sudo password, and it worked, but svn must
*** This bug is a duplicate of bug 416825 ***
https://bugs.launchpad.net/bugs/416825
** This bug has been marked a duplicate of bug 416825
gnome-keyring passwd should be changed on system password change
* You can subscribe to bug 416825 by following this link:
https://bugs.launchpad.net/
I observe this in a 10.10 installation, shortly after I changed my password
with "passwd".
It does seem to be similar to 416825, but that seems to be specific to Ubuntu
1, and
this isn't.Probably the same underlying problem though -- the keyring
somehow didn't
notice I changed my password.
Did you recently change your system login password? This might be related to
#416825.
Try entering your old system login password to the Gnome keyring dialog.
--
gnome-keyring demands unspecified password, breaking svn commits
https://bugs.launchpad.net/bugs/473139
You received this bug notifica
** Changed in: gnome-keyring
Importance: Unknown => Medium
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
I've seen this too, on 10.04.
Editing ~/.subversion/config as suggested in comment #23 fixes it, takes
gnome keyring out the loop.
I also have to go with comment #28 here, I'm not sure what problems
gnome-keyring is trying to solve, but they are not the ones I have. I've
already had to turn off i
same problem here with my Kubuntu lucid.
I haven't the .gnome2/keyrings/* and adding the [auth]\npassword-stores = \n
didn't change anything on my ubuntu.
It's strange, it works well on my old computer (which has an upgrade to lucid)
but with my fresh new install of lucid on my laptop, I have thi
Have this issue on Lucid 10.04 too
(without KDE or GNOME installed, only dependencies like libraries/utils, i.e.
gnome-keyring)
$ svn log -rhead
Passwort für GNOME-Schlüsselring »(null)«:
solved by rm ~/.gnome2/keyrings/login.keyring
(although it didn't ask for 'login' explicitly ...)
--
gnom
I have the exact same problem, deleting the login keyring makes svn fall
back to the ~/.subversion/auth plain-text storage.
Gnome-keyring needs a manual which explains how to add password groups
and SVN needs some info on where/how it reads off gnome-keyring.
Only commits need passwords for me, s
same problem here
echo - "[auth]\npassword-stores = \n" >~/.svn/config did not work
solved problem by rm ~/.gnome2/keyring/*
after breaking ssh-agent, gnome-keyring just earned itself a second
scoring point on my "useless daemons creating problems" list. is it
really necessary that so many packa
i'm at ubuntu lucid; no ~/.gnome/keyring/.. at all; getting
Password for '(null)' GNOME keyring:
and failure afterwards on any svn server with http/https.
a line:
password-stores =
in the ~/.subversion/config fixes it (as Piotr Piastucki suggested above).
--
gnome-keyring demands unspecified pas
This bug is also present in updated Kubuntu 10.04 beta.
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
I also encountered the problem doing a checkout to a subversion
repository (Google code) from inside the netbeans 6.8 IDE. And under my
Ubuntu 9.10 (upgraded from 9.04 clean install) subversion access fails.
There is no prompt at all for a keyring password. There is just a
credentials failure:
OPT
One correction, the file correct file to modify is ~/.subversion/config
--
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
Bugs, which is subscribed to Ubuntu.
--
ubunt
In order to prevent SVN from asking you for 'login' keyring password you may
try to add the following line to [auth] section in ~/.subversion/conf :
password-stores =
E.g.
--- cut ---
### saving of *new* credentials; it doesn't invalidate existing
### caches. (To do that, remove the cache file
Same problem here, after updating to 9.10. Deleting login.keyring fixed
it for me too, allowing me to commit without entering any password.
--
gnome-keyring demands unspecified password, breaking svn commits
https://bugs.launchpad.net/bugs/473139
You received this bug notification because you are
> rm ~/.gnome2/keyrings/login.keyring
this worked for me too. Thanks.
Could be that the current SVN client (1.6.5) is not completely
compatible with older SVN servers. I know I did not have this problem
in Ubuntu 9.04 which used SVN 1.5.4 or something around there.
--
gnome-keyring demands uns
upstream commented saying it's a subversion issue
** Changed in: gnome-keyring (Ubuntu)
Status: Confirmed => Triaged
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged => Confirmed
** Package changed: gnome-keyring (Ubuntu) => subversion (Ubuntu)
** Changed in: subversion (Ubun
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged => Confirmed
--
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
Bugs, which is subscribed to Ubuntu.
--
ubun
The bug report to https://bugzilla.gnome.org/show_bug.cgi?id=600758 is
marked as resolved, apparently passing it off as a subversion problem.
I encountered the problem doing a checkin to a subversion repository
from inside the netbeans 6.7.1 IDE. Under ubuntu 9.0.4 this worked fine.
Under 9.10 suc
An update: My machine was rebooted because of a power outage and next
time svn commit worked without any of the work-around-s.
--
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
** Changed in: gnome-keyring (Ubuntu)
Status: New => Triaged
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged => New
** Changed in: gnome-keyring (Ubuntu)
Status: New => Triaged
** Also affects: gnome-keyring via
https://bugzilla.gnome.org/show_bug.cgi?id=600758
I
i have reported this "upstream" at:
https://bugzilla.gnome.org/show_bug.cgi?id=600758
and tagged it as gnome-keyring. Maybe they will know where to categorize
it.
Merci, Sebastien!
** Bug watch added: GNOME Bug Tracker #600758
https://bugzilla.gnome.org/show_bug.cgi?id=600758
--
gnome-keyr
I'm still not sure to understand the issue and why gnome-keyring would
ask for a password on the command line but upstream could known better
though
--
gnome-keyring demands unspecified password, breaking svn commits
https://bugs.launchpad.net/bugs/473139
You received this bug notification becaus
On Wed, Nov 4, 2009 at 11:02 PM, Sebastien Bacher
wrote:
> The issue is an upstream one and it would be nice if somebody having it
> could send the bug the to the people writting the software
> (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)
>
It seems like it _might_ be a distro-specific configur
The issue is an upstream one and it would be nice if somebody having it
could send the bug the to the people writting the software
(https://wiki.ubuntu.com/Bugs/Upstream/GNOME)
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete => New
--
gnome-keyring demands unspecified password, b
> rm ~/.gnome2/keyrings/login.keyring
this worked for me too. Thanks.
> the restriction is not wanted, not sure what is going on there bug you
can choose to cache your ssh key in gnome-keyring in which case the ssh
agent will not to unblock the keyring to access it, I've not seen
command line pro
On Wed, Nov 4, 2009 at 2:12 AM, pleiades wrote:
> I was experiencing this issue and I resolved it as follows:
>
> rm ~/.gnome2/keyrings/login.keyring
>
After a reboot i was having the problem again (forgot to unset SSH_AUTH_SOCK
in my login script, so i'm not sure if that's a long-term fix or no
33 matches
Mail list logo
