10 thoughts on “Fix xterm launch from Terminal.app in Mac OS X 10.5 (display error solved!)

    Nelman Senarathne said:
    2009.05.19 at 15:41

    Mac x11 terminal dosen’t start.? when i click it suddenly come and gone. (like a flash)

    this error msg. came tru terminal

    Last login: Sun May 17 04:56:41 on ttys000
    dyld: lazy symbol binding failed: Symbol not found: _tgetent
    Referenced from: /bin/bash
    Expected in: flat namespace

    dyld: Symbol not found: _tgetent
    Referenced from: /bin/bash
    Expected in: flat namespace

    [Process completed]

    what is this. please help.
    I have mac book pro (os x 10.5.7 Leapord)

      Mr. Drive responded:
      2009.05.19 at 16:08

      Did this start to happen after you followed the above procedure?

    Nelman Senarathne said:
    2009.05.19 at 17:01

    no. i installed bash. after that this msg. came. is it a big error. the only prob. is terminal starting. text wrangle, gimp, inkspace working well. thanks

    Mr. Drive responded:
    2009.05.19 at 23:42

    Take a look at your ~/.bash_login or ~/.bash_profile with a text editor, maybe you can find some lines that are related to the problem. If you do find something related, comment those lines. Then try to launch your X11 again and see what happens…

    RUKnight said:
    2009.10.15 at 15:48

    ok. so i’m new to mac and i have no idea what your talking about. for step 2: doing that stuff in terminal just gives me a blank screen. i have macos x snow leopard.

    Mr. Drive responded:
    2009.11.20 at 10:12

    @RUKnight: hey after which part of step 2 you get the blank screen? is it a Terminal Blank Screen? or is it an X11 blank screen?

    i-blis said:
    2010.02.08 at 18:01

    Nice tip.

    If you use zsh, you probably just have a .zshrc file to check. Comment out the line which sets DISPLAY. Open a new shell (no need to restart Terminal) and your done : you can launch X11 apps from Terminal.

    Thanks man.

    BJH said:
    2012.07.12 at 20:07

    Thanks for the gr8 instructions. They saved my ass after a new application changed the env parameters. Much appreciated!!

    Sashmo said:
    2012.12.05 at 18:16

    FYI, I removed JUST the display varibable from my bash_profile and everything worked again, when I did echo $DISPLAY I got a /tmp/launch-V38NC7/org.macosforge.xquartz:0

    This seemed to fix it, all is fine again.

    Thanks for the help

    serenthia said:
    2013.05.07 at 12:01

    Hmm, .profile and .bash_login didn’t exist, and .bash_profile only contained:

    [[ -s “$HOME/.rvm/scripts/rvm” ]] && source “$HOME/.rvm/scripts/rvm” # Load RVM into a shell session *as a function*

    Therefore, the changes above didn’t actually make any changes to the value of $DISPLAY. Any ideas?

    Thanks so much.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s