Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

g_set_application_name not set #10

Closed
grownseed opened this issue Jul 31, 2014 · 2 comments
Closed

g_set_application_name not set #10

grownseed opened this issue Jul 31, 2014 · 2 comments

Comments

@grownseed
Copy link

I may be missing something, but using keytar always gives me:

** (process:12345): WARNING **: g_set_application_name not set.

Possibly irrelevant, but I've never had the issue with Python's keyring.

@odensc
Copy link
Contributor

odensc commented Apr 13, 2017

This should be fixed now as keytar no longer uses gnome-keyring. @BinaryMuse ?

@BinaryMuse
Copy link
Contributor

Ah, I wasn't familiar with that call so didn't recognize it.

@grownseed This may be fixed by #63 so feel free to try out the new keytar v4.0.2 and re-open this issue if you continue to have trouble.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants