Comment 10 for bug 2063032

Here you go:

///////////////////////
ps aux | grep livepatch
///////////////////////

root 749614 0.0 0.0 17736 6720 ? S 12:37 0:00 journalctl -o json --no-pager -n 10 -f --namespace=* -u snap.canonical-livepatch.canonical-livepatchd.service
root 755884 0.0 0.0 17736 6720 ? S 12:39 0:00 journalctl -o json --no-pager -n 10 -f --namespace=* -u snap.canonical-livepatch.canonical-livepatchd.service
root 756858 0.0 0.0 17736 6720 ? S 12:41 0:00 journalctl -o json --no-pager -n 10 -f --namespace=* -u snap.canonical-livepatch.canonical-livepatchd.service
root 841197 0.0 0.0 6620 2496 pts/19 S+ 15:45 0:00 grep --color=auto livepatch

/////////////////////////////////////////////////
ps aux | grep livepatch (After stopping the snap)
/////////////////////////////////////////////////

Same result as above

Using the snap_common command it states only "Livepatch client disabled." canonical-livepatch status states the same error as before. Could it be that there are two seperate versions of livepatch, maybe and could they interfer with each other? Because in snap I can start/stop a snap called "canonical-livepatch" as well as one called "canonical-livepatch.canonical-livepatchd". Or is that just an alias?