Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

runtime-cleanup: Do not purge pam binaries #1385

Closed
wants to merge 1 commit into from

Conversation

jexposit
Copy link

@jexposit jexposit commented Mar 6, 2024

In order to migrate from X.Org to Wayland [1], GNOME Kiosk needs to be run in a new PAM session.

After an update in systemd, the session is failing to start because the PAM binaries are not found with the following error:

Starting user@0.service - User Manager for UID 0...
pam_unix(systemd-user:account): helper binary execve failed: No such file or directory
pam_unix(systemd-user:account): helper binary execve failed: No such file or directory
PAM failed: Authentication service cannot retrieve authentication info
user@0.service: Failed to set up PAM session: Operation not permitted

Do not remove the PAM binaries in /usr/sbin to avoid this issue.

[1] rhinstaller/anaconda#5485

In order to migrate from X.Org to Wayland [1], GNOME Kiosk needs to be
run in a new PAM session.

After an update in systemd, the session is failing to start because the
PAM binaries are not found with the following error:

    Starting user@0.service - User Manager for UID 0...
    pam_unix(systemd-user:account): helper binary execve failed: No such file or directory
    pam_unix(systemd-user:account): helper binary execve failed: No such file or directory
    PAM failed: Authentication service cannot retrieve authentication info
    user@0.service: Failed to set up PAM session: Operation not permitted

Do not remove the PAM binaries in /usr/sbin to avoid this issue.

[1] rhinstaller/anaconda#5485
Signed-off-by: Martin Kolman <mkolman@redhat.com>
Signed-off-by: José Expósito <jexposit@redhat.com>
Copy link
Contributor

@bcl bcl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks ok to me. FWIW I'd prefer to do a new lorax build after whatever other changes are needed are in, instead of a new build for each PR. So you may need to patch locally until everything is sorted out.

@bcl
Copy link
Contributor

bcl commented Mar 6, 2024

Tests still failing because new python3-coveralls hasn't hit all the mirrors yet (I assume).

@jexposit
Copy link
Author

jexposit commented Mar 6, 2024

Sure, for the GNOME Remote Desktop work @M4rtinK is doing, he will have to open another PR to preserve libgsm.so* and he'll need #1384 as well. I'll let you coordinate on building the new image.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 8169754312

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 43.521%

Totals Coverage Status
Change from base Build 7964413895: 0.0%
Covered Lines: 1614
Relevant Lines: 3500

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants