Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 24445 - xfree with ipv6 SmsGenerateClientID fails, leading to "...severely misconfigured" warning when starting kde
Summary: xfree with ipv6 SmsGenerateClientID fails, leading to "...severely misconfigu...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal
Assignee: Gentoo X packagers
URL:
Whiteboard:
Keywords:
: 24446 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-07-14 04:20 UTC by fschneider
Modified: 2003-12-04 00:57 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
fixed patch (2000_all_4.3.0-ipv6-server.patch,189.43 KB, patch)
2003-11-27 16:28 UTC, Andrew Bevitt
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description fschneider 2003-07-14 04:20:36 UTC
xfree-4.3.0-r3 
 
error in  2000_all_4.3.0-ipv6-server.patch 
 
patched file: 
 
xc/lib/SM/sm_genid.c 
 
error: when ipv6 is enabled when building xfree, 
the function SmsGenerateClientID misinterpretes 
the return value of getaddrinfo, resulting in 
generating no ID. 
 
This leads to the "...is severely misconfigured" 
warning message from ksmserver when starting kde 
 
 
line 140: 
    if (getaddrinfo(hostname,NULL,NULL,&ai) != 0) { 
should be 
    if (getaddrinfo(hostname,NULL,NULL,&ai) == 0) { 
 

Reproducible: Always
Steps to Reproduce:
1. emerge xfree-4.3.0-r3 with USE="ipv6" 
2. start kde with startx 
3. 



I have only tested the SmsGenerateClientID sm_genid.c alone and with the correction 
it now generates an ID, but I didn't do a complete re-emerge of xfree with the patched line.
Comment 1 Martin Holzer (RETIRED) gentoo-dev 2003-07-14 04:55:37 UTC
*** Bug 24446 has been marked as a duplicate of this bug. ***
Comment 2 Andrew Bevitt 2003-11-27 16:28:57 UTC
Created attachment 21392 [details, diff]
fixed patch

I just checked the 4.3.99 code and this change is the case in the
no patched code, it looks like the 4.3.0 patch was back ported 
at a stage when a bug existed in the 4.3.99 code. 

Attached updated patch, that has the problem solved, barring no
release problems this fix should go into 4.3.0-r4's patchset.
Comment 3 Donnie Berkholz (RETIRED) gentoo-dev 2003-12-04 00:57:35 UTC
Added the patch in comment #2 to 4.3.0-r3. Please test and reopen if this is not fixed.