Comment 10 for bug 2039577

So I took a look and tested the patch and it doesn't actually fix the issue. In a default installation of Lucid+, the ssh.socket unit is enabled and active, and the ssh.service unit is disabled and inactive.

The code in cc-remote-login.c only checks ssh.service to determine the status of the daemon, so it is still showing ssh as being disabled.

Also, the patch will attempt to enable and start both the socket and the daemon, when only one of them should be enabled at the same time.

The difficulty here is that while by default the socket is the one that is active on Lunar+, and the service is what is enabled by default on jammy and older, the README.Debian has documentation that allows an admin to change which of the two activation methods can be the default.

While we could modify the patch to hardcode socket on lunar+ and service on jammy-, I wonder if there's a better way to handle this.