Config files not updated

snapd
21

Ok.

We currently do not fully support running snapd on a system where users’ homes are not accessible by root all the time. This means ecryptfs, automount, etc., are not fully supported.

This is because snapd currently does operations on the user’s data as part of refreshes, removals, etc. and if the user’s data disappears, then the system’s state will be inconsistent.

You can work around this limitation on single-user systems by controlling or limiting when snapd refreshes, in order to ensure that it’s always done (either manually or automatically) when the user is logged in.

We appreciate that this is inconvenient and are wanting to address it, but it’s not going to get fixed before 19.04.

1 Like
22

ok.
may i suggest this:

  • copy AND current link renew should be done only when the user is loggued in, not at boot time or outside sessions
  • new clean config files (reseted) should be created only when there is no ones in directories.
  • for other cases, a copy of last one should be done instead.
23

Hey

We discussed many issues related to encrypted home directories and to working with user data in general. We have no implementation at this time but we have a solid plan to relay such changes through the “userd” service running inside a per user session environment.

1 Like