Menu

4.30 unworkable, even under best case

Help
2003-08-18
2003-08-18
  • Carlton Hogan

    Carlton Hogan - 2003-08-18

    I cannot get v4.30 to work on any of my Macs. I
    assumed that this was my fault, and I had a bad config,
    or a screwed up lib-link. But then I got a computer back
    from service. I don't know what they did, but they screwed
    the OS up so bad, I had to do a totally clean install. So
    I did this:

    1)Install OS 10.2
    2) Ran "Software Update" to bring me to the present
    3) Installed the developer tools (December version,
    not the new one with the problematic gcc)
    4) Installed XonX

    ....And I got the exact behaviour as on all my other
    machines: a launch, a grey screen with big "X" cursor,
    and then immediate exit.

    To be sure, I deleted (or rather .tgz'ed and moved)
    my .xininitrc, my Xdefaults, all the configs in /etc/X11
    - as far as XonX installer could tell, thei was a first-time
    install.

    I Have tried various .xinitrc tricks, specifying other
    windowmanagers (ones that compiled clean, with
    no errors) etc. Same thing. Launch. Crash.

    I frankly am amazed: the quality of work on the XonX
    project has been so good, all the way back to the
    "darwinfo" days. But 4.3 seems to just be a lemon.
    I have tried everything I can think of - any ideas?

    Carlton Hogan
    carlton@ccbr.umn.edu

     
    • Torrey T. Lyons

      Torrey T. Lyons - 2003-08-18

      Full screen has a known bug in full screen mode that causes it to crash in certain screen resolutions. This has been fixed in the current source code, but a new binary file has not been made available yet. (We may sneak in one other more subtle bug fix first.) In the meantime you can run in rootless mode to avoid this problem or build from the xf-4_3-branch yourself if you need full screen. (BTW, if you can't find the option to start in rootless mode, the easiest thing to do is quit XDarwin and then remove the ~/Library/Preferences/org.xfree86.XDarwin.plist file.)

       

Log in to post a comment.