http://bugzilla.opensuse.org/show_bug.cgi?id=989268 http://bugzilla.opensuse.org/show_bug.cgi?id=989268#c2 --- Comment #2 from Episteme PROMENEUR ---

...

Do you have signon-kwallet-extension installed? no

also several kde relative packets about authoring are not installed ktp-approver ktp-auth-handler and if i want to install kde telepathy there is no metapacket telepathy-kde as with opensuse 13.1 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=989268 http://bugzilla.opensuse.org/show_bug.cgi?id=989268#c4 --- Comment #4 from Episteme PROMENEUR --- i installed signon-kwallet-extension then i deleted the google account then a dialog window asks for me to a security mode for kwallet and a password for the wallet then i fill the password then the google account disappears then i click on "create" then i choose "google" then i fill the id and password of my google account then again a window asks for me to fill the password of the "default keyring" according to unlock it note this: i don't remember i supplied any password for initializing this "default keyring". this is a fresh install of leap 42.1 i checked that the password of my google account is recorded in kwallet but not the id! in kwallet there is also a binary data "2/1" -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=989268 http://bugzilla.opensuse.org/show_bug.cgi?id=989268#c6 --- Comment #6 from Wolfgang Bauer --- (In reply to Episteme PROMENEUR from comment #5)

today there were some updates about signon and kde extension but problem still there

What updates from where? I am not aware of any recent updates that should fix anything in this regard. And what problem is still there?

skypeforlinux alpha also uses default keyring!

worst last (53) google-chrome asks for unlocking default keyring then for unlocking kwallet !

And how is this related to this bug report? skypeforlinux and Google Chrome are no KDE applications and are not even provided by openSUSE anyway. If they use kwallet, you need to provide the kwallet password. A way around that is to give your wallet an empty password (so you won't be asked for a password any more), or use pam_kwallet to unlock it automatically on login. If they use gnome-keyring, you need to supply the gnome-keyring password. gnome-keyring should be unlocked automatically on login (via gnome-keyring-pam), but only if you use gdm or lightdm (you could change that in /etc/pam.d/common-session though). If an application uses both, it's a bug in the application I'd say (or a misconfiguration). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=989268 http://bugzilla.opensuse.org/show_bug.cgi?id=989268#c8 --- Comment #8 from Wolfgang Bauer --- (In reply to Episteme PROMENEUR from comment #7)

sorry i sent a bug report to skype and google.

it was just for info.

So what problem does still exist? That you have to enter the GNOME keyring password when creating a Google account? Well, IIRC (I do not use this at all, but have tested it a while ago) the account creation just opens the default web browser to create the account. Maybe this (Google Chrome?) tries to open/use the gnome keyring? I just tried that here and did not get asked for a keyring password. (I don't have Google Chrome installed)

pam_kwallet does not work.

i must still supply the kwallet password after opening a session

I never tried that myself either, but it should work. Did you enable it in the PAM config? And AFAIK, the kwallet password must be the same as your user account password for it to be opened automatically on login. And again, setting an empty password should remove all password requests by kwallet completely. That's how I am using it since 13 years here... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=989268 http://bugzilla.opensuse.org/show_bug.cgi?id=989268#c10 --- Comment #10 from Episteme PROMENEUR --- i made some experiments: chrome asks for gnome keyring hangouts asks for kde keyring gnome keyring package is not a dependency for chrome how do you use map-config to activate pam_kwallet? thanks for kwallet i use pgp key with same password as my login one. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=989268 http://bugzilla.opensuse.org/show_bug.cgi?id=989268#c12 --- Comment #12 from Wolfgang Bauer --- (In reply to Episteme PROMENEUR from comment #10)

i made some experiments: chrome asks for gnome keyring hangouts asks for kde keyring

hangouts is from Google as well, right?

gnome keyring package is not a dependency for chrome

And? That doesn't necessarily mean it is not using it. You wrote yourself that Chrome is asking you for the gnome-keyring password.

how do you use map-config to activate pam_kwallet?

See the included README in /usr/share/doc/packages/pam_kwallet.

for kwallet i use pgp key with same password as my login one.

Then pam_kwallet won't work. You need to use blowfish with the same password as your account. (In reply to Episteme PROMENEUR from comment #11)

...

...

what does it remains regarding why i created the bug report? All.

i go to kde settings then i go to "accounts" then i click "+" then i choose "google" then i fill the id and pwd of my google account then a window opens asking for me a password for "default keyring" then i fill a password then the dialog window disappears.

As I said I don't get a password prompt for a "default keyring" here when I follow the exact same steps.

it's strange i was expecting in a kde environment that kwallet is used.

It depends on the *applications* what they use. This is not something the "kde environment" does. And again, Chrome, Hangouts and skype4linux are not even KDE applications at all. You cannot blame KDE that they do not use kwallet.

* i made this second experiment before any installation of skypeforlinux alpha or chrome.

Was this a fresh user account (without the previous Chrome settings/profile)? Was signon-kwallet-extension installed? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=989268 http://bugzilla.opensuse.org/show_bug.cgi?id=989268#c14 --- Comment #14 from Wolfgang Bauer --- (In reply to Wolfgang Bauer from comment #12)

...

how do you use map-config to activate pam_kwallet?

See the included README in /usr/share/doc/packages/pam_kwallet.

Sorry, I just noticed that it doesn't contain a README file. This should help: https://wiki.archlinux.org/index.php/KDE_Wallet But as I wrote, this will only work with blowfish encryption, not GPG. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=989268 http://bugzilla.opensuse.org/show_bug.cgi?id=989268#c16 Luca Beltrame changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lbeltrame@kde.org --- Comment #16 from Luca Beltrame --- For the record, I think the issue lies in Chromium, and I've seen the issue in Tumbleweed too. What happens is that *even if* KWallet is present and you have chromium-desktop-kde installed, Chromium will *prefer* gnome-keyring if it is running. What one can do is to kill gnome-keyring and remove the package, and this will not happen again. This issue in the amended title also happens with the whole Telepathy stack, not just Google accounts (I've seen it with Jabber). If you have gnome-keyring installed and running, it will prefer it to KWallet. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=989268 http://bugzilla.opensuse.org/show_bug.cgi?id=989268#c18 --- Comment #18 from Wolfgang Bauer --- (In reply to Episteme PROMENEUR from comment #17)

is there any project at freedesktop to unify pasword storage?

Well, there's "Secret Service": https://standards.freedesktop.org/secret-service/ I don't know the state of this though. There also was a KDE project named "KSecretService" which should have enabled KWallet to use the same storage as gnome-keyring (or replace KWallet even) AIUI, but never much came out of it AFAIK, at least it never got released. See https://community.kde.org/KSecretService (not much there), or https://bugs.kde.org/show_bug.cgi?id=313216 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=989268 http://bugzilla.opensuse.org/show_bug.cgi?id=989268#c20 --- Comment #20 from Episteme PROMENEUR --- 42.2b2 problem still there -- You are receiving this mail because: You are on the CC list for the bug.