[Touch-packages] [Bug 1796758] Re: Because gnome-terminal-server is launched by systemd --user, logging out and back in doesn't reinit groups
This is still a problem but I'm not convinced it's enough of a problem to warrant reopening the ticket. I run into this because my `systemd --user` process persists between logins because I have persistent service units running under it. For most people `systemd --user` will exit when they log out, so for most people, logging out and logging back in will indeed reset their groups. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1796758 Title: Because gnome-terminal-server is launched by systemd --user, logging out and back in doesn't reinit groups Status in systemd package in Ubuntu: Invalid Bug description: Since the beginning of time, the way to apply changes to one's group memberships in UNIX has been to log out and log back in again. In current Ubuntu, that doesn't work. When you add yourself to a group, close all of your windows, log out, log back in again, and open a new gnome-terminal window, and your group memberships will be the same as before. This is because gnome-terminal processes are launched by gnome- terminal-server, which is launched by systemd --user, which doesn't exit when you log out. One possible fix would be to have the systemd init process (i.e., process 1) detect when group memberships have changed and re-launch the systemd --user processes for the users whose groups have changed. Another fix would be to kill systemd --user processes upon logout and have systemd re-launch them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 16:11:13 2018 InstallationDate: Installed on 2018-09-27 (11 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/vgencrypted-lvencryptedroot ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET55W(1.30):bd08/31/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO modified.conffile..etc.systemd.logind.conf: [modified] mtime.conffile..etc.systemd.logind.conf: 2018-09-27T11:40:55.615410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796758] Re: Because gnome-terminal-server is launched by systemd --user, logging out and back in doesn't reinit groups
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1796758 Title: Because gnome-terminal-server is launched by systemd --user, logging out and back in doesn't reinit groups Status in systemd package in Ubuntu: Invalid Bug description: Since the beginning of time, the way to apply changes to one's group memberships in UNIX has been to log out and log back in again. In current Ubuntu, that doesn't work. When you add yourself to a group, close all of your windows, log out, log back in again, and open a new gnome-terminal window, and your group memberships will be the same as before. This is because gnome-terminal processes are launched by gnome- terminal-server, which is launched by systemd --user, which doesn't exit when you log out. One possible fix would be to have the systemd init process (i.e., process 1) detect when group memberships have changed and re-launch the systemd --user processes for the users whose groups have changed. Another fix would be to kill systemd --user processes upon logout and have systemd re-launch them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 16:11:13 2018 InstallationDate: Installed on 2018-09-27 (11 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/vgencrypted-lvencryptedroot ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET55W(1.30):bd08/31/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO modified.conffile..etc.systemd.logind.conf: [modified] mtime.conffile..etc.systemd.logind.conf: 2018-09-27T11:40:55.615410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796758] Re: Because gnome-terminal-server is launched by systemd --user, logging out and back in doesn't reinit groups
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1796758 Title: Because gnome-terminal-server is launched by systemd --user, logging out and back in doesn't reinit groups Status in systemd package in Ubuntu: Confirmed Bug description: Since the beginning of time, the way to apply changes to one's group memberships in UNIX has been to log out and log back in again. In current Ubuntu, that doesn't work. When you add yourself to a group, close all of your windows, log out, log back in again, and open a new gnome-terminal window, and your group memberships will be the same as before. This is because gnome-terminal processes are launched by gnome- terminal-server, which is launched by systemd --user, which doesn't exit when you log out. One possible fix would be to have the systemd init process (i.e., process 1) detect when group memberships have changed and re-launch the systemd --user processes for the users whose groups have changed. Another fix would be to kill systemd --user processes upon logout and have systemd re-launch them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 16:11:13 2018 InstallationDate: Installed on 2018-09-27 (11 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/vgencrypted-lvencryptedroot ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET55W(1.30):bd08/31/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO modified.conffile..etc.systemd.logind.conf: [modified] mtime.conffile..etc.systemd.logind.conf: 2018-09-27T11:40:55.615410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
