Am 15.03.22 um 13:36 schrieb Ingo Wichmann:
Package: systemd Version: 247.3-6 Severity: normal X-Debbugs-Cc: iw-deb...@linuxhotel.deDear Maintainer, on a notebook running Debian 11 (tested with Ubuntu 20.04, too) with gnome desktop I added my user to a new group: sudo groupadd docker sudo gpasswd -a nutzer36 docker after that, I logged out and then on again. I expected that when I check with the id command, that my user would now belong to that group. But that's not the case. I found out, that there are some processes left over from my last login: pgrep -lau nutzer36 | head 723 /lib/systemd/systemd --user 724 (sd-pam) 758 /usr/bin/pipewire 759 /usr/bin/pulseaudio --daemonize=no --log-target=journal 792 /usr/bin/pipewire-media-session 871 ssh-agent -D -a /run/user/1000/openssh_agent all the current processes of my new desktop session are child processes of that old systemd --user session If I log out and terminate systemd --user, the session is closed and after login I'm member of the group as expected. login out using loginctl kill-session did not help
Which terminal emulator do you use? E.g gnome-terminal is implemented as a user service and might be affected.
After logging out, how long did you wait before logging in again?I vaguely remember that there is a timeout before an idle user session is terminated.
Or do you have lingering enabled, so user sessions are deliberately not terminated?
OpenPGP_signature
Description: OpenPGP digital signature
