-
Notifications
You must be signed in to change notification settings - Fork 6
Unable to login #4
Comments
Sorry, I'm going to be a little slower and less responsive during the holiday season. From a brief check, it looks like keyring is complaining that it doesn't have a backend. Take a look at that page and see if that makes sense and if you can install any of the secret backends it supports. Keyring is necessary because we have to store an access token for Google (otherwise you would have to login again every time you use the plugin). I'll see what I can do about making this error message friendlier and more actionable when I get a chance. |
Looking at this again, it seems like keyring is maybe recognizing a backend but is having problems with it. It looks like you're on Arch, are you running headless? Some relevant links I found:
|
Sorry for bugging you during the holidays. I had some alone time and was redoing my nvim config while reading reddit and stumbled across your package. I'm running kde so it's probably trying and filling to get to kwallet. Will look at the links and report back when I get the opportunity. |
No worries! I hope you find the issue, and let me know if there's anything I could add that would make debugging this easier. At a minimum I'll probably add some additional documentation around |
I'm also seeing this behavior with latest commit on MacOS. I installed everything for the first time today and had it working but then it broke and it won't login anymore. I've tried reinstalling and manually cleaning but it won't prompt me for email again, just password.
Debug log excerpts:
|
@dittoalex when you say you are also seeing this behavior, does that mean that you're seeing the error posted in the original issue? What happens when you try to log in? It sounds like it's not prompting you for an email (that's expected, and shouldn't be an issue unless you want to change the email), but after you enter your password...is there an error? Does it spin forever? I'll need more information to debug. If you want to fully reset the state, do a |
When I saw the above behavior I did not see an error message like in the original issue, but thought it was being eaten by an exception. It felt like it was spinning forever. I tried logging out about a dozen times in my troubleshooting and kept getting "Cannot perform action while Gkeep is Uninitialized." I again tried logging in tonight, same behavior. The customization process during which gkeep.nvim broke I was following README.MD with a fresh install of nvim dedicated just for gkeep.nvim and the minimum amount in .nvimrc. It may be that the failures are due to my having too-large notes in Google Keep. For years I've had a bug where the items in my notes would get randomized, and that's what led me to gkeep.nvim. While troubleshooting gkeep.nvim I did another search and found recent support post "Google Keep Notes Checklist items re-arrange / get jumbled in random order for unknown reason" , which seems to be caused by character limits in notes. I spent the weekend paring things out of my notes through the browser, while items were being randomized, and will be moving away from Google Keep. |
Oof, yeah Keep does have some hidden, relatively small character limits in the product. Unfortunately I wouldn't expect gkeepapi to behave any better once you hit that because the behavior becomes undefined. Sorry you're hitting these issues and good luck with finding a replacement! |
@stevearc, the errors I get rn on running
|
Looking around, it sounds like your system may be missing the "login" keyring? I found several references to this issue with VS Code live share microsoft/live-share#219. You can try some of the solutions they listed there. If you want a very small repro, |
@stevearc the command failed. I don't think I'd want to deal with this anymore. Feel free to close the issue. BTW, I hate python. It hasn't given me anything other than problems. |
Describe the bug
Unable to login. After I enter my email, I get the error. I'm not prompted for
any password.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Version information
Linux arch 5.15.10-zen1-1-zen #1 ZEN SMP PREEMPT Fri, 17 Dec 2021 11:17:39 +0000 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: