|Summary:||XFree86 writes over /usr/X11R6/bin/X link|
|Product:||[Retired] Red Hat Linux||Reporter:||d-mueth|
|Component:||Xconfigurator||Assignee:||Preston Brown <pbrown>|
|Status:||CLOSED WONTFIX||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2000-01-14 17:30:11 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description d-mueth 1999-09-28 20:43:19 UTC
XFree86 writes over the /usr/X11R6/bin/X link, automatically changing the default X server. For users who are not using XFree86, this creates a lot of confusion. In my case, I have autorpm automatically upgrading RH errata, and XFree86 is not configured(I'm using Accel-X), so X suddenly broke. Solutions? 1) Could this link only be made on an install (rpm -i) and not an upgrade (rpm -U) ? 2) Could this link only be made if the link does not already exist? I think (2) would be best. At any rate, it should be smart enough that if the link exists and points to a non-XFree86 server, it does not write over it.
Comment 1 Preston Brown 2000-01-14 17:30:59 UTC
if accel-X doesn't use Xwrapper, that is their packaging issue, not ours. Dealing with this special case will be difficult, to say the least, and will probably result in far more bug reports from people who it may potentially fail for who use XFree86 rather than Accel-X. We have to provide the best solution for the majority. I'd talk to XIG about this.