See upstream bug https://gitlab.gnome.org/GNOME/gnome-session/-/issues/74#note_978036 Reproducible: Always
Solution from the linked thread was: "add Slice=-.slice in the [Service] section of/usr/lib/systemd/user/gnome-session-restart-dbus.service fixes the issue."
So to be explicit, this is a regression with systemd-247
in the meantime, this is what I did because I think 120s is really excessive : # cat /etc/portage/patches/sys-apps/systemd/excessive_timeout.patch --- a/units/user@.service.in 2020-11-26 13:00:50.000000000 -0500 +++ b/units/user@.service.in 2020-11-29 08:32:55.309364569 -0500 @@ -23,5 +23,5 @@ KillMode=mixed Delegate=pids memory TasksMax=infinity -TimeoutStopSec=120s +TimeoutStopSec=5s KeyringMode=inherit
Applying the following patch to gnome-base/gnome-session fixed the issue for me. https://gitlab.gnome.org/GNOME/gnome-session/-/merge_requests/55
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=86c66f18359d1521517820a84325a6e8fec93b85 commit 86c66f18359d1521517820a84325a6e8fec93b85 Author: Pacho Ramos <pacho@gentoo.org> AuthorDate: 2021-03-28 08:52:55 +0000 Commit: Pacho Ramos <pacho@gentoo.org> CommitDate: 2021-03-28 08:52:55 +0000 gnome-base/gnome-session: Fix conflict with systemd v247 Upstream patch from 'master' to fix indirect conflict with exit.target via app.slice Closes: https://bugs.gentoo.org/758752 Package-Manager: Portage-3.0.17, Repoman-3.0.2 Signed-off-by: Pacho Ramos <pacho@gentoo.org> ...e-session-3.38.0-exit-conflict-systemd247.patch | 56 ++++++++++ .../gnome-session/gnome-session-3.38.0-r1.ebuild | 123 +++++++++++++++++++++ 2 files changed, 179 insertions(+)
