Work out some way of automatically testing this thing!

[grodin]

Testing this is a real pain, since it has to connect to logind via dbus, so there's a lot of moving parts to the test environment.

There's a very small amount of business logic underneath the system glue, which could be tested, but that's not where things tend to go wrong.

[grodin]

The only idea I've had so far is to spin up a VM/container (not sure a container gives enough isolation), run unlockd in that, call loginctl lock-session in the VM/container, and verify that unlockd logs that it detected the lock/unlock.

It's quite a bit of work, with a lot of potential for flakiness. Also doesn't really solve the problem of testing on a bunch of different distros, except by duplicating a lot of the setup.

[grodin]

For some of what would be needed for this, see zbus' CI. There's more than we need and there's a lot to unpack but maybe this is slightly easier than I thought.