Open brasswood opened 2 hours ago
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
/question
Odd that would happen in a package upgrade.
Have you tried the following?
sudo systemctl unmask systemd-binfmt.service
sudo systemctl start systemd-binfmt.service
systemctl status systemd-binfmt.service
and optionally:
sudo systemctl enable systemd-binfmt.service
if you want to run on each start.
@sirredbeard Odd that I would get that error message from a package upgrade, or odd that a package upgrade would mask the service? I'm not actually sure what caused the service to get masked, though I'm fairly sure I didn't manually do it.
The link was made on September 29, 2023 so I'm looking through logs from that date to see if anything happened.
Strangely, the link was made 11 seconds before journald logs begin. Could this have happened if I upgraded from WSL 1 to WSL 2 at that time?
I suppose I will unmask the service and hope that nothing breaks.
I noticed today that apt upgrade gave me the message
Failed to restart systemd-binfmt.service: Unit systemd-binfmt.service is masked.
What happened?