On UbuntuMATE 20.04, after logging out, the login session remains in state 'closing', blocked by the /usr/libexec/geoclue-2.0/demos/agent process.
The loginctl command shows accumulating sessions. loginctl session-status <session-name> shows: c2 - ebp-admin (1000) Since: Tue 2021-03-23 03:51:12 PDT; 3min 20s ago Leader: 1149 Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user Desktop: mate State: closing Unit: session-c2.scope └─1547 /usr/libexec/geoclue-2.0/demos/agent Mar 23 03:51:12 ubuntu systemd[1]: Started Session c2 of user ebp-admin. Mar 23 03:51:14 ubuntu mate-session[1175]: WARNING: Unable to find provider '' of required component 'dock' Mar 23 03:51:16 ubuntu gnome-keyring-daemon[1172]: The SSH agent was already initialized Mar 23 03:51:16 ubuntu gnome-keyring-daemon[1172]: The Secret Service was already initialized Mar 23 03:51:16 ubuntu gnome-keyring-daemon[1172]: The PKCS#11 component was already initialized Mar 23 03:51:28 ubuntu pkexec[1888]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Mar 23 03:51:28 ubuntu pkexec[1888]: ebp-admin: Executing command [USER=root] [TTY=unknown] [CWD=/home/ebp-admin] [COMMAND=/usr/lib/updat> Mar 23 03:52:17 ubuntu lightdm[1149]: pam_unix(lightdm:session): session closed for user ebp-admin -- 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