Red Hat Bugzilla – Bug 46218
startx and Xwrapper problem and solution
Last modified: 2007-04-18 12:34:12 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22 i686; en-US; m18)
Description of problem:
I can't see how startx ever could have worked in RH7.0,
nevertheless, this is what it took to get it working for me.
Change line 33 in startx to say server= instead of serverargs=
Otherwise the args end up in the wrong order down the bottom
with display coming before the server which is wrong. Then
X must be a symlink to the specific X server I am using
(i.e. not a link to Xwrapper.). Then there must be a
xserverrc file that execs Xwrapper. The final outcome here
is that startx execs xserverrc which execs Xwrapper which
execs X which is a symlink to my accelerated server.
Having X a symlink to Xwrapper doesn't seem to work because
Xwrapper doesn't know which accel server to start.
Steps to Reproduce:
1. default RH7.0 startx doesn't start, just hangs.
When I said RH7.0, I meant RH7.1.
*** Bug 46217 has been marked as a duplicate of this bug. ***
startx works fine in all releases of Red Hat Linux. I use startx
exclusively ever since RHL 5.0, so this bug is totally unreproduceable
by me. Can you reproduce this on a fresh clean install (not upgrade)?
I don't have the facilities to do a clean install.
I have been continuously upgrading since many RH
versions ago. Feel free to close this bug if it
looks like it's going nowhere.
However, I would appreciate it if you could clarify exactly how
the Xwrapper stuff is supposed to be setup. I suspect something
somewhere has got screwed up in the RH upgrade path. Is my
setup above correct? I can never actually figure out how Xwrapper
is supposed to figure out which X server to run. The above works,
but I don't think it is how RH comes out of the box.
Xwrapper is not supposed to be ever touched by the end user.
Xconfigurator manages the X configuration symlinks automatically.
Doing any configuration by hand is not supported. Always use
Xconfigurator to choose either the 4.x server, or a 3.3.6 server
using the --preferxf3 and --preferxf4 commandline options. That is
more of a tech support issue though, which bugzilla isn't intended
The startx issue you describe however needs some further looking into.
I'll need to test it out on a clean installation to see what happens.
The X server that gets ran, is a symbolic link which is configured by
Xconfigurator. Closing bug as NOTABUG as it seems to have been just
a local configuration mishap or somesuch.