pidgin: symbol lookup error: pidgin: undefined symbol: purple_core_ensure_single_instanceI tried reinstalling via Synaptic. No avail. I read through this thread, and there was no known solution. So, the only apparently solution was to install Pidgin via source.
[UPDATE: There is now a solution to this without recompiling Pidgin. Taken from this thread. Go to /usr/local/lib and delete these files: libpurple.so, libpurple.so.0, libpurple.so.0.0.1, and libpurple.so.0.0.2. So, essentially:
cd /usr/local/libAnd the next time you run Pidgin, it should work. You might not have all of these files, but it will remove the ones that you do have, which is what is important.]
sudo rm libpurple.so libpurple.so.0 libpurple.so.0.0.1 libpurple.so.0.0.2
[NOTE: This guide was
The first thing you want to do is remove the installed version of pidgin. That can be done via:
sudo apt-get remove pidgin pidgin-dataNext thing, you download the source code.
After that, you unpack it and move into the folder (Firefox downloads things to my Desktop, so I'm using the code to do that):
cd ~/DesktopNext you start the build cycle. Unlike the guide that was linked to, configuring without any options worked fine for me, so that's what I did:
tar -jxvf pidgin-2.2.1.tar.bz2
./configureNext, you use make (you don't HAVE to be root to do this, but you can):
makeLastly, you can end with the traditional, sudo make install, but I choose not too. It's far too messy for me. I use the checkinstall tool, which compiles the source into a .deb which is then listed in Synaptic. However, just doing "sudo checkinstall" does not work. This is where I'm thankful for that guide. The successful command goes like this:
sudo checkinstall --exclude=/etc/gconf,/usr/bin,/usr/libCongratulations, pidgin should now be installed and able to be successfully run. However, I recommend doing the fix described at the beginning of this post. If you install from source via checkinstall, the Update Manager will keep bugging you to upgrade to the version of pidgin in the Ubuntu repos, which still have that problem. However, if you fix the Ubuntu version as described, it won't bother you. Well, I hope this guide was of help to someone, and if it wasn't, too bad. It was a help to me!