I see this on Ubuntu 20.04.4 LTS with geoclue-2.0/focal,now
2.5.6-0ubuntu1:
$ loginctl session-status c4
c4 - spiele (1002)
Since: Tue 2022-08-02 19:58:47 CEST; 11h ago
Leader: 3710
Seat: seat0; vc7
Display: :0
Service: lightdm; type x11; class user
Desktop: mate
State: closing
Unit: session-c4.scope
├─4152
/usr/lib/x86_64-linux-gnu/indicator-application/indicator-application-service
├─4180 /usr/libexec/geoclue-2.0/demos/agent
└─4194 /usr/bin/dbus-daemon --syslog --fork --print-pid 5
--print-address 7 --session
--
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
