You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 both keytar and seshat were missing; installing keytar via npm i -g keytar seems to have fixed my issue. I have not customized USE flags for this package, so native-modules and build-online remain off.
An easy solution would be to add a note in pkg_postinst() saying to run npm 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:
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.
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: