Control: severity -1 minor I consider this bug pretty minor since X11 stuff is going to be installed for quite some time on Debian's Wayland based desktops, so don't spend too much effort on this right now.
On Sat, 2020-05-23 at 15:57 +0100, Colin Watson wrote: > My concern about that is that it's about what's installed, not what's > active/running for that particular user. It may not matter in your case > but I'm sure cutting that corner is going to be wrong for somebody. Hmm, that is a good point. I think the main problem here is that the service itself (ssh-agent) is checking settings (Xsession.options) for the service manager (Xsession) to see if the service should run instead of the service manager doing the checking. Ideally it should be the other way around instead. I noticed that Xsession.d 99x11-common_start exists too and also starts the ssh-agent when appropriate but I assume Xsession isn't used for the GNOME X11 session run from gdm on systemd though. In addition various desktops have their own session service starting mechanisms, although some are moving to systemd user services. In addition there is the xdg autostart mechanism and I guess there are user services started by dbus too. I'm not sure how to untangle this mess, but I guess the first thing to be done would be to test on both systemd/sysvinit what happens when launching different X11/Wayland desktops and window managers from startx and from different login managers to see exactly when ssh-agent is launched by Xsession and when by systemd and when there are any race conditions between the two options. Then you can go through the matrix of possibilities and find plausible fixes. Since the results will probably be useful to other Debian folks, perhaps a wiki page of the results and a thread about them would be useful to Debian too. -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
