Ximin Luo

BTW, since you are rewriting everything, do you think you could use libsecret instead of libgnome-keyring? That would work for KDE keyring too, I believe. There is more information about...

Thanks, I agree. I do not have much time to work on this myself however. If you could find documentation on that format, it would be much appreciated!

Seahorse displays the secret type as "Google Chrome password" and stores attributes like the following: submit_element: scheme: 0 action_url: **** username_value: **** ssl_valid: 0 origin_url: **** application: chrome-6717484 signon_realm: ****...

unfortunately, "auto-complete" _does_ exhibit this behaviour in certain cases, i.e. when the other keyrings contain a MATCH for the current domain to be auto-completed on.

the GNOME search functionality does not allow searching by keyring. currently we are getting results from all keyrings back, then filtering by keyring ourselves. unfortunately, GnomeKeyringFound contains char\* secret as...

libsecret (the successor to libgnome-keyring) will allow this. https://bugzilla.gnome.org/show_bug.cgi?id=672356

Ouch man that sucks :( I'm not an expert on this issue but it may be more mozilla's fault than ubuntu - upstream does not make xulrunner easy to package...

thanks, will release a new version as soon as i have some personal time

The sync service should be using mozilla APIs to get the password via this extension in the same way the firefox interface gets the list of passwords via this extension....

Did sync work for the original database when this extension is disabled? I noticed that "show passwords" no longer works with gnome-keyring 3.4, maybe this is the real cause of...