I use Seahorse in Plasma instead of KWallet. However each time I login I have to unlock it manually, although the Login keyring uses the same password as the one for user login. Afaik normally in Gnome this should be unlocked automatically on login. I wonder if this is possible in Plasma too?
I’m pretty sure that there is a rule something like “unlock if Gnome or XFCE”. That’s why it doesn’t unlock for KDE/Plasma.
Ah, okay, I see the rule. It is “auto_start only_if=gdm,gdm-password,lxdm,lightdm” (in one of the files in “/etc/pam.d”).
I’m using “gdm” and it is not unlocking for me. I suppose you could try “lightdm”. But I’m going to guess that it won’t help.
I didn’t know it is controlled by that file. Thanks. Unfortunately adding ‘kdm’ to the list didn’t help.
I’m using “gdm” and it is not unlocking for me.
Should that be reported as a bug then?
I suppose you could try “lightdm”. But I’m going to guess that it won’t help.
I need to stay with Plasma.
I just switched to using “lightdm” for login. And then I logged into KDE/Plasma 5. This was on Tumbleweed.
And the Gnome login keyring was already open.
I don’t know if that will happen on 42.2. I don’t want to reboot my main desktop right now for testing. But it might be worth a try. You might need to first install “lightdm”. Then edit “/etc/sysconfig/displaymanager” to change the “DISPLAYMANAGER=” value to “lightdm”. Then reboot.
Before doing anything let me please check if I understand correctly:
You switched “/etc/sysconfig/displaymanager” to “lightdm” and with that setting you logged into Plasma? How is that possible? Shouldn’t one use kdm for Plasma? Or if lightdm is possible to use in combination with Plasma - wouldn’t that have any negative side effects?
Yes, that works fine. I’ve been using “lightdm” for several years now. I mostly use KDE, currently Plasma 5. I used it because it unlocked the Gnome keyring, and I like to occasionally experiment with Gnome or XFCE.
However, with Leap 42.2, I switched to using “gdm”, because Gnome doesn’t work properly with other login managers.
Shouldn’t one use kdm for Plasma? Or if lightdm is possible to use in combination with Plasma - wouldn’t that have any negative side effects?
It really should be “sddm” for Plasma. But I don’t like “sddm”. I have not run into any problems using “lightdm” or “gdm”, except on Tumbleweed. When using Tumbleweed, and with Plasma-wayland-session installed (if that’s the right name), I can only login into Plasma under Wayland with “sddm”. But Plasma under Wayland is broken, so it isn’t much loss to lose that ability.
So give “lightdm” a try. I think it might do what you want.
It works! Thank you so much!
How exactly did you add ‘kdm’ to the list?
Try to remove the “only_if=gdm,gdm-password,lxdm,lightdm” part completely.
PS: that autostart only_if is for gnome_keyring, no?
I’m not sure how this would be related to seahorse then, seahorse is maybe autostarted differently.
Or are you actually talking about the gnome-keyring?
Of course, like with kwallet, it seems to be possible to set an empty password to avoid any password prompts at all.
See here e.g. https://askubuntu.com/questions/867/how-can-i-stop-being-prompted-to-unlock-the-default-keyring-on-boot (first Google hit).
The question is whether you want that though.
Personally, I am using kwallet with an empty password since 15 years…
Or maybe this helps:
https://wiki.archlinux.org/index.php/GNOME/Keyring#Using_the_keyring_outside_GNOMEand in particular https://wiki.archlinux.org/index.php/KDM#KDM_and_Gnome-keyring
(though IIANM, kdm uses /etc/pam.d/xdm in openSUSE, definitely not /etc/pam.d/kde)
By editing the text file containing it.
Try to remove the “only_if=gdm,gdm-password,lxdm,lightdm” part completely.
Thanks. That worked! Now it auto unlocks with kdm too 
Or are you actually talking about the gnome-keyring?
I suppose so. Afaik seahorse is just the GUI for it, right?
Yes, sure.
I meant what change exactly did you make, how did your modified line look like.
Thanks. That worked! Now it auto unlocks with kdm too
Great!
I suppose so. Afaik seahorse is just the GUI for it, right?
More or less, yes.
But not only, I think.
According to Wikipedia:
Seahorse is a GNOME front-end application for managing PGP and SSH keys.
Sounds more like something like kgpg or kleopatra on the KDE side.
OTOH:
The GNOME Keyring Manager (gnome-keyring-manager) was a user interface for the GNOME Keyring. As of GNOME 2.22, it is deprecated and replaced entirely with Seahorse.[4]](https://en.wikipedia.org/wiki/GNOME_Keyring#cite_note-4)
In any case, it uses the gnome-keyring, and therefore it has to be opened/unlocked.
Thanks a lot.
Just upgraded from 42.2 to 42.3 and removed again the “only_if…” line from /etc/pam.d/common-session
Unfortunately this trick doesn’t seem to produce the desired effect any more - on login the login keyring is not unlocked automatically (using kdm).
Any ideas about a reason/fix?
Just tried to set displaymanager to lightdm but that doesn’t seem to work either.
It works with lightdm if I restore the line in /etc/pam.d/common-session:
session optional pam_gnome_keyring.so auto_start only_if=gdm,gdm-password,lxdm,lightdm
ETA: just like before (when I was using lightdm) it seems logging out doesn’t terminate chromium correctly and upon login and starting it again it says it was not stopped correctly and asks me to restore tabs. I wonder why lightdm is causing this.
Apparently that does still work as you confirmed now in http://bugzilla.opensuse.org/show_bug.cgi?id=1079361 … 
So you probably just did something wrong back then.
Sorry for not responding earlier here, I was busy with other things and somehow forgot this thread.