Re: upgrade to Lion broke xterm? (Solved!)
Re: upgrade to Lion broke xterm? (Solved!)
- Subject: Re: upgrade to Lion broke xterm? (Solved!)
- From: "William \"Chops\" Westfield" <email@hidden>
- Date: Thu, 23 Feb 2012 18:16:29 -0800
> Check /Applications/Utilities/Console.app for messages? Also, try running it in Terminal and seeing if it outputs an error message.
>
> You might also want to check if the -ls / +ls option changes anything.
Nothing.
> Also, to see if it has to do with something going pear shaped with the initial shell, try "xterm -hold".
This, however, leaves the xterm window up with a "Couldn't copy terminal settings" message…
> I'm curious why it's exiting. If you are familiar with gdb, I'd recommend running xterm under gdb and breaking in _exit to see why it's bailing.
Breakpoint 1, 0x00007fff96a535c4 in _exit ()
(gdb) bt
#0 0x00007fff96a535c4 in _exit ()
#1 0x000000010001d87f in Exit ()
#2 0x000000010000bc4f in VTparse ()
#3 0x000000010000b4f8 in VTRun ()
#4 0x000000010001b94e in main ()
(gdb)
So I renamed away all my shell init files, seeing as this points in that direction. An xterm started from the old shell (started WITH the init files) still exits immediately. Soooo... binary search through the startup files...
Apparently, it does NOT like "export LANG=en_US" (a virgin shell has LANG=en_us.UTF8)
BillW-MacOSX-2:~ billw$ echo $LANG
en_US.UTF-8
BillW-MacOSX-2:~ billw$ xterm &
[1] 1119 (running successfully!)
BillW-MacOSX-2:~ billw$ export LANG=en_US
BillW-MacOSX-2:~ billw$ xterm &
[2] 1121
BillW-MacOSX-2:~ billw$
[2]+ Done xterm (exits early !)
Now, my init files are ancient, used to run on Solaris, and copied from someone else who understood them better than I do (probably several times removed.) But this is not one of the things I would have expected to be wrong in a way that caused this behavior… Oh well.
BillW
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden