Could you please uninstall the snap with `sudo snap remove canonical-livepatch` then re-install it with `sudo snap install canonical-livepatch` and then provide us with the output from the following commands to investigate further.
- snap info canonical-livepatch
- canonical-livepatch status --verbose
- journalctl -t canonical-livepatch.canonical-livepatchd
- snap connections canonical-livepatch
- ls -la /var/snap/canonical-livepatch/current
The Livepatch snap is made up of a daemon and a client, the daemon is always running in the background and when you run a command like `canonical-livepatch status` the client sends a request over a unix socket located at /var/snap/canonical-livepatch/current/livepatchd.sock or /var/snap/canonical-livepatch/current/livepatchd-priv.sock to the daemon. On your system it looks like the socket is never created.
Hi Robin,
Could you please uninstall the snap with `sudo snap remove canonical- livepatch` then re-install it with `sudo snap install canonical- livepatch` and then provide us with the output from the following commands to investigate further.
- snap info canonical-livepatch livepatch. canonical- livepatchd canonical- livepatch/ current
- canonical-livepatch status --verbose
- journalctl -t canonical-
- snap connections canonical-livepatch
- ls -la /var/snap/
The Livepatch snap is made up of a daemon and a client, the daemon is always running in the background and when you run a command like `canonical- livepatch status` the client sends a request over a unix socket located at /var/snap/ canonical- livepatch/ current/ livepatchd. sock or /var/snap/ canonical- livepatch/ current/ livepatchd- priv.sock to the daemon. On your system it looks like the socket is never created.