Skip to content

X11 Server startup Weirdness (and a fix) in Panther

For some reason, when I upgraded to Panther my Dock shortcut to the X11 Server
busted. After fiddling around I noticed in the Consoloe that it was complaining
about some unrecognized option when launching. I found X11 in the
Applications directory and tried that but the same problem. After scritching my head for a bit I ended up trying to start X from Terminal by just typing X. Lo’ and behold it worked! But I just got an X server without much that was
interesting. So then I tried starting xterm from the Finder (Show in Finder
on the X program brought up /usr/X11R6/bin).
Then the familiar little X11 icon popped up again and this one I ended
up keeping in my Dock and NOW things are working. Not sure what exactly that did to fix it but it ended up fixing it.

Here’s the beginning of the message I got from the Console:

Unrecognized option: –xquartz-be-xinit
use: X [:] [option]
-a # mouse acceleration (pixels)
-ac disable access control restrictions
-audit int set audit trail level
-auth file select authorization file
bc enable bug compatibility
-br create root window with black background
+bs enable any backing store support
-bs disable any backing store support
-c turns off key-click
c # key-click volume (0-100)
-cc int default color visual class
-co file color database file
-core generate core dump on fatal error
-dpi int screen resolution in dots per inch
dpms enables VESA DPMS monitor control
-dpms disables VESA DPMS monitor control

Be Sociable, Share!

{ 2 } Comments

  1. Tom Arons | October 28, 2003 at 8:41 pm | Permalink

    This is because an archive/install didn’t remove the old in /Applications which was pointed to by your icon. The newest is in /Applications/Utilities. See #85 at for details. This was driving me batty all afternoon.

  2. Alain Hoang | October 28, 2003 at 10:16 pm | Permalink

    Thanks for the pointer and the explanation. That makes perfect sense. Luckily it only confused me for about an hour and not the afternoon. But I didn’t bother figuring out the root cause except that it must be some effect of having the X11 beta already installed on a Jaguar machine before Archive & Install