On Mon, 21 Dec 2020 at 19:29:19 +0100, Michael Biebl wrote:
> Indeed. While looking at this, I also noticed that e.g. tracker is started
> within the gdm session. This doesn't strike me as a good idea.
> I'm not so firm anymore, how the gdm(3) session is setup, so I'm not sure
> whether to report such issues against gdm3 or tracker.
Probably gdm3 with an X-Debbugs-Cc to tracker - if we conclude that it's
actually tracker that should change, we can reassign, but gdm3 is probably
a better coordination point.
I'm not sure how enabling/disabling services for the greeter session is
meant to work. The greeter uses /usr/share/gdm/greeter/applications and
/usr/share/gdm/greeter/autostart to customize fd.o MIME handling and
autostarted apps, but doesn't seem to have anything to restrict activation
of D-Bus services or systemd user services.
It seems inconsistent that the "user bus" is getting used at all, in fact:
I would have expected that nothing running as Debian-gdm would be seeing
it, because everything ought to be wrapped in dbus-run-session.
Perhaps this is all triggered by services that are launched "eagerly" by
`systemd --user` as part of default.target? Of those services, I think
we probably need pulseaudio (for screen readers and other a11y), but not
the rest.
smcv
