[opensuse-buildservice] Getting osc to use Plasma5's kwalletd5?
Dear all, when I log into my Tumbleweed machine with Plasma5, I get asked for my kwallet password (ssh-add wants to unlock my ssh key and uses the password in kwallet). After that kwallet should be unlocked, I guess. But osc still keeps asking me for my kwallet password (via a kwallet unlock popup), and after using osc I have a kwalletmanager icon in the systray. So I guess it is using a different kwallet, maybe the one from kde4? Any way to tell osc which one to use? So I do not have to enter my password multiple times. Any hints are highly appreciated... Johannes
On Okt 10 2016, Johannes Kastl
Any way to tell osc which one to use?
osc uses python-keyring. If something is missing it needs to be added there, I'd guess. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 2016-10-10 22:15:20 +0200, Andreas Schwab wrote:
On Okt 10 2016, Johannes Kastl
wrote: Any way to tell osc which one to use?
osc uses python-keyring. If something is missing it needs to be added there, I'd guess.
It is possible to configure a specific keyring backend via the /home/<username>/.local/share/python_keyring/keyringrc.cfg config file. [backend] default-keyring = keyring.backends.kwallet.DBusKeyring I just had a quick look at the DBusKeyring code (python-keyring-9.3.1) and it seems that it already uses kwalletd5... Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Marcus, thanks for the answer. On 14.10.16 13:04 Marcus Hüwe wrote:
It is possible to configure a specific keyring backend via the /home/<username>/.local/share/python_keyring/keyringrc.cfg config file.
[backend] default-keyring = keyring.backends.kwallet.DBusKeyring
I'll try to set this and see what happens.
I just had a quick look at the DBusKeyring code (python-keyring-9.3.1) and it seems that it already uses kwalletd5...
I will dig deeper maybe kill the kde4 wallet, maybe there is something hidden there. Johannes
On 14.10.16 13:04 Marcus Hüwe wrote:
It is possible to configure a specific keyring backend via the /home/<username>/.local/share/python_keyring/keyringrc.cfg config file.
[backend] default-keyring = keyring.backends.kwallet.DBusKeyring
Works like a charm. Even before uninstalling kwalletmanager (without the 5)... Johannes
participants (3)
-
Andreas Schwab
-
Johannes Kastl
-
Marcus Hüwe