Bug#859189: systemd-logind: Unix group changes ignored by gdm/lightdm until logind is restarted
Nathan Dorfman
ndorf at rtfm.net
Fri Mar 31 20:56:00 BST 2017
Control: retitle -1 systemd-logind: Unix group changes ignored by gdm/lightdm until logind is restarted
On Fri, Mar 31, 2017 at 12:40:55PM +0200, Michael Biebl wrote:
> When you log out, do you still have an open logind session for that user
> (you can check that as root from the console via loginctl)
Hmm, yes. It looks like they never go away; after logging out and back
in a few times, I have this:
SESSION UID USER SEAT TTY
8 1000 test seat0
10 1000 test seat0 /dev/tty2
6 1000 test seat0
11 1000 test seat0
c5 117 lightdm seat0
2 1000 test seat0
6 sessions listed.
All the sessions except 10 and c5 are X logins that are no longer
active. (Session 10, on tty2, was opened after all this, just so I
could run loginctl.)
On Fri, Mar 31, 2017 at 12:41:42PM +0200, Michael Biebl wrote:
> Are you using gnome-terminal?
> What if you use xterm?
Well, that was totally unexpected! It only happens in gnome-terminal,
not xterm, rxvt or xfce4-terminal. It didn't even occur to me that
it'd do anything other than inherit its GID set from the X session,
(without any kind of --login option, that is).
Anyway, it also continues to assign me groups that no longer exist.
After deleting them with groupdel(1) and logging out and back in:
test at stretch:~$ groups
test cdrom floppy sudo audio dip video plugdev netdev bluetooth
scanner groups: cannot find name for group ID 1001
1001 groups: cannot find name for group ID 1002
1002
test at stretch:~$
BTW, is it correct to Cc you on all of these? Or should I only send
them to the bug?
-nd.
More information about the Pkg-systemd-maintainers
mailing list