debian/control.in: Relax the evolution version for the Breaks, the .desktop file was apparently already renamed in 3.30.0

This variable was introduced to allow Xwayland auto-startup.
Unfortunately, it will prevent g-s-d process startup if it leaks from a
wayland session to an Xorg session.

As such, add it to the list of variables that are unset at login time.

There is error in journal log:
gnome-session-c[4905]: Error creating FIFO: File exists
The errno can't be negative number.

https://gitlab.gnome.org/GNOME/gnome-session/-/merge_requests/42

The description of the autostart mechanism with default directories
--autostart option and environment variable was unclear and also did
not match the actual implementation.

The bus daemon is going to get restarted on shutdown, so make sure
it has a pristine environment when starting back up.

At the moment, gnome-session explicitly sets the various LC_ variables
to the user configured region.

That's unnecessary, though.  If the LC_ variables are unset,
applications know to use LANG.  Furthermore, setting the LC_ variables
makes it so you can't override them with LANG anymore.

This commit makes sure the LC_ variables only get set when absolutely
necesary. That is, when they are different than LANG.

https://gitlab.gnome.org/GNOME/gnome-session/issues/37

Benjamin Berg authored Nov 27, 2019 and Ray Strode committed May 06, 2020

Both gnome-shell and g-s-d will start putting launched applications into
transient scopes. As these scopes will be prefixed with gnome-launched-,
we can set defaults by installing an appropriate drop-in. This allows us
to bind them to graphical-session.target and lower their stop timeout.

See gnome-shell!863 and gnome-settings-daemon!147

Benjamin Berg authored Nov 28, 2019 and Ray Strode committed May 06, 2020

Try to place launched applications into a systemd scope. This will only
have an effect on systemd managed sessions, where it will e.g. protect
gnome-session from OOM actions to a child resulting in a service
shutdown.

systemd's target units can never be in the failed state, they only have mapping for inactive and active.

Simplify the definition using G_DECLARE_FINAL_TYPE and using the type as private
instance.

Remove deprecated functions

In multi-monitor setups show the fail dialog in all visible monitors instead
of only showing in the primary that might not work, or might allow the user
to still interact with the Shell if the session stopped running at application
level.

Explicitly setting the variable to an empty string is a bit more more readable.
See https://www.shellcheck.net/wiki/SC1007

Add --list command to make it easy to list the applications currenty
inhibiting the session, rather than having to poke at introspection
output.

In the event that the user logs back in after a session failure, it is
likely that some failed units cannot start. Reset all failed states to
ensure that systemd at least tries to start all previously failed units
on every login.

This is intended to be run from core components of a session. It is an
alternative to using OnFailure=gnome-session-failed.target that can be
put into ExecStopPost/ExecStop which will only trigger OnFailure for a
subset of errors.

Primarily this avoids trigger the OnFailure action for dependency
issues.

During the GNOME 3.34 times when systemd support was still added, all
the session components pulled in themselves or were explicitly pulled by
GNOME session. However, doing this makes it really hard to create a
custom session or to modify the existing sessions in some way.

Change things so that we pull in all the dependencies for each session
type independently. This works using a drop-in for the
gnome-session@.target and all GNOME session users will need to provide
such a drop-in or pass --builtin to gnome-session.

This is a bit painful, but to do proper shutdown, we need an
After=gnome-session-x11-services.target, but we also need to be able to
tell gnome-shell when the services are ready. So add a special
gnome-session-x11-services-ready.target which will be used by
org.gnome.SettingsDaemon.XSettings.service.

Update to upstream version '3.37.0'
with Debian dir e974fff70c96569ca1ca5799aa554ee83ae5e423

This gnome-session updates and rejigs the systemd units that live here -
we need to make sure we have the updated versions available.

3.37.90 has not been relased yet.

This component also includes a session definition that gnome-session breaks

Updating gnome-session would just break previous gdm3, causing a black
screen.

gnome-session Debian release 3.37.0-1

The fail whale is still used as triggered by systemd, the bugs that the
patch was addressing are 5 years old now and there's no point to carry
this patch even more when upstream believes that the dialog should be
shown. Also from an Ubuntu POV it's a better user experience than just
going back to gdm.

As per upstream changes, now we need to provide a systemd configuration for
ubuntu, thanks to the upstream changes we can keep the diff minimal though,
as we basically can reuse most of the gnome session, creating a new specific
drop-in for the ubuntu session that is now automatically generated by meson.

Using a deny list of components we don't care about, so that it's easier to
maintain.