Bug 1905795

Summary:	su and sudo crashes after updates from updates-testing
Product:	[Fedora] Fedora	Reporter:	laolux
Component:	pam	Assignee:	Iker Pedrosa <ipedrosa>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	33	CC:	besser82, ipedrosa, jonathan, kzak, siddharth, tmraz
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-14 11:04:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description laolux 2020-12-09 05:26:48 UTC

Description of problem:
Util-linux crashes after installing the latest packages from updates-testing. abrt reports that util-linux quit unexpectedly whenever I try to use su or sudo.
su and sudo themselves crash with segmentation fault.

Version-Release number of selected component (if applicable):


How reproducible:
Install updates from updates-testing, potentially reboot, try to use sudo

Steps to Reproduce:
1. install latest updates from updates-testing
2. in terminal, run sudo ls (or any other command with sudo)

Actual results:
sudo fails with segmentation fault (core dumped) and abrt reports that util-linux quit unexpectedly

Expected results:
ls prints output and util-linux does not quit unexpectedly

Additional info:
I do not recall what packages were updated using dnf --enablerepo=updates-testing update, but looking at bodhi it seems like util-linux was NOT updated. Rather, it seems like an update to another package causes util-linux to malfunction.

Comment 1 Karel Zak 2020-12-09 11:50:44 UTC

From your description, it seems the problem is sudo(8) or/and su(1), right? 

su(1) is from util-linux package and sudo(8) is another (alone) package -- the packages share PAM only. Can you verify PAM update?

Comment 2 Siddharth 2020-12-09 12:01:50 UTC

hi, yes there are some updates and also 

systemctl status sssd-pam.service
● sssd-pam.service - SSSD PAM Service responder
     Loaded: loaded (/usr/lib/systemd/system/sssd-pam.service; indirect; vendor preset: disabled)
     Active: inactive (dead)
       Docs: man:sssd.conf(5)


    Upgrade  fprintd-pam-1.90.6-1.fc34.x86_64                                   @rawhide
    Upgraded fprintd-pam-1.90.1-2.fc33.x86_64                                   @@System
    Upgrade  pam-1.5.1-2.fc34.x86_64                                            @rawhide
    Upgraded pam-1.5.1-1.fc34.x86_64                                            @@System
    Upgrade  pam-kwallet-5.20.4-1.fc34.x86_64                                   @rawhide
    Upgraded pam-kwallet-5.20.3-1.fc34.x86_64                                   @@System
    Upgrade  systemd-pam-247.1-1.fc34.x86_64                                    @rawhide
    Upgraded systemd-pam-247-1.fc34.x86_64                                      @@System
  17 Failed to try-restart sssd-pam.service: Operation refused, unit sssd-pam.service may be requested by dependency only (it is configured to refuse manual start/stop).
  18 See system logs and 'systemctl status sssd-pam.service' for details.

Comment 3 Siddharth 2020-12-09 12:08:12 UTC

dnf history :
Scriptlet output:
---
---
  11 Failed to try-restart sssd-autofs.service: Operation refused, unit sssd-autofs.service may be requested by dependency only (it is configured to refuse manual start/stop).
  12 See system logs and 'systemctl status sssd-autofs.service' for details.
  13 Failed to try-restart sssd-nss.service: Operation refused, unit sssd-nss.service may be requested by dependency only (it is configured to refuse manual start/stop).
  14 See system logs and 'systemctl status sssd-nss.service' for details.
  15 Failed to try-restart sssd-pac.service: Operation refused, unit sssd-pac.service may be requested by dependency only (it is configured to refuse manual start/stop).
  16 See system logs and 'systemctl status sssd-pac.service' for details.
  17 Failed to try-restart sssd-pam.service: Operation refused, unit sssd-pam.service may be requested by dependency only (it is configured to refuse manual start/stop).
  18 See system logs and 'systemctl status sssd-pam.service' for details.
  19 Failed to try-restart sssd-ssh.service: Operation refused, unit sssd-ssh.service may be requested by dependency only (it is configured to refuse manual start/stop).
  20 See system logs and 'systemctl status sssd-ssh.service' for details.
  21 Failed to try-restart sssd-sudo.service: Operation refused, unit sssd-sudo.service may be requested by dependency only (it is configured to refuse manual start/stop).
  22 See system logs and 'systemctl status sssd-sudo.service' for details.

Comment 4 Siddharth 2020-12-09 19:29:02 UTC

hi, this is duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1905667

Comment 5 laolux 2020-12-10 01:54:48 UTC

(In reply to Karel Zak from comment #1)
> From your description, it seems the problem is sudo(8) or/and su(1), right? 
> 

Yes, sudo and su both fail with segfault. Only su creates an abrt message about util-linux failing.
sudo version is 1.9.2-1
util-linux version is 2.36-3

> su(1) is from util-linux package and sudo(8) is another (alone) package --
> the packages share PAM only. Can you verify PAM update?

pam did not receive an update recently I think, as it is from the updates repo. However, fprintd-pam is from updates-testing.
pam version: 1.4.0-10
fprintd-pam version: 1.90.6-1

Now I would like to try whether downgrading fprintd-pam solves the problem, but having a default fedora desktop install means that I have no root password set and no ssh server running. So I would probably have to boot a live image and set a root password :-|

Comment 6 Karel Zak 2020-12-14 11:04:53 UTC


*** This bug has been marked as a duplicate of bug 1905667 ***