frankly can't you do a "systemctl daemon-reload" and look in yours logs before blowing out such stuff to updates? [root@rh:~]$ system-errors.sh Jan 6 19:03:20 rh systemd[1]: /usr/lib/systemd/system/haveged.service:32: Failed to parse system call, ignoring: newuname SystemCallFilter=@system-service newuname
FEDORA-2022-3fbf2cf85c has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-3fbf2cf85c
Hmm, I have tested and it has worked fine for me. See https://github.com/jirka-h/haveged/issues/63 In any case, as I got more reports of the newuname causing problems, I have built a new package with the newuname removed. https://koji.fedoraproject.org/koji/taskinfo?taskID=80996907 https://bodhi.fedoraproject.org/updates/FEDORA-2022-3fbf2cf85c Please give it a try. It works fine for me. Thanks Jirka
FEDORA-2022-3fbf2cf85c has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-3fbf2cf85c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-3fbf2cf85c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-3fbf2cf85c has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.