So this is probably more a documentation issue for Synchronize with Gramps - Gramps Web but I couldn’t find any easy way to submit a documentation “bug” report. I use gramps and grampsweb on Fedora and after typing my password into grampswebsync numerous times I decided to try and save the password. I saw that this required the python keyring module and promptly ran
dnf install python3-keyring
which installed the necessary keyring and secretservice modules. And after many crashes trying to figure out what went wrong I stumbled on this old (stil open) bug report
Backend inference between KWallet and Gnome leads to unexpected results · Issue #496 · jaraco/keyring · GitHub
and burried in the comments the needed workaround:
For those looking for the workaround like I was, here it is. This will cause keyring to use GNOME’s keyring instead of kwallet on systems similar to mine. Make sure the Python package secretstorage is installed. Then create the configuration file ~/.config/python_keyring/keyringrc.cfg and edit it to look like this:
[backend]
default-keyring=keyring.backends.SecretService.Keyring
So in summary, if you’re using KDE, the instructions on the sync page work fine, but if you’re using Gnome (at least on Fedora and probably others) you may need that workaround to prevent crashes. Since the bug is not in any part of gramps but rather the python module, there’s probably little that can be done here, but document it.