Nylas-mail: Cannot log into Nylas Mail - endless Password Management Error

[oshunluvr]

Are there any related issues?

...

What operating system are you using?

...Kubuntu 16.04 / KDEneon

What version of Nylas Mail are you using?

...2.0.10

--

Bug?

Do you have any third-party plugins installed? If so, which ones?

...Can't start mail program

Is the issue related to a specific email provider (Gmail, Exchange, etc.)?

...Can't start mail program

Is the issue reproducible with a particular attachment, message, signature, etc?

...First error is:
Password Management Error
We couldn't store your password securely! For more information, visit https://support.nylas.com/hc/en-us/articles/223790028

Article at above link suggests installing libgnome-keyring-dev. The package already installed.

Second error:
Your NylasID is invalid. Please log out then log back in.
Actions like sending and receiving mail require this token. Please log back into your Nylas ID to restore it—your email accounts will not be removed in this process.

Closing second error re-opens first error again, then Nylas Mail restarts and same error loop begins again.

Log files have very odd permissions set. Last log (as far as I can tell, given the log file structure) contained only
{"host":"office","timestamp":"2017-04-14T19:31:06.359Z","payload":["ActionBridge: work Action Bridge Broadcasting: db-store-trigger"]}
{"host":"office","timestamp":"2017-04-14T19:32:06.790Z","payload":["ActionBridge: work Action Bridge Broadcasting: db-store-trigger"]}

Launching nylas-mail from terminal resulted in attached output:
bash_dump.txt

--

Feature Request?

Does this feature exist in another mail client or tool you use?

...

[h4ck3r-ky13]

I have exactly the same issue! Using Arch Linux, Gnome-keyring-daemon initialized in .xinitrc, and bspwm.

[jaredcrean]

Same issue here. Running Arch Linux with i3wm and gnome-keyring-daemon running.

[jaredcrean]

So I got past the password prompt by adding the following changes to my system. Just make sure to back these files up first. Messing up these files can lock you out of your system.

I added this to the end of the /etc/pam.d/passwd

password optional pam_gnome_keyring.so

Then adding this the end of /etc/pam.d/login

session    optional     pam_gnome_keyring.so        auto_start
auth       optional     pam_gnome_keyring.so

Then I added this line to the end of my ~/.xinitrc

eval $(/usr/bin/gnome-keyring-daemon --start --components=pkcs11,secrets,ssh)
export SSH_AUTH_SOCK

Rebooted and Nylas loads without the error

[h4ck3r-ky13]

@jaredcrean 's edits in /etc/pam.d/* solved my keyring loop

[mamantoha]

sudo apt install gnome-keyring

[ibrokemypie]

Did not solve for me

[etano]

This is broken for me as well, and the /etc/pam.d/* did not fix. I'm using Debian 9 w/ i3WM.

@ibrokemypie you ever get past this?

[ibrokemypie]

@etano seemingly so, I believe it works after starting a polkit daemon? In my case I have /usr/lib/xfce-polkit/xfce-polkit & and eval $(/usr/bin/gnome-keyring-daemon --start --components=pkcs11,secrets,ssh) export SSH_AUTH_SOCK in my xinitrc

[etano]

@ibrokemypie ultimately what fixed it for me was installing seahorse and creating a default