Bug 1227216

Summary:	pam_config: many things do not work after graphic login
Product:	[openSUSE] openSUSE Distribution	Reporter:	Giacomo Comes <gcomes.obs>
Component:	Basesystem	Assignee:	E-mail List <screening-team-bugs>
Status:	NEW ---	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None
Version:	Leap 15.6
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Giacomo Comes 2024-07-01 05:17:19 UTC

After installing Leap 15.6 I did the first login in KDE and found many issues:
no sound, network manager not working, etc.
The reason was because the process systemd --user was not started.
Normally in the file /etc/pam.d/common-session-pc you will find this line:
  session optional        pam_systemd.so
which take care of starting systemd --user. In my installation such line is missing.
When the rpm systemd is installed the post scriptlet runs:
  pam-config --add --systemd
which take care of adding the pam_systemd.so entry in /etc/pam.d/common-session-pc.
Looking at /var/log/zypp/history I found the following:
# 2024-06-30 23:52:53 systemd-254.13-150600.4.5.1.x86_64.rpm installed ok
# Additional rpm output:
# ERROR: module /lib/security/pam_systemd.so is not installed.
# Running in chroot, ignoring command 'daemon-reexec'
# Creating group 'systemd-journal' with GID 469.
# 
2024-06-30 23:52:53|install|systemd|254.13-150600.4.5.1|x86_64||repo-sle-update|4b4498112e009db2bc50fd1739eaf226e74303f311af987a3488ef95f34cf05e|

When pam-config --add --systemd is executed, if the program does not find the 32bit module (which means if systemd-32bit is not installed before systemd) it stops the execution with an error message and it does not add systemd support in pam.

This behavior is also causing boo#1226123. In tumbleweed pam-config does not throw an error if the 32-bit module is missing, only a warning. I think the same should happen in Leap 15.6

Comment 1 Thorsten Kukuk 2024-07-01 05:59:44 UTC

(In reply to Giacomo Comes from comment #0)

> This behavior is also causing boo#1226123. In tumbleweed pam-config does not
> throw an error if the 32-bit module is missing, only a warning. I think the
> same should happen in Leap 15.6

The only correct solution is to fix your system and install the missing PAM modules.

Comment 2 Thorsten Kukuk 2024-07-01 08:44:43 UTC

No idea why this got assigned to me if comment #1 clearly states that this is not a pam-config bug.

Comment 3 Giacomo Comes 2024-07-01 11:45:22 UTC

The problem happens during the installation. I cannot control the order in which the modules are installed. And because of the issue I described I ended up with a broken system.
Either the rpm systemd should requires the pre installation of systemd-32bit or pam-config should not fail if the 32-bit modules are missing (ad it does on tumbleweed)