FEDORA-2026-f5293aa6a6 — unspecified update for systemd

obsolete

systemd-260~rc1-1.fc45

FEDORA-2026-f5293aa6a6 created by zbyszek a month ago for Fedora 45

Automatic update for systemd-260~rc1-1.fc45.

Changelog

* Wed Feb 25 2026 Zbigniew Jędrzejewski-Szmek <zbyszek@amutable.com> - 260~rc1-1
- Version 260~rc1
- See https://raw.githubusercontent.com/systemd/systemd/v260-rc1/NEWS. Too
  many changes to list or discuss here.
* Wed Feb 25 2026 Luca Boccassi <luca.boccassi@gmail.com> - 259.1-2
- Install /usr/lib/systemd/boot/hwids/ in ukify package

This update was automatically created

a month ago

This update's test gating status has been changed to 'waiting'.

a month ago

This update's test gating status has been changed to 'failed'.

a month ago

nixuser commented & provided feedback a month ago

karma

Looks OK. System didn't break and basic stuff works after rebooting. Tested in a VirtualBox guest.

adamwill commented & provided feedback a month ago

karma

It looks like switching to any VT other than 1 gives a blank screen, in openQA testing.

zbyszek commented a month ago

audit: type=1400 audit(1772063918.935:9): avc:  denied  { create } for  pid=1 comm="systemd" name="io.systemd.Resolve.Monitor" scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:var_run_t:s0 tclass=lnk_file permissive=0
systemd[1]: systemd-resolved-monitor.socket: Failed to create symlink /run/systemd/resolve/io.systemd.Resolve.Monitor → /run/varlink/registry/io.systemd.Resolve.Monitor, ignoring: Permission denied

The message is borked: https://github.com/systemd/systemd/pull/40839 We'll need to adjust the selinux policy to allow this. But it's a new feature that is not used for anything and the failure should not cause problems.

Not sure why VT switching would be affected. I don't recall patches related to that, but I'll take a list of the commits again.

This update has been obsoleted by systemd-260~rc1-5.fc45.

a month ago

Please log in to add feedback.

Metadata

Type

unspecified

Karma

Signed

Content Type

RPM

Test Gating

failed

Autopush Settings

Unstable by Karma

-3

Stable by Karma

disabled

Stable by Time

0 days

Thresholds

Minimum Karma

Minimum Testing

0 days

Dates

submitted

a month ago

in testing

a month ago

Builds

systemd-260~rc1-1.fc45

Automated Test Results

For help debugging failed Fedora CI tests (fedora-ci.*), contact the Fedora CI team.
For help debugging failed Fedora CoreOS tests (coreos.*), contact the Fedora CoreOS team.
For help debugging failed openQA tests (update.*), contact the Fedora Quality team, who will usually investigate and diagnose all failures within 24 hours.

failed