-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate systemd session management #17
Comments
For the time being to get the daily focal builds working, we've opted to add the |
While we're at it could we revisit #4? I never got an answer as to why the changes were reverted. I note that the startups already have the necessary fields to be started and managed by gnome-session without being listed as RequiredComponents:
Eventually I suspect GNOME will transition their own xdg autostarts to systemd, but I do not as yet know if they are planning a complete conversion of them to systemd services or to use gnome-session as an interface between systemd and xdg startups for backward compatibility. Listing them as RequiredComponents only ensures that some users get dropped to that confounding "Oops..." screen which they are not going to know what to do with; removing them will do no harm at the moment and may even be necessary anyway once the transition to systemd session management is complete for g-s-d. |
Please keep in mind that some distros with non-systemd suppoprt still need some solution outside the systemd world! |
Yep, that is why GNOME hasn't dropped any of their xdg autostarts, and claimed they should continue to work. I agree that these should not be removed from session-settings. |
We should work on this soon as GNOME is removing the old code here https://gitlab.gnome.org/GNOME/gnome-session/-/merge_requests/93 |
I guess this can be closed since we're now handling both the X and Wayland sessions with systemd session management |
Just writing down some considerations based on the fact we're retiring cerbere and switching to
gnome-session
to manage session components (like plank and wingpanel).gnome-session
>= 3.34 is using systemd units for session components by default and it looks like we're getting that version or newer in 20.04, so we should probably look into this.Thanks to @quequotion we know that we don't need to use this new systemd method and we can use the
--builtin
flag ongnome-session
to carry on supporting theX-GNOME-AutoRestart
key that we're planning to use for 3.28, but maybe systemd will bring us some advantages like more configurable aggressiveness of restarting components etc...I imagine that the
--builtin
option will become less and less supported as time goes on, but at least we know we have two options outside of Cerbere for 6.0.Some info here:
The text was updated successfully, but these errors were encountered: