Bug 132979
| Summary: | exporting DISPLAY via hostname fails | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 3 | Reporter: | Matt Jamison <jamisonm> |
| Component: | XFree86 | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
| Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.0 | Keywords: | Triaged |
| 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: | 2005-04-15 11:04:13 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
Matt Jamison
2004-09-20 16:22:57 UTC
Does this problem only occur if the hostname is changed while the X server is running, or does it also occur if you do a full system reboot, in which the machine's hostname gets assigned via DHCP on system startup, prior to the X server starting? Thanks in advance. Setting problem status to "NEEDINFO". from customer: The problem seems to be how the X server resolves the client hostname, in this case our PCs with DHCP assigned addresses. This problem occurs everytime the client hostname starts with a number. If I define my pc's address (to start with an alphabet) in the /etc/hosts file and make the corresponding change in the /etc/nsswitch.conf (to override DNS name resolution and use local file), the display works. I get a display back if I set my client PC (runningThe DISPLAY variable to an IP address. It does not seem to be a problem with the DNS, we can do forward and reverse lookups without any problems. The problem is always reproducible. I went and checked RH's bugzilla all day yesterday but did not find anything close to what we are seeing here. This is kind of holding us back in rolling-out our 64-bit machines with update 3 patches. any update? Bug #134883 appears to be the same issue, along with: https://freedesktop.org/bugzilla/show_bug.cgi?id=1605 |