Yes, because the controlling systemd service wait in vain for graceful
termination of the gnome-session-binary and send a SIGKILL after 90s.
For an unknown reason nobody seems to send a SIGTERM before. But I'm
neither used to write scripts for systemd nor know the details of
desktop session management. Therefore, I expect that my suggestion is
not the proper way to fix the issue. But it may lead experts to discover
the core problem.
On 28.01.25 11:19, L'Africain wrote:
> Can you explain more?
> You add this lines to the service:
> #<<< 20250128/gj send SIGTERM to the gnome session binary
> ExecStop=-/bin/bash -exc 'GS_PID=$(ps x -o "pid,args" | grep
> "[g]nome-session-binary --session=unity" | awk \'{print $1}\') && [ "$GS_PID"
> ] && logger "PATCH: kill $GS_PID ..." && kill $GS_PID '
> #>>> ?
>
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/2063383
Title:
[SRU] Ubuntu Unity takes 90 seconds to log out
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2063383/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
