Snapd should not start if there are no Snaps installed
Bug #1730159 reported by
Simon Quigley
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bionic |
Fix Released
|
High
|
Unassigned |
Bug Description
If there are no Snaps installed (or maybe just the core Snap), snapd should shut down on boot so it does not use up resources which are not needed by the user. This would be useful in situations where installing snapd is mandatory but the user has no desire to use it (some Ubuntu flavors).
Related branches
~lubuntu-dev/ubuntu-seeds/+git/lubuntu:lp.1730159
Merged
into
~lubuntu-dev/ubuntu-seeds/+git/lubuntu:disco
at
revision e363bfda004ab733b31a2c87410f9fda1a3f18e6
- Simon Quigley: Approve
-
Diff: 25 lines (+0/-6)2 files modifiedblacklist (+0/-5)
supported (+0/-1)
tags: | added: id-5acd1db06f41344de82489f0 |
Changed in snapd (Ubuntu): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Since there is a snapd.socket unit, if snapd is stopped, it can correctly autostart on invocation of the 'snap' command. So this seems like a reasonable change to remove memory pressure from snapd when it's not in use.