Bug#859189: /lib/systemd/systemd-logind: Unix group changes ignored by gdm/lightdm until logind is restarted

[Michael Biebl]

Am 31.03.2017 um 12:19 schrieb Nathan Dorfman:
> Package: systemd
> Version: 232-19
> Severity: important
> File: /lib/systemd/systemd-logind
> 
> Dear Maintainer,
> 
> On a fresh stretch install, adding myself to a new Unix group has no
> effect on lightdm and gdm3 logins until systemd-logind is restarted
> (via systemctl). No amount of logging out and back in, or restarting
> the DM itself, is effective. 
> 
> I simply use the following commands:
> 
> sudo groupadd testgroup
> sudo groupmod -aG testgroup $USER
> 
> Subsequent graphical logins don't put me in the new group (it doesn't
> appear in the output of groups(1) or id(1)). Virtual terminals,
> login(1) and su(1) all work fine, though.
> 
> The situation persists until I run 'systemctl restart systemd-logind',
> after which graphical logins see the new group as expected.

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)


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20170331/a4c81922/attachment-0002.sig>