Bug 2132
| Summary: | after su as user root programs can't find user X server | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | mark_evans |
| Component: | XFree86 | Assignee: | David Lawrence <dkl> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 1999-04-12 20:31:24 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
mark_evans
1999-04-11 22:40:32 UTC
You must use xauth to add authority for root to your display. man xauth for more information. hopefully, su will be modified to do xauth automatically via pam before release, but if not, you will have to use xauth manually. My workaround for this problem is to explicitly set a XAUTHORITY environment variable that points to my .Xauthority file. As long as one uses su instead of 'su -' (which would wipe out the environment) and as long as root can still read the file after su'ing (not always true in some NFS environments), this lets programs run after the su still have access to the right xauth data. A short-term workaround for RedHat might be to add something like this to their XDM and/or startx script environments. |