It has always worked in the past; when svn was run, I got a prompt to unlock the default keyring (I run in SSH + X forwarding, so that doesn't happen automatically on login). That is why I expected the lock message to come from KWallet.
Yes, libpam-gnome-keyring is installed (but I've never managed to have it work for SSH+X). [investigates further] Hmmm. Looking at /var/log/messages, it looks like it IS trying to do something with the keyring; when I enter the password, I see Jun 12 15:27:54 leeloo org.gnome.keyring.SystemPrompter[15144]: Unable to init server: Could not connect: Connection refused Jun 12 15:27:54 leeloo gcr-prompter[15427]: cannot open display: Jun 12 15:27:54 leeloo gnome-keyring-d[15208]: couldn't create system prompt: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.keyring.SystemPrompter exited with status 1 appear. The same happens with Seahorse, which fails to unlock the keyring. However, I don't think I updated any packages alongside subversion, so this is an odd change in behaviour. (It's also odd that svn --version doesn't report GNOME Keyring support.) [investigates further] Looks like this may in part be a DBus thing instead. Based on https://bbs.archlinux.org/viewtopic.php?id=202754 I ran dbus-update-activation-environment --systemd DISPLAY. Running "svn up" after that still prompted me for my SVN password first, but then popped up a window asking for a password to unlock the keyring. A further "svn up" just ran without a password prompt. Looks like some backend changes happened somewhere which dropped support for non-GUI credential prompting, making it look as though SVN wasn't using GNOME keyring. -----Original Message----- From: James McCoy [mailto:[email protected]] Sent: Tuesday, June 12, 2018 3:04 PM To: Tim Van Holder <[email protected]>; [email protected] Subject: Re: Bug#901387: subversion: GNOME Keyring support is missing On Tue, Jun 12, 2018 at 01:31:46PM +0200, Tim Van Holder wrote: > After updating subversion to the current version, it has stopped using > GNOME Keyring. > > `svn --version` also only lists > * Plaintext cache in $HOME/.subversion > * GPG-Agent > * KWallet (KDE) > > as supported credential caches. The reporting appears to be broken regardless of whether GNOME Keyring support is used. > Performing an authenticated operation now prompts for an SVN password > each time (as opposed to a once-only request for the password to use > to unlock the > keyring) and then reports > > ** Message: Remote error from secret service: > org.freedesktop.Secret.Error.IsLocked: Cannot create an item in a > locked collection > > before continuing with the SVN operation. It's trying to use the keyring, but the keyring is locked. Based on that, I would assume you have something installed (likely the gnome-keyring package) which provides /usr/share/dbus-1/services/org.freedesktop.secrets.service. I'm not sure how one normally unlocks the keyring, but it seems like libpam-gnome-keyring may be useful here. Is that installed? Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
