isa/gnome-shell
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
a466029374
gnome-shell/data/org.gnome.Shell@wayland.service.in

35 lines
1.1 KiB
SYSTEMD
Raw Normal View History

data: Update systemd units The existing units were never used as the corresponding support was never merged into gnome-session. This commits updates units to be usable with the newer gnome-session unit definitions. Also added is appropriate failure/restart logic including the ability to disable extensions. Note that extensions will only be disabled if a failure happens in the first two minutes after login. https://gitlab.gnome.org/GNOME/gnome-session/merge_requests/13 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/507
2019-04-19 18:21:55 -04:00
[Unit]
Description=GNOME Shell on Wayland
# On wayland, force a session shutdown
data: Use org.gnome.Shell prefix for systemd units In general we want to move towards using reverse domain names for systemd units. Doing this also means we have a consistent name between desktop file and systemd unit, allowing us to create a generator that pulls in the unit as defined in the sessions RequiredComponents. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/895
2020-02-13 12:39:32 -05:00
OnFailure=org.gnome.Shell-disable-extensions.service gnome-session-shutdown.target
data: Update systemd units The existing units were never used as the corresponding support was never merged into gnome-session. This commits updates units to be usable with the newer gnome-session unit definitions. Also added is appropriate failure/restart logic including the ability to disable extensions. Note that extensions will only be disabled if a failure happens in the first two minutes after login. https://gitlab.gnome.org/GNOME/gnome-session/merge_requests/13 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/507
2019-04-19 18:21:55 -04:00
OnFailureJobMode=replace-irreversibly
CollectMode=inactive-or-failed
RefuseManualStart=on
RefuseManualStop=on
After=gnome-session-manager.target
Requisite=gnome-session-initialized.target
PartOf=gnome-session-initialized.target
Before=gnome-session-initialized.target
data: Use ConditionEnvironment on unit files Following GNOME/gnome-shell!1472. It's been almost three years since ConditionEnvironment was available. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2791>
2023-06-07 03:59:25 -04:00
ConditionEnvironment=XDG_SESSION_TYPE=%I
data: Update systemd units The existing units were never used as the corresponding support was never merged into gnome-session. This commits updates units to be usable with the newer gnome-session unit definitions. Also added is appropriate failure/restart logic including the ability to disable extensions. Note that extensions will only be disabled if a failure happens in the first two minutes after login. https://gitlab.gnome.org/GNOME/gnome-session/merge_requests/13 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/507
2019-04-19 18:21:55 -04:00
[Service]
data: Place the shell into session.slice when using systemd This way we conform more to https://systemd.io/DESKTOP_ENVIRONMENTS https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/895
2020-07-29 10:59:32 -04:00
Slice=session.slice
Notify service startup to systemd Using the bus name to notify service startup to systemd has some disadvantages. The main one being that systemd will consider a gnome-shell restart (Alt+F2 r) a service failure and restart the shell, cleaning up all its children (i.e. user launched applications). In the future the shell should launch applications in their own transient unit so that a service restart does not affect applications. Another potential issue is that we must never load gnome-shell-wayland.service and gnome-shell-x11.service at the same time, as systemd does not like two services providing the same bus name. Fixes https://gitlab.gnome.org/GNOME/gnome-shell/issues/1496 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/690
2019-08-25 01:26:12 -04:00
Type=notify
data: Update systemd units The existing units were never used as the corresponding support was never merged into gnome-session. This commits updates units to be usable with the newer gnome-session unit definitions. Also added is appropriate failure/restart logic including the ability to disable extensions. Note that extensions will only be disabled if a failure happens in the first two minutes after login. https://gitlab.gnome.org/GNOME/gnome-session/merge_requests/13 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/507
2019-04-19 18:21:55 -04:00
ExecStart=@bindir@/gnome-shell
data: Create generic org.gnome.Shell.target Move the GNOME shell service file adapation for x11/wayland into the target/service files. This means that the session definition can simply pull in org.gnome.Shell.target, without having to care about whether it is starting an X11 or wayland session. Note that this currently requires fork'ing to do the test. This will however not be needed in the long term when ConditionEnvironment becomes available (see https://github.com/systemd/systemd/pull/15817). We technically do not need to use template units. But doing so means that the unit can be translated to the app id more easily (though it is not yet completely clear how this should look like in the long term). https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/895
2020-06-09 07:01:39 -04:00
# Exit code 1 means we are probably *not* dealing with an extension failure
SuccessExitStatus=1
data: ensure systemd environment is sanitized when shell exits When mutter is acting as a display server it sets a number of environment variables in the user's session. These variables tell applications where the display server's sockets are. When the shell exits at logout time it leaves these environment variables in the systemd --user environment, which can confuse subsequent sessions. This commit clears up the environment on exit. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1129
2020-03-25 16:30:46 -04:00
# unset some environment variables that were set by the shell and won't work now that the shell is gone
data: Only unset environment when the service actually ran ExecStopPost= is executed even if ExecCondition= fails. As such, we need to add a guard as we would otherwise clear environment variables on X11 sessions (rendering them utterly useless). https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1418
2020-08-20 04:08:01 -04:00
ExecStopPost=-/bin/sh -c 'test "$SERVICE_RESULT" != "exec-condition" && systemctl --user unset-environment GNOME_SETUP_DISPLAY WAYLAND_DISPLAY DISPLAY XAUTHORITY'
data: ensure systemd environment is sanitized when shell exits When mutter is acting as a display server it sets a number of environment variables in the user's session. These variables tell applications where the display server's sockets are. When the shell exits at logout time it leaves these environment variables in the systemd --user environment, which can confuse subsequent sessions. This commit clears up the environment on exit. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1129
2020-03-25 16:30:46 -04:00
data: Update systemd units The existing units were never used as the corresponding support was never merged into gnome-session. This commits updates units to be usable with the newer gnome-session unit definitions. Also added is appropriate failure/restart logic including the ability to disable extensions. Note that extensions will only be disabled if a failure happens in the first two minutes after login. https://gitlab.gnome.org/GNOME/gnome-session/merge_requests/13 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/507
2019-04-19 18:21:55 -04:00
# On wayland we cannot restart
Restart=no
data: Lower TimeoutStartSec in systemd units If there's a stubborn process in our cgroup, we shouldn't hang around waiting for the default (30 seconds) before the session closes. We've logged out, SIGTERMed and the thing is refusing to go away, let's not make people hang around for ages. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/699
2019-09-03 07:45:24 -04:00
# Kill any stubborn child processes after this long
TimeoutStopSec=5
data: Lower down gnome-shell process' OOM score When GNOME shell runs on a less memory system (for example 3 GB RAM), it is usually killed by the kernel OOM-killer easily. Because, it has a higher OOM score. However, GNOME desktop environment cannot do anything when the GNOME shell is killed. This commit adjusts and lowers down gnome-shell process' OOM score to avoid being killed by the kernel OOM-killer too early. In other words, sacrifices other processes first. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2582>
2022-12-12 02:21:23 -05:00
# Lower down gnome-shell's OOM score to avoid being killed by OOM-killer too early
OOMScoreAdjust=-1000
Reference in New Issue Copy Permalink