No need to log out or reboot.
sudo dnf upgrade --advisory=FEDORA-2022-f38f479b8f
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.
This update can be pushed to stable now if the maintainer wishes
zbyszek edited this update.
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.
@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.
Karma has been reset.
Still boots here on 2 machines.
Works great! LGTM! =)
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 --user unusable.
× firstname.lastname@example.org - User Runtime Directory /run/user/1000
Loaded: loaded (/usr/lib/systemd/system/user-runtime-dir@.service; static)
Active: failed (Result: exit-code) since Wed 2022-01-19 16:41:21 EET; 4min 32s ago
Process: 1540 ExecStart=/usr/lib/systemd/systemd-user-runtime-dir start 1000 (code=exited, status=1/FAILURE)
Main PID: 1540 (code=exited, status=1/FAILURE)
tammi 19 16:41:21 marty-t460 systemd: Starting User Runtime Directory /run/user/1000...
tammi 19 16:41:21 marty-t460 systemd-user-runtime-dir: mmap: Permission denied
tammi 19 16:41:21 marty-t460 systemd-user-runtime-dir: Failed to mount per-user tmpfs directory /run/user/1000: No such file or directory
tammi 19 16:41:21 marty-t460 systemd: email@example.com: Main process exited, code=exited, status=1/FAILURE
tammi 19 16:41:21 marty-t460 systemd: firstname.lastname@example.org: Failed with result 'exit-code'.
tammi 19 16:41:21 marty-t460 systemd: Failed to start User Runtime Directory /run/user/1000.
@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.
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2019 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.