On Wed, Jun 09, 2021 at 05:10:58PM +0200, Meikel wrote:
Am 09.06.2021 um 01:19 schrieb Jonathan Billings:
> The problem is caused by your sshfs homedir and gnome-keyring:
>
>
https://bugzilla.gnome.org/show_bug.cgi?id=730587
> <
https://bugzilla.gnome.org/show_bug.cgi?id=730587>
>
> It is a rather old bug, and it doesn’t seem likely that it’ll be fixed
> any time soon. Basically, if you have a fuse mounted sshfs home
> directory, you can’t use gnome-keyring.
This explains the problem sufficently for me. I need to decide if I can get
rid of gnome-keyrings and if not then I have to get rid of sshfs-mounted
home directory.
So, I've worked with some network filesystems that behave poorly with
certain daemons, and one of the solutions I've used was to have a
login process copy the data into $XDG_RUNTIME_DIR
(i.e. /run/user/$UID) and then point the daemon there. Of course, you
need a cleanup process that copies it back (or syncronizes it
periodically).
It's nice that GNOME's dconf has figured this out already, and you can
set "service-db:keyfile/user" in /etc/dconf/profile/user instead of
"user-db:user", that makes dconf copy the user's config into
XDG_RUNTIME_DIR and then periodically sync it back to $HOME as a text
file. I suspect you might get some mileage out of that if you use
sshfs.
If you're familiar with windows, it would be like Folder Redirection
and Roaming Profiles.
Semi-off-topic:
I actually started working on a user daemon that does the sync for a
configurable set of directories/files in $HOME, so you could, for
example, create a tmpfs for $HOME and sync files from a network
homedir. Why do this? Because that network homedir might not support
things like hard links, sockets, fifos, or just be really slow. The
idea would be to set XDG_CONFIG_HOME at the slow network filesystem,
and other XDG_ variables, as described here:
https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
One idea I had was that you could even use this with services like
Dropbox (with a proper encryption layer in front of it). Use something
like rclone's autofs support:
https://github.com/rclone/rclone/wiki/rclone-mount-helper-script
... or just sync directly using the native sync client or the
provider.
--
Jonathan Billings <billings(a)negate.org>