Bug 480380

This seems to be a problem with how Neon packages kwallet-pam

I had to install libpam-kwallet5 to have the needed pam files

*** Bug 479060 has been marked as a duplicate of this bug. ***

(In reply to Nicolas Fella from comment #1)
> This seems to be a problem with how Neon packages kwallet-pam
> 
> I had to install libpam-kwallet5 to have the needed pam files

Doing that fixed the problem for me as well- both at login and starting Falkon.

I've added back libpam-kwallet5 (along side 6) to the Recommends for plasma-workspace now
https://invent.kde.org/neon/kde/plasma-workspace/-/commit/55eb53b8b89157f9fc2ac1af2fb3c7bf14222e9c

The packaging looks odd to me. libpam-kwallet6 does not actually contain any useful files

(In reply to Nicolas Fella from comment #5)
> The packaging looks odd to me. libpam-kwallet6 does not actually contain any
> useful files

It depends on libpam-kwallet-common which contains files.

But the actually interesting file (pam_kwallet5.so) is in libpam-kwallet5. I don't see why we need multiple packages in the first place. The 5 in pam_kwallet5.so is purely cosmetic

I was hit by this problem after upgrading KDE Neon User Edition to MegaRelease 6.

- `PAM_KWALLET5_LOGIN` environment variable was not set.
- No socket was created at `/run/user/1000/kwallet5.socket`.
- Therefore the `pam_kwallet_init` script did nothing.

Thanks to this thread, I see this was caused by `libpam-kwallet5` being removed in the upgrade, and not being restored in the fixes released on 2 March.

The issue is that `libpam-kwallet5` is marked and treated as a transitional package:

- Its title now has "- transitional" at the end.
- The description says "This package can be removed."
- Its category is "Libraries - Old"
- It depends on `libpam-kwallet6`.

But since `libpam-kwallet5` contains the file of substance that makes everything work, in reality `libpam-kwallet6` depends on `libpam-kwallet5`.

This looks like a clear case of a packaging error to me. Presumably `pam_kwallet5.so` was intended to move to `libpam-kwallet-common`?

Hello,

sorry to chime in.

Wondering if this issue is the root cause of: https://bugs.kde.org/show_bug.cgi?id=480151

Several upgrading users (Plasma 5 -> 6), me included, are facing this annoying issue for which we have to re-enter our kwallet's pwd at every boot just to have our OS connect to the WiFi network.

Maybe it would be good to merge these tickets into one, and also provide a workaround (if possible at all) while the packaging problem gets sorted out.

Thanks a lot in advance! :)

> Several upgrading users (Plasma 5 -> 6), me included, are facing this annoying issue

I haven't upgraded to plasma 6; I'm having and always have had this issue on Plasma 5.
On Manjaro, and I think I had it on OpenSUSE TW too  before I switched to Manjaro.
I'm using X11.

Sorry, didn't mean to create confusion here.

I've read your bug report again and indeed the issue didn't appear after a 5->6 upgrade for you.

Although some other comments in your bug report experienced this on that upgrade path.

This is weird...

(In reply to Andrea Ippolito from comment #9)
> Maybe it would be good to merge these tickets into one, and also provide a
> workaround (if possible at all) while the packaging problem gets sorted out.

You're on openSUSE Tumbleweed, aren't you? I can't see what files are included in which packages using the openSUSE package browser, so all I can do is reiterate the files that you need at a minimum:

- pam_kwallet5.so (in libpam-kwallet5 on Neon)
- pam_kwallet_init (in libpam-kwallet-common on Neon)
- pam_kwallet_init.desktop (in libpam-kwallet-common on Neon)
- plasma-kwallet-pam.service (in libpam-kwallet-common on Neon)

As mentioned previously, even under kf6 the working parts here still have "5" in them.

(In reply to Alex Ball from comment #12)
> (In reply to Andrea Ippolito from comment #9)
> > Maybe it would be good to merge these tickets into one, and also provide a
> > workaround (if possible at all) while the packaging problem gets sorted out.
> 
> You're on openSUSE Tumbleweed, aren't you? I can't see what files are
> included in which packages using the openSUSE package browser, so all I can
> do is reiterate the files that you need at a minimum:
> 
> - pam_kwallet5.so (in libpam-kwallet5 on Neon)
> - pam_kwallet_init (in libpam-kwallet-common on Neon)
> - pam_kwallet_init.desktop (in libpam-kwallet-common on Neon)
> - plasma-kwallet-pam.service (in libpam-kwallet-common on Neon)
> 
> As mentioned previously, even under kf6 the working parts here still have
> "5" in them.

Thanks so much!

I got an answer from the opensuse TW support forums as well (thread here: https://forums.opensuse.org/t/plasma-6-upgrade-kwallet-not-unlocked-at-login/173150/7), apparently they are working on a fix:

https://bugzilla.opensuse.org/show_bug.cgi?id=1221371

> Sorry, didn't mean to create confusion here.

Maybe *I* created some confusion, sorry.
Just to clarify: I understand that for some (if not most) other users the issue appeared only after upgrading. That's why I wanted to chime in to let you know that that wasn't the case for me.

(In reply to php4fan from comment #14)
> > Sorry, didn't mean to create confusion here.
> 
> Maybe *I* created some confusion, sorry.
> Just to clarify: I understand that for some (if not most) other users the
> issue appeared only after upgrading. That's why I wanted to chime in to let
> you know that that wasn't the case for me.

No, no, I definitely did :D

Your report was about Plasma 5 ;)

I just got confused by the follow-up comments saying "me too plasma 6" and since I've already developed a bit of a Plasma 6 tunnel vision following the release for my distro yesterday, I see plasma 6 everywhere now :D

Hi again,

just commenting again to say that at least on opensuse-tumbleweed the problem is solved as of snapshot 20240315.

Bug report was here, for reference:

https://bugzilla.opensuse.org/show_bug.cgi?id=1221371

I wonder if this KDE bug report is still valid at this point @Doug ?

(In reply to Andrea Ippolito from comment #16)
> Hi again,
> 
> just commenting again to say that at least on opensuse-tumbleweed the
> problem is solved as of snapshot 20240315.
> 
> Bug report was here, for reference:
> 
> https://bugzilla.opensuse.org/show_bug.cgi?id=1221371
> 
> I wonder if this KDE bug report is still valid at this point @Doug ?

My problem was fixed with the workaround suggested in comment #1.  Unfortunately, I cannot really check if the problem is fixed in Neon generally without reinstalling at this point.

(In reply to Andrea Ippolito from comment #16)
> I wonder if this KDE bug report is still valid at this point @Doug ?

Expanding on what I said in comment #8, I don't think this Neon bug can be considered fixed until either

- the `libpam-kwallet5` package is marked as substantive/necessary for pam-kwallet functionality as opposed to transitional (the description "This package can be removed" is outright false if you want this to work); OR
- the file `pam_kwallet5.so` (or a new file that does the same thing) is included in one of the packages currently marked as necessary for pam-kwallet functionality: presumably `libpam-kwallet-common` (since it seems to be) but possibly `libpam-kwallet6`.

KDE NOEN with plasma 6.1

Package libpam-kwallet5 provides pam file in wrong location. 
In package it is: /usr/lib/x86_64-linux-gnu/security/pam_kwallet5.so

But, all other pam modules are installed into /lib/x86_64-linux-gnu/security/ , not into /usr/lib ... 

A symbolic link in /lib/x86_64-linux-gnu/security/ to   /usr/lib/x86_64-linux-gnu/security/pam_kwallet5.so makes auto unlock to work again.