My daily system just broke after the most recent update (updated 2020-01-19). Should have tested it in a VM first. reboot does not even work and it sits at the boot loader forever. I will try reverting the update (boot from usb), but some packages are now missing in the repo 🙁
To reproduce (so simple I am wondering if this was even tested prior to release).
Installed Solus Budgie 4.0 from ISO in a VM.
Packages update fine... then:
[✗] Reloading systemd configuration failed
A copy of the command output follows:
Failed to reload daemon: Access denied
[✗] Re-executing systemd failed
A copy of the command output follows:
Failed to reload daemon: Access denied
systemd-tmpfiles --create
/usr/lib64/tmpfiles.d/NetworkManager.conf:2: Line references path below legacy directory /var/run/, updating /var/run/NetworkManager → /run/NetworkManager; please update the tmpfiles.d/ drop-in file accordingly.
/usr/lib64/tmpfiles.d/NetworkManager.conf:3: Line references path below legacy directory /var/run/, updating /var/run/NetworkManager/devices → /run/NetworkManager/devices; please update the tmpfiles.d/ drop-in file accordingly.
/usr/lib64/tmpfiles.d/spice-vdagent.conf:1: Line references path below legacy directory /var/run/, updating /var/run/spice-vdagentd → /run/spice-vdagentd; please update the tmpfiles.d/ drop-in file accordingly.
/usr/lib64/tmpfiles.d/spice-vdagentd.conf:2: Line references path below legacy directory /var/run/, updating /var/run/spice-vdagentd → /run/spice-vdagentd; please update the tmpfiles.d/ drop-in file accordingly.
[/usr/lib64/tmpfiles.d/spice-vdagentd.conf:2] Duplicate line for path "/run/spice-vdagentd", ignoring.
Nothing happens.