Stopping session-c1.scope after starting tails

I’ve been having memory problems with tails 3.0 and I thought the cause was my current gnome-shell session. But upon further investigation it turned out that the real problem was the Xorg instance for gdm running as user-114.

I was able to reclaim a huge portion of memory by killing Xorg, then I thought if it’s possible to do it in a cleaner way and I came upon these commands:

systemctl stop session-c1.scope
systemctl disable session-c1.scope
systemctl reset-failed

I wonder why session-c1.scope is even necessary after starting tails from the greeter? why not stop it by default after starting the vt2 xorg?

Related issues

• Is duplicate of #12092 (closed)

Original created by @cypherpunks on 12999 (Redmine)