Comment 53 for bug 1718658

I hate to say this, folks, but ecryptfs looks like a dead end for us. It's no longer supported by Ubuntu (the package has been moved to the Universe repo). Also, the problem at hand is caused by systemd, which is run by a man famous for releasing poorly-vetted, system-breaking software, and then refusing to fix the damage he causes.

For a year or so, I maintained a systemd patch to work around this bug. (It is posted above, but no longer applies to current systemd code.) There was a time when it looked like the problem was finally fixed upstream, but then it just broke again.

Anyone who (like me) has been using ecryptfs to encrypt a private directory and unlock it only when needed, might consider switching to gocryptfs. From a user's point of view, it works similarly to ecryptfs. There's also a handy GUI called SiriKali that works with it.
https://nuetzlich.net/gocryptfs/
https://mhogomchungu.github.io/sirikali/

Good luck.