Create /etc/resolv.conf symlink if nothing is present yet (#2032085)
Add missing requirements for libfido2 and libtss2 (#1975827)
Allow mprotect(2), arch_prctl(2) in @default seccomp filter, bpf(2) and /proc
for systemd-udev (#2027627)
Various documentation fixes (#1926323)
Fix sysusers without /proc (#2036217)
Various fixes to condition handling (#1919538)
Bugfixes for the manager, systemd-networkd, systemd-journald and journalctl,
systemd-analyze, systemd-resolved, systemd-homed, shell completions,
systemd-detect-virt on MS Hyper-V, nss modules
Ordering of various units during early boot and shutdown is adjusted to fix
some corner cases
Maximum numbers of files are bumped for /dev and /tmp
fstab-generator now ignores root-on-nfs/cifs/iscsi and live (#2037233)
CVE-2021-3997, #2024639: systemd-tmpfiles would exhaust the stack and crash
during excessive recursion on a very deeply nested directory structure.
Some minor documentation fixes and a fix for journalctl
Make systemd-xdg-autostart-service ignore missing condition check binary
(related to #2038750, but does not fix it)
@zbyszek : I can confirm what @thesourcehim reported ... The system boots into emergency mode.
I checked the logs in emergency mode, but couldn't find something useful to report in a bug report.
Unfortunately I don't know what has been changed in the packages that causes this behavior.
For now I have reverted back to the stable version and everything works without issues again.
@zbyszek : Unfortunately not ... I always remove the /var/log/journal directory after the system installation.
Maybe @thesourcehim makes use of journal archiving, and can give you the log details you are asking for ?
@harrymichal: this update has gone stable a few days ago, so commenting here is not going to be effective. Open a bug instead. This looks like a selinux issue, please include avc logs and information about versions of systemd and selinux policy.
This update has been submitted for testing by zbyszek.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
Works.
This update can be pushed to stable now if the maintainer wishes
zbyszek edited this update.
zbyszek edited this update.
This update's test gating status has been changed to 'failed'.
System enters emergency mode on boot asking for root password. Pressing Ctrl+D allows to boot normally though.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
This update's test gating status has been changed to 'passed'.
@thesourcehim: please file a bug in bugzilla. It's hard to say what the problem is just from this one snippet.
@zbyszek : I can confirm what @thesourcehim reported ... The system boots into emergency mode.
I checked the logs in emergency mode, but couldn't find something useful to report in a bug report.
Unfortunately I don't know what has been changed in the packages that causes this behavior.
For now I have reverted back to the stable version and everything works without issues again.
OK, can you at least paste the full logs from the failed boot somewhere?
@zbyszek : Unfortunately not ... I always remove the /var/log/journal directory after the system installation.
Maybe @thesourcehim makes use of journal archiving, and can give you the log details you are asking for ?
@zbyszek : In case it helps you ... These packages are currently installed.
Confirming what @thesourcehim and @clnetbox experienced, I opened a bug: https://bugzilla.redhat.com/show_bug.cgi?id=2039888
This update has been unpushed.
zbyszek edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by zbyszek.
zbyszek edited this update.
This update has been pushed to testing.
Still boots here on 2 machines.
Works great! LGTM! =)
This update can be pushed to stable now if the maintainer wishes
Works
The system boots successfully without issues now. Thanks @zbyszek !
is it worth to push it to stable?
with 249.9-1 all is fine
This update has been submitted for stable by zbyszek.
This update has been pushed to stable.
The user-runtime-dir.service fails on Fedora Silverblue making Wayland unavailable and
systemd --userunusable.@harrymichal: this update has gone stable a few days ago, so commenting here is not going to be effective. Open a bug instead. This looks like a selinux issue, please include avc logs and information about versions of systemd and selinux policy.
@harrymichal There is a lot of trouble with the two latest selinux-policy releases 35.9 and 35.10 ...
You may want to check out
https://bodhi.fedoraproject.org/updates/FEDORA-2022-41fa7610dd.If you have installed one of them, downgrade to version 35.8, and check if the problem still occurs.