Comment 11 for bug 2063032

Okay this was very helpful!

The message "Livepatch client disabled." is only printed when Livepatch is set to be disabled. There are 3 ways to disable/modify the "mode" that Livepatch starts to diagnose issues and prevent avoid faulty patches. It looks like your mode is set to completely disable starting the Livepatch daemon.

- Kernel cmdline: Run `cat /proc/cmdline` and look for a key=value pair where the key is "canonical_livepatch_mode"
- Check for a mode file with `cat /var/local/canonical_livepatch_mode` and see if there is anything inside the file.
- Check for a mode file with `cat /var/lib/snapd/hostfs/var/local/canonical_livepatch_mode"` and see if there is anything inside the file.

And for reference, the "canonical-livepatch.canonical-livepatchd" that comes up when using the snap commands is the name of the service inside the snap. Try `snap info canonical-livepatch` and you can see all the services inside the snap (only 1) and you can try the same with other snaps. Services of a snap can be started/stopped, etc. Running `snap start/stop snap.service` will only start/stop the specified service while `snap start/stop snap` will start/stop all services for that snap. More details are here https://snapcraft.io/docs/service-management