Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 462106

Summary: net-im/pidgin-2.10.7 - Installation with sasl USE flag breaks libirc functionality.
Product: Gentoo Linux Reporter: Matthew <logical.zero>
Component: Current packagesAssignee: Gentoo Net-im project <net-im>
Status: RESOLVED DUPLICATE    
Severity: normal CC: logical.zero
Priority: Normal    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701541
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: emerge --info pidgin

Description Matthew 2013-03-17 22:07:54 UTC
If enabling the `sasl` use flag when emerging pidgin, pidgin's IRC functionality ceases to function. Current recorded IRC accounts are marked as type "Unknown" and IRC is removed from the list of available account types.

gdb'ing pidgin reveals the following line:
plugins: /usr/lib64/purple-2/libirc.so is not loadable: undefined symbol: sasl_client_step

This seems to be a similar issue reported for Debian: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701541

Reproducible: Always

Steps to Reproduce:
1. emerge pidgin with the sasl USE flag
2. start pidgin
3. attempt to create an IRC account / use an existing IRC account
Actual Results:  
IRC accounts with pidgin are unusable and not recognized by Pidgin

Expected Results:  
IRC accounts with pidgin should be useable and createable

Recently upgraded kernel to 3.7.10, Gentoo sources 13
Comment 1 Matthew 2013-03-17 22:09:57 UTC
Created attachment 342434 [details]
emerge --info pidgin
Comment 2 Matthew 2013-03-17 22:17:58 UTC
Something I forgot to mention: If you emerge again without `sasl`, IRC accounts are useable again.
Comment 3 Manuel RĂ¼ger (RETIRED) gentoo-dev 2013-03-18 06:32:31 UTC
possible dup of bug #461530 

this is fixed upstream already via
https://hg.pidgin.im/pidgin/main/rev/944ec96bb103
Comment 4 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2013-03-18 08:08:37 UTC

*** This bug has been marked as a duplicate of bug 461530 ***