I think you misunderstand me a bit. > The issue is probably in systemd, starting up gnome-terminal (and > presumably any other app that it starts up) with the wrong groups.
Yes gnome-terminal uses a systemd --user service to start a terminal-server. This terminal-server is the parrent of all shells in a gnome-terminal for this user. The problem is systemd --user services are designed as per-user service not per-session[0]. As I understand the Mailinglist, there ar no plans to change this. So a systemd --user service isn't the right tool for this architecture of a terminal and for any other programm which should belong to a session. Thats why I say it's a bug in gnome-terminal not in systemd. That systemd has no per-session services is an other problem. [0] https://lists.freedesktop.org/archives/systemd- devel/2014-March/017552.html -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1835224 Title: gnome-terminal drops pam_group config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1835224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
