| Summary: | With Systemd boot, log out followed by login no longer applies changes from /etc/groups | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Vorpal <kdebugs> |
| Component: | Startup process | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | a.samirh78, kde, kdelibs-bugs-null, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.24.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Vorpal
2022-06-10 19:58:25 UTC
To confirm, you are logging out and logging back in again rather than rebooting, right? If so, does rebooting instead work? If that works, then I strongly suspect that this is fixed in Plasma 5.25 with https://invent.kde.org/plasma/plasma-workspace/-/commit/e1b146551a0623a308f09a2d9be417b9cf7a4e83. Can you upgrade to 5.25 and see if that fixes it for your log out+log in scenario? I don't think that would affect it. The issue is: systemd --user starts and becomes a session leader systemd --user forks into plasmashell/whatever you change groups you log out and back in systemd --user forks into plasmashell/whatever but it's from the same instance so has the same permissions running newgrp should fix it? > To confirm, you are logging out and logging back in again rather than rebooting, right? Indeed. > If so, does rebooting instead work? Not tested, but if systemctl stop user@1000.service works, I would assume that a reboot also would work. Do you think it is worth testing reboot specifically (I'd have to reenable systemdBoot etc to test this). > Can you upgrade to 5.25 and see if that fixes it for your log out+log in scenario? 5.25 is still in testing in Arch. I'll look into it as soon as it is stabilised. I really don't want to switch to testing. > but it's from the same instance so has the same permissions So why does this work properly in Cinnamon that to the best of my knowledge use systemd for the user session, just like Gnome? I haven't tested Gnome itself though (it has been a long time since I used it and I have no wish to install modern Gnome if I can at all avoid it). > running newgrp should fix it? Yes, but that works even if you don't log out and back in again. However, that starts a nested shell (you could exec newgrp, but it would still only affect that tab in your terminal emulator). (In reply to Nate Graham from comment #1) > Can you upgrade to 5.25 and see if that fixes it for your log out+log in > scenario? I updated to 5.25.0. That did not fix the issue. Perhaps David Edmundson is correct. Yeah, he usually is. :) I don't think there's much we can do our end. (In reply to David Edmundson from comment #6) > I don't think there's much we can do our end. If so, you would expect that gnome has the same issue? I can certainly install it and test it. Also, shouldn't this at least be added to known caveats at https://invent.kde.org/plasma/plasma-workspace/-/wikis/Plasma-and-the-systemd-boot ? |