What's the procedure?
Is anything happening to get this fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069555
Title:
Failed to take /etc/passwd lock: Invalid argument on upgrade
To manage no
> On my end it only happens on WSL1.
Also WSL1 here.
GitHub Actions only supports WSL1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069555
Title:
Failed to take /etc/passwd lock: Invalid argumen
On my end it only happens on WSL1. Not WSL2 with systemd enabled.
It happens in the postinst script of systemd, that uses the binary
systemd-sysusers. It is in this binary the bug happens. It can be
reproduced by just running the systemd-sysusers binary. It seems to be a
problem for systemd versio
On my end it only happens on WSL1. Not WSL2 with systemd enabled.
It happens in the postinst script of systemd, that uses the binary
systemd-sysusers. It is in this binary the bug happens. It can be
reproduced by just running the systemd-sysusers binary. It seems to be a
problem for systemd versio
On my end it only happens on WSL1. Not WSL2 with systemd enabled.
It happens in the postinst script of systemd, that uses the binary
systemd-sysusers. It is in this binary the bug happens. It can be
reproduced by just running the systemd-sysusers binary. It seems to be a
problem for systemd versio
On my end it only happens on WSL1. Not WSL2 with systemd enabled.
It happens in the postinst script of systemd, that uses the binary
systemd-sysusers. It is in this binary the bug happens. It can be
reproduced by just running the systemd-sysusers binary. It seems to be a
problem for systemd versio
On my end it only happens on WSL1. Not WSL2 with systemd enabled.
It happens in the postinst script of systemd, that uses the binary
systemd-sysusers. It is in this binary the bug happens. It can be
reproduced by just running the systemd-sysusers binary. It seems to be a
problem for systemd versio
On my end it only happens on WSL1. Not WSL2 with systemd enabled.
It happens in the postinst script of systemd, that uses the binary
systemd-sysusers. It is in this binary the bug happens. It can be
reproduced by just running the systemd-sysusers binary. It seems to be a
problem for systemd versio
On my end it only happens on WSL1. Not WSL2 with systemd enabled.
It happens in the postinst script of systemd, that uses the binary
systemd-sysusers. It is in this binary the bug happens. It can be
reproduced by just running the systemd-sysusers binary. It seems to be a
problem for systemd versio
On my end it only happens on WSL1. Not WSL2 with systemd enabled.
It happens in the postinst script of systemd, that uses the binary
systemd-sysusers. It is in this binary the bug happens. It can be
reproduced by just running the systemd-sysusers binary. It seems to be a
problem for systemd versio
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069555
Title:
Fa
11 matches
Mail list logo
