[ quoted text reordered ] On Fri, Aug 05, 2016 at 02:43:30PM -0400, Daniel Kahn Gillmor wrote: > The simplest way to see the control group hierarchy is with "systemctl > status". When these processes are launched by the user service, they'll > end up in the user@NNNN.service like this: [...] > If they've been autolaunched, they'll end up in the sesion-X.scope > sub-tree.
It was indeed the case for me: they had been auto-launched. > > On Fri, Aug 05, 2016 at 12:41:18PM -0400, Daniel Kahn Gillmor wrote: > >> On desktop systems (where i'd expect the majority of secret key access > >> happens), for folks who are running systemd, i recommend enabling the > >> systemd user services, as documented in > >> /usr/share/doc/{gnupg-agent,dirmngr}/README.Debian : > >> > >> systemctl --user enable gpg-agent > >> systemctl --user enable dirmngr OTOH, doing this inhibited a proper start of my GNOME session at next login: only Nautilus started (I can tell because I've it handle my desktop icons) and I could use it to browse the filesystem, but GNOME Shell didn't see to be running. Reverting the above with "disable" [*] fixed the issue, and at next login GNOME session started properly, including GNOME Shell. I haven't yet filed this as a bug report, because my package mix is kinda unusual at present: Debian testing + hand-picked gpg from experimental. But it might be useful for you to know about this. Let me know how I can debug it further and/or if you'd like to move this discussion into a dedicated bug report (and when). Cheers. [*] actually, I manually removed the symlinks from .config/systemd/user/default.target.wants/, but AFAICT the effect is the same -- Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o Former Debian Project Leader . . . . . @zacchiro . . . . o o o . . . o . « the first rule of tautology club is the first rule of tautology club »
signature.asc
Description: PGP signature