One problem I had after a fresh EnOS install using i3 WM based on @joekamprad fine configuration scripts: I could not get my Nextcloud Desktop app to register my login credentials and it would repeatedly open a browser instance to authorize my login. Once completed it synced my files as usual.
I came across @Buckfae’s topic Automatically unlock gnome-keyring where he needed visual-studio-code-bin for code synching and so I tried adding gnome-keyring package as well as seahorse as I knew the latter program works in the Xfce4 WM.
However, after installation seahorse shows up in the rofi menu as “Passwords and Keys” as normally in Xfce4 but it contained no “login” entry and using its menu to add another type of key, nothing showed up. So I decided to follow the PAM step method described in the Arch Wiki and lo and behold the “login” entry appeared in Seahorse. However it is unlocked which I think is normal, but I’d feel safer if anyone more knowledgeable could confirm this.
More usefully, though, for me now, the authorizing key to enable Nextcloud to sync my files works automatically as well and I didn’t have to enter my login credentials either. This is a bit of a mystery to me as I would have thought I’d need to at least login once manually for the key to be saved.
My other related question concerns another entry in the Arch Wiki about Using gnome-keyring outside desktop environments. Here they say that a dbus command has to be issued “during window manager startup” but I could find no mention of what the command would be for i3. Is this also necessary?