-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
net-im/element-desktop: unable to restore session if keytar is not installed #371
Comments
By any chance, have you noticed at which version this started to occur? |
Thanks for the quick response! Unfortunately not; I don't have an exact version number, but it's at least a few versions ago at this point; I've been trying to fix this for a few weeks now and finally invested some time. |
This does look similar to your issue: element-hq/element-desktop#1853 Could you mention there that it works with keytar manually installed? |
Done, thank you for finding that bug. |
Yeah, I've observed this too. Workaround is to use online build. |
Strictly speaking we need rust parts, not online build. But I guess current ebuild only builds rust parts in online mode. |
I tried making rust parts to build offline, but gave up as it is a packaging nightmare (to be honest, it even dwarfs yarn in that regard). Although there exists cargo.eclass, which might be a solution. |
Thank you for this great set of ebuilds.
Previously, I could quit and reopen element-desktop and remain logged in; when it stopped doing this (perhaps to lack of disk space), I cleared
~/.config/Element
(and~/.config/Riot
), but sessions remained unable to persist across restarts. Launching from the CLI showed that bothkeytar
andseshat
were missing; installingkeytar
vianpm i -g keytar
seems to have fixed my issue. I have not customized USE flags for this package, sonative-modules
andbuild-online
remain off.An easy solution would be to add a note in
pkg_postinst()
saying to runnpm i -g keytar
, if this is the best way to solve this (is it?). Is this expected behaviour? Are we supposed enable the USE flags mentioned above instead?The text was updated successfully, but these errors were encountered: