After working for some time, Pidgin starts asking for passwords on every reconnection, like they were not ever present. I think that happens after Pidgin loses connection for the first time, e.g., when you put the computer into sleep. There are no debug messages related to keyring or passwords when I start pidgin -d. Your plugin is great, but this problem freaks me out. It works fine on another PC, by the way. What should I try to do and what additional info should I give to you?

It would be great, if this plugin could also store its passwords in kwallet and not just in gnome-keyring.

Hi!
I use pidgin-gnome-keyring v2.0 from debian unstable. I see that its do not retrieve passwords from keyring after reconnect. I just see prompt is password widget. It is common problem for all protocols.

Based on https://launchpadlibrarian.net/158290638/pidgin-gnome-keyring_1.22~saucy-1_source.changes and fcec00c I'm guessing that this is now the canonical repository for Pidgin Gnome Keyring?

If so, please note that the PPA is no longer building correctly for most versions of Ubuntu, including Saucy:

https://launchpad.net/~pidgin-gnome-keyring/+archive/ppa/+packages

Hi, I am new to both pidgin and to the Gnome keyring, and so unsure that this is the right place to query about the following:
Running Gnome3 desktop on 4-13.5-1-ARCH (x86_64), I just installed 'pidgin', 'purple-plugin-pack', 'purple-skype-web', 'pidgin-lib-notify'... Also installed Purple Telegram, and 'purple-gnome-keyring 1.1-3' from AUR.
All is well except that, everytime I launch pidgin, I get a small window with the foll0wong message: "Gnome Keyring Plugin could not load collection" with a close button. Can you give me pointers so I can troubleshoot this ? Or is it just me ?
Any pointer will do so I can be on my way. Cheers. -ced

Hello,

At the moment, running 'make install' places the plug-in in $DESTDIR/usr/lib/purple-2/. This will not work as expected in a lot of cases, for instance on amd64 machines running RedHat-compatible distros (in which case the plug-in should go into /usr/lib64/purple-2/ - /usr/lib is for 32-bit libraries only). A much better way would be to simply ask libpurple, via pkg-config, where its plug-in directory is:

PLUGINDIR = $(pkg-config --variable=plugindir purple)

...

mkdir -p ${DESTDIR}/${PLUGINDIR}/
cp ${TARGET}.so ${DESTDIR}/${PLUGINDIR}/

It seems pidgin-gnome-keyring does not support creating new keyring, even though
there is an option in the configuration window for this.

I've tried to make this plugin use a keyring called "pidgin", and it still uses the previously created
keyring.

Of course, I have restarted pidgin and tried again.

And probably other protocols too.

All collected info: dequis/purple-facebook#48

Hi, I'd be interested in packaging this software more "properly" for Debian, e.g. like mozilla-gnome-keyring. This requires clarifying the license. I see that make_package.py mentions gpl2 but could you explicitly state this in a COPYING file, and also clarify if you'd like to make it "GPL-2" or "GPL-2 or later"?