Ubuntu
pidgin-otr package

pidgin resolver process crashes with ldap accounts

Bug #248684 reported by Oliver Lemke
42
This bug affects 3 people
Affects Status Importance Assigned to Milestone
pidgin-otr (Debian)
Confirmed
Unknown
pidgin-otr (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: pidgin

When using ldap accounts pidgin (1:2.4.3-0ubuntu1~hardy1) is not able to login to any of my accounts. The error message it gives is:

Could not connect to authentication server: Unable to send request to resolver process.

It seems that the resolver process crashes if the system uses ldap user accounts. Temporarely removing ldap from /etc/nsswitch.conf makes it possible to start pidgin and log in to all accounts. See attached 'pidgin -d' output for details.

Revision history for this message
Oliver Lemke (olemke) wrote :
Revision history for this message
Jurgen Haan (jurgen-easyflex) wrote :

Assuming you're talking about ldap unix accounts and not about ldap im accounts.
This seems to be caused by the pidgin-otr plugin.
Both the pidgin program and the plugin are compiled against libcrypt, and (I read) this causes a problem.
simply by mv-ing /usr/lib/pidgin/pidgin-otr.so to pidgin-otr.so.bak, you can at least use pidgin as your current user while still using LDAP.
I myself am not a developer and have only somewhat mediocre knowledge about this stuff, but this fixed the problem for me.
I only hope the next update I receive on pidging has a fix or workaround for this.

Revision history for this message
Oliver Lemke (olemke) wrote :

Thanks Jurgen, your workaround fixed the problem.

Revision history for this message
Caspar Clemens Mierau (leitmedium) wrote :

Thank you for the report. I hereby confirm this bug.

Changed in pidgin:
status: New → Confirmed
Revision history for this message
Caspar Clemens Mierau (leitmedium) wrote :

moved to pidgin-otr

Revision history for this message
Luis Mondesi (lemsx1) wrote :

I was bitten by this today and moving pidgin-otr worked for me.

what a bug...

Revision history for this message
T-Bone (varenet) wrote :

For the record, this bug is not exactly pidgin-otr's fault. It's a "feature" of libgcrypt, by which it can't be used as a shared library by more than one client in the same program (it uses unprotected global variables). libldap and pidgin-otr both use libgcrypt, thus when you use both in pidgin, it goes kaboom. This problem seems to be mostly ignored on libgcrypt's side though.

Revision history for this message
pidgin-otr-is-br0ken (pidgin-otr) wrote :

Will this be fixed in pidgin-otr? or libgcrypt? or what? I currently log in on my work machine through ldap, so pidgin-otr is unusable, but I'd really like to use it.
Thanks

Revision history for this message
Phil Pratt-Szeliga (pcpratts) wrote :

working on it in my free time

Changed in pidgin-otr:
assignee: nobody → phil-pratt-szeliga
status: Confirmed → In Progress
Phil Pratt-Szeliga (pcpratts)
Changed in pidgin-otr:
assignee: phil-pratt-szeliga → nobody
status: In Progress → Confirmed
Bug Watch Updater (bug-watch-updater)
Changed in pidgin-otr:
status: Unknown → Confirmed
Revision history for this message
Sven Neuhaus (sven-neuhaus) wrote :

So, is it a good idea to report this as a libgcrypt bug instead?

Revision history for this message
Sven Neuhaus (sven-neuhaus) wrote :

I'm curious - how does Kopete implement OTR? Maybe it does not rely on libgcrypt?
I can use kopete with its OTR plugin on the same system with LDAP just fine...!

Daniel T Chen (crimsun)
Changed in pidgin-otr (Ubuntu):
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.