Bug 38924 – tripwire segfalts after emerge -u world (suspect new glibc)

• Status: RESOLVED WORKSFORME
• Product: Gentoo Linux

[Description Richard 2004-01-21 08:22:36 UTC]

After an 'emerge -u world'  on my 'Gentoo Base System version 1.4.3.10' system ( I do not use 'ACCEPT_KEYWORDS="~x86" ) running 'tripwire --check' returned a segmentation fault.  (The emerge -u world did NOT update tripwire.) (Tripwire was working well before the 'emerge -u world')

I suspect that this was caused by glibc being emerged to version: glibc-2.3.2-r9
Just a guess.

I fixed the issue by re-emergeing tripwire ( 'emerge tripwire')

IF this was caused by the newer glibc, shouldn't there be a dependency that causes tripwire to auto re-emerge when the newer glibc was emerged?

Reproducible: Always
Steps to Reproduce:
1. /usr/sbin/tripwire --check
2.
3.

Actual Results:  
Segmentation Fault

Expected Results:  
< tripwire report >

[Comment 1 Daniele Arduini 2004-02-14 07:10:15 UTC]

Same behavior on my system: NOT using ~x86 ebuilds, tripwire stopped working (Segmentation fault) after an emerge -uv world, now works again after an emerge tripwire.

[Comment 2 Tavis Ormandy (RETIRED) 2004-02-14 08:22:30 UTC]

Hmm, interesting.  I'll look into it.

[Comment 3 Jakub Moc (RETIRED) 2005-08-12 13:18:35 UTC]

Is this still even remotely an issue after 1 1/2 years?

[Comment 4 Tavis Ormandy (RETIRED) 2005-08-22 11:09:20 UTC]

The -r2 ebuild seems to work for me in these circumstances, please reopen if 
it's still an issue.