Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-terminal (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
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
> Starting a gnome-terminal from this terminal
Even executing "gnome-terminal" from an xterm goes through dbus/systemd.
"gnome-terminal" is just a controlling client that asks systemd to start
up a server which then displays the window and does all the rest.
Don't ask why the architecture is
I can start an other terminal (i.e. xterm) there are the groups correct.
Starting a gnome-terminal from this terminal causes wrong groups in
gnome-terminal. So either gnome-terminal sets the groups or uses a
dbus/systemd/whatever funktion to set the groups. I would call both
scenarios a bug in the
gnome-terminal itself doesn't do any authentication / PAM stuff. It's
probably an issue with `systemd --user` which launches gnome-terminal.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
** Description changed:
If you use pam_group to add users to a group and open gnome-terminal the
dynamic group is lost.
How to reproduce:
enable pam_group
add "*;*;*;Al-2400;dialout" to /etc/security/group.conf
- log in with a user which is not in the video group
+ log in with
