Updated How-To for KeepassXC and Firefox for 2nd User

[klmcw]

For future readers: the reasons why /home is not a direct replacement for /var/home is covered in this thread:

Dropbox support

That is another view of the symptom. The reality is that there is nothing to move! But the code inside of the flatpak: doesn’t understand the metadata it is getting from the composefs fs type is not expecting /home to be a symlink and so is not doing the equiv of performing a stat command the follows the symlink. For example, look at the difference of this output: $ stat /home File: /home -> var/home Size: 8 Blocks: 8 IO Block: 4096 symbolic link Device: 0,39 Inode: …

TL;DR - this is because of the introduction of the composefs overlay for / - and the lack of support for it in various flatpaks, etc. Forcing the app to look at /var/home forces it to examine a fs type for which it does have awareness.

The details are in the linked thread above …