Anytype does not maintain login session on Arch Linux
Have you read a contributing guide?
- [x] I have read CONTRIBUTING.md
- [x] I have searched the existing issues and didn't find any that were similar
- [x] I have considered creating a pull request with fixes instead of a bug report and want to proceed
Current Behavior
Description: On Arch Linux, Anytype does not persist the logged-in session after closing and reopening the application. Every time I start Anytype, I am prompted to log in again. This issue persists regardless of installation method (AUR).
Expected Behavior
The application should retain the logged-in session across restarts, allowing the user to remain authenticated without needing to log in again after closing and reopening Anytype.
Steps To Reproduce
Steps to reproduce:
Open Anytype and log in. Close the application completely. Reopen Anytype. Notice that the login session is not maintained, and the app prompts for login again. Expected behavior: The application should retain the logged-in session across restarts.
Environment
System Information:
OS: Arch Linux (fully updated)
Anytype Version: 0.44.0
Installation Method: AUR
Anything else?
No response
Do you have libsecret package installed?
I'm having the same problem. AnyType works as expected in KDE Plasma but when I login to Hyprland, AnyType requires me to login although pam_kwallet_init is launched at login and the default kdewallet is open.
signal-desktop has a --password-store=kwallet6 option that lets me specify where to find the data it needs to unlock. Ideally AnyType would have a similar option.
signal-desktophas a--password-store=kwallet6option that lets me specify where to find the data it needs to unlock. Ideally AnyType would have a similar option.
It does, every chrome/electron application has that option!
OK, I just logged out of KDE Plasma and into Hyprland and lo and behold AnyType unlocked without having to try using the --password-store switch (which didn't work previously either).
I just rebooted and logged directly into Hyprland and AnyType still unlocked successfully (without the --password-store option), so that's great.
I'll eventually test with gnome-keyring and/or keepassxc, and see how it goes.
keepassxc, and see how it goes.
With keepassxc is how I am using it.
Can I close the issue? We have several topics on forum regarding this problem, at the moment there is no another solution as described, until we rework the keychain logic. Feel free to reopen if you feel otherwise.