Bug 2038811
Summary: | shadow-utils: Crash in libsubid nss_init if /etc/nsswitch.conf is missing | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Florian Weimer <fweimer> |
Component: | shadow-utils | Assignee: | Iker Pedrosa <ipedrosa> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | medium | ||
Version: | 35 | CC: | ipedrosa, pvrabec, tm |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | shadow-utils-4.9-9.fc35 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-01-23 01:42:20 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
Florian Weimer
2022-01-10 07:49:00 UTC
Can you provide the steps to reproduce the problem? I'm not a podman expert and so far I haven't been able to reproduce it. By the way, I think that upstream already solved this problem in https://github.com/shadow-maint/shadow/pull/474. For me, “podman pull fedora” or “podman system reset” crash. FEDORA-2022-8e62470e3e has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-8e62470e3e FEDORA-2022-8e62470e3e has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-8e62470e3e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-8e62470e3e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-8e62470e3e has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. |