nut-driver systemd service incorrect
Bug #1979862 reported by
asdasda
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nut (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Upgraded to 22.04 from 20.04
```
$ cat /lib/systemd/
[Unit]
Description=Network UPS Tools - power device driver controller
After=local-
Wants=systemd-
StopWhenUnneede
[Service]
ExecStart=
ExecStop=
Type=forking
```
It hangs on start for 2 minutes now and logs say:
udevadm[1423]: systemd-
I've checked source and there's no 'Wants' line there
https:/
To post a comment you must log in.
Hello asdasda and thanks for this bug report. You don't see a Wants= line in nut-driver. service. in because that's added using a quilt patch, see [1]. However I don't think that's the reason why you are seeing the 2 minute delay this bug report is about.
I tried to reproduce the problem in a Jammy LXD VM by installing nut and rebooting the system, but I didn't incur in the delay. However I had no UPS definition, so the service simply failed to start very quickly.
What we need here in order to confirm this is a bug in Ubuntu and begin working on it is a minimal set of steps to reproduce the issue from a clean Ubuntu system. This could be an LXD VM you can start with
lxc launch ubuntu:jammy --vm
[wait]
lxc exec <vm name> bash
(An LXD container is not enough as the package needs to interact with /sys).
As we need more information to move this forward I'm going to set this bug report as Incomplete for now.
[1] https:/ /git.launchpad. net/ubuntu/ +source/ nut/tree/ debian/ patches/ 0004-fix- systemd- service. patch?h= ubuntu/ jammy