Bug 2526

Summary: Symbol lookup error due to an unloaded object
Product: Mageia Reporter: John Balcaen <balcaen.john>
Component: RPM PackagesAssignee: Thomas Backlund <tmb>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: balcaen.john, nic
Version: CauldronKeywords: NEEDINFO, PATCH
Target Milestone: ---   
Hardware: All   
OS: Linux   
URL: https://bugzilla.novell.com/show_bug.cgi?id=657627
Whiteboard:
Source RPM: glibc-2.12.1-11.mga1.src.rpm CVE:
Status comment:

Description John Balcaen 2011-08-28 02:09:59 CEST
Description of problem:
While trying to debug a problem with kmail2 i noticed some symbol lookup error :

/usr/bin/nepomukindexer: symbol lookup error: /usr/lib64/libldap-2.4.so.2: undefined symbol: ldap_int_tls_destroy

After some google search it seems related to a glibc problem
which seems to be fixed in Suse
you can read https://bugzilla.novell.com/show_bug.cgi?id=657627 especially https://bugzilla.novell.com/show_bug.cgi?id=657627#c62

The patch is available here :

https://build.opensuse.org/package/view_file?file=glibc-elf-localscope.diff&package=glibc&project=openSUSE%3AFactory&srcmd5=ffce69961702ab4bc63c65f202da1481



Version-Release number of selected component (if applicable):
glibc-2.12.1-11.mga1

How reproducible:
always
Mageia 1 is also affected 

Steps to Reproduce:
1.start a kde session with nepomuk enabled
2.check your ~/.xsessions-errors
3.
Comment 1 Manuel Hiebel 2011-10-30 01:32:14 CEST
Bug assigned to the package maintainer.

Keywords: (none) => PATCH
Assignee: bugsquad => tmb

Comment 2 Thomas Backlund 2011-11-08 23:40:11 CET
A fixed glibc-2.12.1-11.1.mga1 is now submitted to Mageia 1 core updates_testing 
and should be available on the mirrors in a few hours.


Is this still an issue in Cauldron with glibc-2.14.1 ?

Status: NEW => ASSIGNED

Comment 3 John Balcaen 2011-11-09 01:26:49 CET
I did not notice this error on current cauldron.

CC: (none) => balcaen.john

Comment 4 Marja Van Waes 2012-05-26 13:10:10 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 5 Nic Baxter 2015-02-14 01:16:18 CET
Cannot reproduce Mageia 5 so close

Status: ASSIGNED => RESOLVED
CC: (none) => nic
Resolution: (none) => FIXED