GNOME Bugzilla – Bug 759915
Don't launch telepathy, gnome-online-accounts on the login screen
Last modified: 2016-09-07 13:10:43 UTC
Debian installs some "interesting" D-Bus service files to /usr/share/gdm/greeter/dbus-1: [D-BUS Service] Name=org.freedesktop.Telepathy.AccountManager Exec=/bin/false [D-BUS Service] Name=org.freedesktop.Telepathy.MissionControl5 Exec=/bin/false [D-BUS Service] Name=org.gnome.OnlineAccounts Exec=/bin/false The effect is to make sure these never get launched for the gdm user. Currently on Fedora, Arch, etc. we have two instances each of goa-daemon, goa-identity-service, and mission-control-5 running at all times: one for the gdm user, and one for the real user. It would be good to find a nicer/upstream solution for this. We have the same issue with gvfsd, except Debian uses environment variables to disable that, and it's needed for g-i-s; that is bug #725584.
Note that the D-Bus service solution won't work for us. We need to keep gnome-online-accounts enabled in initial-setup mode.
*** Bug 752278 has been marked as a duplicate of this bug. ***
This issue also affects gvfs. If KDE is installed, even some kde daemons get started in the same way (dbus activation) thus they should not: $ ps -u gdm PID TTY TIME CMD 998 ? 00:00:00 systemd 1000 ? 00:00:00 (sd-pam) 1003 tty1 00:00:00 gdm-wayland-ses 1024 tty1 00:00:00 dbus-daemon 1038 tty1 00:00:00 gnome-session-b 1068 tty1 00:00:16 gnome-shell 1184 tty1 00:00:00 gvfsd 1193 tty1 00:00:00 Xwayland 1249 tty1 00:00:00 at-spi-bus-laun 1254 tty1 00:00:00 dbus-daemon 1257 tty1 00:00:00 at-spi2-registr 1264 ? 00:00:00 pulseaudio 1306 tty1 00:00:00 gnome-settings- 1312 tty1 00:00:00 gvfs-udisks2-vo 1327 tty1 00:00:00 gvfs-afc-volume 1335 tty1 00:00:00 gvfs-goa-volume 1342 tty1 00:00:00 goa-daemon 1352 tty1 00:00:01 goa-identity-se 1354 tty1 00:00:00 mission-control 1357 tty1 00:00:00 gvfs-gphoto2-vo 1368 tty1 00:00:00 gvfs-mtp-volume 1404 tty1 00:00:00 kded5 1443 ? 00:00:00 kdeinit5 1445 ? 00:00:00 klauncher Also at-spi-bus-launcher is launched even though AutostartCondition=GSETTINGS org.gnome.desktop.interface toolkit-accessibility is set to "false" (my configuration).
FYI: your gsettings are ignored because the gdm user has its own gsettings. See bug #725584 for gvfs.
(In reply to Michael Catanzaro from comment #4) > FYI: your gsettings are ignored because the gdm user has its own gsettings. I know. I changed gdm's gsettings, not the user's gsettings. > See bug #725584 for gvfs. Oh, thanks, I didn't see that.
Hello, what's the status of this bug? I've tested with gdm 3.20 (debian experimental and F24) the feeling that it doesn't try to start goa or telepathy-mission-control
(In reply to Laurent Bigonville from comment #6) > Hello, what's the status of this bug? > > I've tested with gdm 3.20 (debian experimental and F24) the feeling that it > doesn't try to start goa or telepathy-mission-control As stated in comment #0, Debian already disables both goa (which breaks gnome-initial-setup) and telepathy for the login screen. You should be seeing them both in F24; if not, I don't know why.
Well I removed the /usr/share/gdm/greeter/dbus-1 files on my debian machine before testing. So I can confirm that goa and telepathy-missing-control are not being started with 3.20.
Still, gnome-shell running as user gdm is loading libtelepathy-glib.so, which is wrong.
(In reply to Christian Stadelmann from comment #9) > Still, gnome-shell running as user gdm is loading libtelepathy-glib.so, > which is wrong. No. gnome-shell (in any mode) requires the private libgnome-shell which links with libtelepathy-glib. I agree that it doesn't make sense to *run* mission-control and friends from the login-screen, but asking for differently linked private library versions depending on the session mode is moving goal posts way too far.
(In reply to Michael Catanzaro from comment #7) > You should be seeing them both in F24; if not, I don't know why. Actually you shouldn't. The chat integration has never been active on the login screen, what was starting mission-control before was the "busy" switch in the message tray menu (although the tray was always hidden on the login screen). The tray was removed in 3.16, so this should no longer be an issue (also see bug 707486). For what it's worth, I don't see either mission-control or goa-daemon for the gdm user on Fedora 25 ...
(In reply to Florian Müllner from comment #11) > For what it's worth, I don't see either mission-control or goa-daemon for > the gdm user on Fedora 25 ... I can confirm that goa-daemon is not getting started for the gdm user even on Fedora 24. I know that it gets started in Fedora 23. Can't say for sure about mission-control because it isn't even installed. Seems like on a default Fedora 24 installation we only pull in telepathy-glib and telepathy-logger, and I don't have Polari installed on this system.
*** Bug 757112 has been marked as a duplicate of this bug. ***
(In reply to Debarshi Ray from comment #12) > Can't say for sure about mission-control because it isn't even installed. > Seems like on a default Fedora 24 installation we only pull in > telepathy-glib and telepathy-logger, and I don't have Polari installed on > this system. I have just one instance of mission-control running, for my user.