Open ArthurBorsboom opened 3 months ago
Any chance of having a look at this issue?
I don't think anythin will happen here in the future. This check was a stop gap that is going to be phased out in benefit of leveraging something like Loki in the future.
Thanks for the update. I will go find another solution.
After updating an Arch Linux distro, this error started to appear.
This looks like a systemd error message and systemd has been updated in this cycle.
upgraded systemd (255.7-1 -> 256.2-1) upgraded systemd-libs (255.7-1 -> 256.2-1) upgraded systemd-sysvcompat (255.7-1 -> 256.2-1)
I am not sure if this is related though.
Any thoughts?