Skip to content
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

Remove GSD plugins from session RequiredComponents #4

Closed
quequotion opened this issue Mar 3, 2018 · 4 comments

Comments

Projects
None yet
3 participants
@quequotion
Copy link

commented Mar 3, 2018

If anything listed in RequiredComponents fail to start, or crash after starting, gnome-session will crash:

RequiredComponents=gala;org.gnome.SettingsDaemon.A11yKeyboard;org.gnome.SettingsDaemon.A11ySettings;org.gnome.SettingsDaemon.Clipboard;org.gnome.SettingsDaemon.Color;org.gnome.SettingsDaemon.Datetime;org.gnome.SettingsDaemon.Housekeeping;org.gnome.SettingsDaemon.Keyboard;org.gnome.SettingsDaemon.MediaKeys;org.gnome.SettingsDaemon.Mouse;org.gnome.SettingsDaemon.Power;org.gnome.SettingsDaemon.PrintNotifications;org.gnome.SettingsDaemon.Rfkill;org.gnome.SettingsDaemon.ScreensaverProxy;org.gnome.SettingsDaemon.Sharing;org.gnome.SettingsDaemon.Smartcard;org.gnome.SettingsDaemon.Sound;org.gnome.SettingsDaemon.Wacom;org.gnome.SettingsDaemon.XSettings;

When gnome-session crashes, either the user will find themselves back in their desktop manager or facing a white screen-of-death. That screen locks out the desktop with the rather uninformitive message "Oh no! Something has gone wrong. A problem has occured and the system can't recover. Please log out and try again." and a single "Log Out" button (I have a number of gripes about this screen that are best to discuss with GNOME upstream). Lately I haven't encountered it, but I have been dumped back into LightDM, often leaving a zombified failed session that must be killed with loginctl in a TTY before subsequent sessions can be initiated safely (a problem for either LightDM, systemd, or GNOME upstream). I think it best to avoid either scenario if at all possible, given the unlikelyhood that either can be improved (GNOME likes their WSOD; no one wants to take responsibility for the zombified sessions problem).

In any case, these G-S-D plugins are already autostarted by the xdg autostarts provided in this package; it would be redundant to be using the .session file to autostart them. Their listing as RequiredComponents primarily serves to ensure that gnome-session will crash if any of them fail, and secondarily prevents users from disabling any plugins they deem unneccessary. Are they critical enough to warrant that behavior?

@codygarver

This comment has been minimized.

Copy link
Contributor

commented Mar 5, 2018

This was necessary before GSD 3.27 and has been removed now that 3.27 has landed in Bionic.

@codygarver codygarver closed this Mar 5, 2018

@danrabbit danrabbit added this to the juno-beta1 milestone Mar 5, 2018

@codygarver codygarver self-assigned this Mar 5, 2018

@codygarver codygarver changed the title G-S-D Plugins in RequiredComponents; really a good idea? Remove GSD plugins from session RequiredComponents Mar 5, 2018

@quequotion

This comment has been minimized.

Copy link
Author

commented Mar 6, 2018

Good news! Thanks for the update!

@quequotion

This comment has been minimized.

Copy link
Author

commented Apr 17, 2018

@quequotion

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.