KillUserProcesses=yes is a sledgehammer of a solution. I would advise just removing the geoclue package.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1871728 Title: geoclue agent process persists after user logout Status in geoclue-2.0 package in Ubuntu: Confirmed Bug description: This concerns geoclue-2.0 2.5.6-0ubuntu1 in Ubuntu focal. I am using the Xfce desktop. When a user logs in, a /usr/libexec/geoclue-2.0/demos/agent process is started. However, when the user logs out, and the associated "systemd --user" instance is killed, the geoclue process remains---apparently because it is running outside of the process group in which all the other session-related processes were in. Not only does this prevent the process from being cleaned up correctly, if the user logs in again, *another* geoclue process starts up. And when they log out, and everything else gets cleaned up... *two* useless geoclue processes remain. Repeat ad infinitum. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1871728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
