Bug #12999

Stopping session-c1.scope after starting tails

Added by cypherpunks 2017-06-23 11:49:45 . Updated 2017-06-23 12:04:47 .

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2017-06-23
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

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?


Subtasks


Related issues

Is duplicate of Tails - Bug #12092: The Greeter keeps eating lots of memory after logging in Resolved 2016-12-27

History

#1 Updated by intrigeri 2017-06-23 12:04:25

  • is duplicate of Bug #12092: The Greeter keeps eating lots of memory after logging in added

#2 Updated by intrigeri 2017-06-23 12:04:47

  • Status changed from New to Duplicate

Thanks for the hint! I’ll point Bug #12092 to it.