Red Hat Bugzilla – Bug 1464445
Re-logging in does not re-load user groups
Last modified: 2017-11-16 15:02:18 EST
Description of problem:
Logging out and back in does not re-load the user's groups.
Version-Release number of selected component (if applicable):
How reproducible: I tried several times, including with either X session or Wayland, all attempts had this problem.
Steps to Reproduce:
1. addgroup testgroup
2. usermod -a -G testgroup $USER
3. id -a $USER
4. log out of GNOME session
5. log in to GNOME again (using gdm)
6. id -a
uid=1000(alan-sysop) gid=1000(alan-sysop) groups=1000(alan-sysop),10(wheel),1003(testgroup)
uid=1000(alan-sysop) gid=1000(alan-sysop) groups=1000(alan-sysop),10(wheel) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
The groups in the output of `id -a $USER` and `id -a` should be the same, after logging out and back in again.
This is not 100% documented... the Fedora System Adminstrator's Guide doesn't mention *any* method to re-load groups, implying that they take effect immediately. However the behaviour is widely expected, e.g. https://unix.stackexchange.com/a/11573/29483
Rebooting gets the groups reloaded OK.
Originally I tried to restart gdm (while I was still logged in) - I know this forcibly logs you out. But for a while now this ends up with the screen constantly flickering, gdm seems to fail in a loop with "(WW) xf86OpenConsole: VT_ACTIVATE failed: Operation not permitted". So I was not able to test this.
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Appears fixed in F26, yay!