#214 XDarwin crash under 10.2.1

Causes Crash
closed-works-for-me
Rootless (76)
5
2002-10-22
2002-10-21
Anonymous
No

Hi,

When I try to launch XDarwin by double clicking on it icon
under Mac OS X 10.2.1, it crashes. The Console reports this :

Display mode: Rootless Quartz
Screen 0 added: 1152x849 @ (0,21)
Screen 0 placed at X11 coordinate (0,0).
/Users/boudon/.xinitrc: exec: startkde: not found
Using keymapping provided in
/System/Library/Keyboards/Francais.keymapping.
Display mode: Rootless Quartz
Screen 0 added: 1152x849 @ (0,21)
Screen 0 placed at X11 coordinate (0,0).

waiting for X server to shut down ......Oct 21 10:39:51 japet
crashdump: Crash report written to:
/Users/boudon/Library/Logs/CrashReporter/XDarwin.crash.lo
g

So there seem to be a path problem. When I launch it
manually by typing startx in the terminal, it works. Orobor OS
X works too. Not XDarwin. I've made all the updates and my
.tcshrc contains "source /sw/bin/init.csh".

So what's the problem ?

Thank you in advance.

Vincent Boudon

Discussion

  • Torrey T. Lyons

    Torrey T. Lyons - 2002-10-21

    Logged In: YES
    user_id=133579

    Yes, this is a path problem. OroborOSX automatically runs /sw/bin/init.csh so it does not rely on you setting things up properly. For some reason your .tcshrc is either broken or not being run by XDarwin. What do you have your shell set to in the XDarwin startup preferences?

     
  • Torrey T. Lyons

    Torrey T. Lyons - 2002-10-21

    Logged In: YES
    user_id=133579

    Note if you are using:

    source /usr/share/tcsh/examples/rc

    in your .tcshrc, then nothing after this will be executed. The examples are unfortunately broken in Jaguar as you can see if you start XDarwin without a .xinitrc file. The problem is that /usr/share/tcsh/examples/rc always expects TERM_PROGRAM to be set, but this special variable is only set in the Terminal application. Thus the rc script will bomb out anywhere except in the Terminal. You can download a fixed version of this script from Apple's Darwin CVS site. You can also modify rc yourself to put in a check for TERM_PROGRAM before testing its value.

     
  • Nobody/Anonymous

    Logged In: NO

    Hi Torrey,

    Yes, your right, I'm using /usr/share/tcsh/examples/rc. And I noticed
    this TERM_PROGRAM problem when I do a su -, for instance. So
    how do I "download a fixed version of this script from Apple's
    Darwin CVS site" ? I'm not used with this ...

    Thank you in advance.

    Vincent Boudon.

     
  • Nobody/Anonymous

    Logged In: NO

    OK, I've found the solution here :

    http://www.macosxhints.com/article.php?story=200208280906199
    56

    In short, there is a typo in /usr/share/tcsh/examples/aliases

    One should change the line that says:

    if ("$TERM_PROGRAM" == "Apple_Terminal") then

    to:

    if ("$?TERM_PROGRAM" == "Apple_Terminal") then

    and it works !

    Vincent Boudon.

     
  • Torrey T. Lyons

    Torrey T. Lyons - 2002-10-22

    Logged In: YES
    user_id=133579

    The macosxhints.com solution is almost right, but breaks one thing to fix another. The problem is that:

    if ("$?TERM_PROGRAM" == "Apple_Terminal")

    will never be true. "$?TERM_PROGRAM" evaluates to either 1 or 0, which obviously does not equal "Apple_Terminal". So while the script won't crash, it also does not work as intended if you do happen to be running in Apple's Terminal application. The correct fix is:

    if ($?TERM_PROGRAM) then
    if ("$TERM_PROGRAM" == "Apple_Terminal") then
    alias settermtitle 'echo -n "]2;\!:1"'
    endif
    endif

    In any case, we can close this XDarwin bug.

     
  • Torrey T. Lyons

    Torrey T. Lyons - 2002-10-22
    • assigned_to: nobody --> torrey
    • status: open --> closed-works-for-me
     

Log in to post a comment.