Hi Simon Am 21.12.20 um 18:48 schrieb Simon McVittie:
comm="/usr/libexec/gsd-sharing "In an ideal world, I suspect this service shouldn't even be started in the greeter: there's no reason why the greeter session would want to share anything with a LAN.
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.
I don't think we need the gvfs monitors in the gdm session either: │ │ └─user@125.service» │ │ ├─gvfs-goa-volume-monitor.service» │ │ │ └─812 /usr/libexec/gvfs-goa-volume-monitor │ │ ├─pulseaudio.service» │ │ │ └─735 /usr/bin/pulseaudio --daemonize=no --log-target=journal │ │ ├─gvfs-daemon.service» │ │ │ ├─751 /usr/libexec/gvfsd │ │ │ └─769 /usr/libexec/gvfsd-fuse /run/user/125/gvfs -f -o big_writes │ │ ├─gvfs-udisks2-volume-monitor.service» │ │ │ └─775 /usr/libexec/gvfs-udisks2-volume-monitor │ │ ├─init.scope» │ │ │ ├─728 /lib/systemd/systemd --user │ │ │ └─729 (sd-pam) │ │ ├─gvfs-gphoto2-volume-monitor.service» │ │ │ └─801 /usr/libexec/gvfs-gphoto2-volume-monitor │ │ ├─dbus.service»│ │ │ ├─740 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopi…
│ │ │ ├─818 /usr/libexec/goa-daemon │ │ │ └─836 /usr/libexec/goa-identity-service │ │ ├─tracker-miner-fs.service» │ │ │ └─737 /usr/libexec/tracker-miner-fs │ │ ├─gvfs-mtp-volume-monitor.service» │ │ │ └─846 /usr/libexec/gvfs-mtp-volume-monitor │ │ └─gvfs-afc-volume-monitor.service» │ │ └─806 /usr/libexec/gvfs-afc-volume-monitor gnome-online-accounts in the gdm session seems unneeded as well. Regards, Michael
OpenPGP_signature
Description: OpenPGP digital signature
