Bug 128213
Summary: | net join rpc segfaults | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joachim Sauer <jsa> |
Component: | samba | Assignee: | Jay Fenlason <fenlason> |
Status: | CLOSED CANTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | jfeeney, mattdm, tim |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-10-30 14:09:38 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Joachim Sauer
2004-07-20 08:51:01 UTC
I think I have very similar problem with current samba (3.0.6-2.fc2) and joining an ADS as the "net ads join" command seg faults on join. However "net rpc join" works I have now installed the i386 rpm of samba client and I can join and use the ADS domain without problems. This is still a problem on x86_64 in FC3 (even current development version - 3.0.8-3) Please move bug up to FC3, so that we can have this fixed? Fedora Core 2 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC3 updates or in the FC4 test release, reopen and change the version to match. Closing per lack of response to previous request for information. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. Please install a still supported version and retest. If it still occurs on FC5 or FC6, please reopen and assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier. This bug is fixed in current versions of fedora core |