Bug 223785

Summary:	prelink causes lot of "Warning: ignoring invalid out-of-map direct binding for symbol" messages
Product:	[openSUSE] openSUSE 10.2	Reporter:	Marvin FourtyTwo <marvin24>
Component:	Other	Assignee:	Marcus Meissner <meissner>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	grep output of .xession-errors

Description Marvin FourtyTwo 2006-11-26 15:03:47 UTC

hi,

prelinking my RC1 system (with "prelink -avmRf") causes many c++ applications to throw out "Warning: ignoring invalid out-of-map direct binding for symbol ..." messages. This fills up my .xession-errors file very quick and causes very long loading times. Must have something to do with a glibc extension (don't know the name of it anymore).

thanks

Marc

Comment 1 Matej Horvath 2006-11-27 22:37:37 UTC

Please attach your /var/log/Xorg.0.log, .xession-errors and /var/log/messages. 
Thank you.

Comment 2 Marvin FourtyTwo 2006-11-28 08:31:36 UTC

Created attachment 107149 [details]
grep output of .xession-errors

Comment 3 Marvin FourtyTwo 2006-11-28 08:32:41 UTC

well, I attached the grep "out-of-map" output of .xsession-errors. There are no abnormal lines in Xorg.0.log or messages, so I leave them out here.
Programs, which cause these messages are e.g. konqueror, kmail and lyx. Simple programs like kcalc or kedit so dot, but kate does.
This should be simple to reproduce or something if terrible wrong with my system.

Comment 4 Marvin FourtyTwo 2007-01-04 13:24:07 UTC

any news on this?
has someone been able to reproduce it?

p.s. still exists in released version 10.2

Comment 5 Marcus Meissner 2007-01-04 13:30:59 UTC

did not have time to look at it.

Comment 6 Marvin FourtyTwo 2008-07-16 19:11:13 UTC

... pong 

is there a "bug is to old to be fixed" status in bugzilla? 

I can't reproduce this anymore, because have no v10.2 anymore. It didn't happen with 10.3 and 11.0, and noone seemed to care anyway. So I'm closing it as "won't fix".