Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
Re: upgrade to Lion broke xterm?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: upgrade to Lion broke xterm?



Weird.  I don't want to push you too far out of your comfort zone, but 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.

Upgrading from SL to Lion should've left you with a working XQuartz.app since the upgrade would not have touched it.

These xrdb lines are interesting:
>>> 2/23/12 2:27:42.687 PM org.macosforge.xquartz.startx: xrdb: colon missing on line 1, ignoring line

Do you have your own ~/.Xresources or ~/.Xdefaults

On Feb 23, 2012, at 2:35 PM, William Chops Westfield <email@hidden> wrote:

>
> On Feb 23, 2012, at 9:54 AM, Jeremy Huddleston wrote:
>
>> Do you have a crash log?
>
> I don't think so (that'd be a popup window, not a file stashed somewhere?)  It doesn't seem to crash; just exits immediately.
>
>
>> What is the exit code from xterm?  To find the exit code, check the $? variable
>
> 0
>
>
>> Also, does it print any text to the terminal when it fails like this?
>
> No, nothing.
>
>
>> Is there anything interesting in /var/log/system.log?
>
> No.  Nothing at all from X11/xterm.  There's a bit when X starts up (see below), but nothing at all when attempting to start the xterms.
>
>
>> Which xterm are you running?  Can you try using the full paths to /usr/X11/bin/xterm and /opt/X11/bin/xterm
>
> See below.  I think the /usr/X11/bin/xterm is from the Lion install, and /opt/X11/bin/xterm is from the XQuartz install?
>
>
>> Your sentence about 2.7.0 and 2.7.1 are confusing to me.  Are you experiencing the issue with both 2.7.0 and 2.7.1?  Lion only?
>
> I was running 2.7.0 under Snow Leopard.  After the lion upgrade, it didn't work, so I figured I'd install the latest (2.7.1), since you normally need to re-install xquartz after Apple upgrades.  Still didn't work.  Then I noticed just how new 2.7.1 was and re-installed 2.7.0 (after manually deleting xquartz.app due to the installer issue.  That should have been sufficient, right?)  It's still not working.  The examples were run with 2.7.1 re-installed.
>
> Log:
>>> BillW-MacOSX-2<9972> xterm
>>> BillW-MacOSX-2<9973> echo $?
>>> 0
>>> BillW-MacOSX-2<9974> which xterm
>>> /opt/X11/bin/xterm
>>> BillW-MacOSX-2<9975> /opt/X11/bin/xterm
>>> BillW-MacOSX-2<9976> echo $?
>>> 0
>>> BillW-MacOSX-2<9977> ls -l /opt/X11/bin/xterm
>>> -rwxr-xr-x  1 root  wheel  857892 Feb 19 21:54 /opt/X11/bin/xterm*
>>>
>>>
>>> BillW-MacOSX-2<9979> ls -l /usr/X11/bin/xterm
>>> -rwxr-xr-x  1 root  wheel  891936 Feb 22 15:00 /usr/X11/bin/xterm*
>>> BillW-MacOSX-2<9980> /usr/X11/bin/xterm
>>> BillW-MacOSX-2<9981> echo $?
>>> 0
>>>
>
> (and system.log)
>
>>> 2/23/12 2:27:40.400 PM [0x0-0x7d07d].org.macosforge.xquartz.X11: DISPLAY=/tmp/launch-slmSY8/org.macosforge.xquartz:0
>>> 2/23/12 2:27:40.412 PM [0x0-0x7d07d].org.macosforge.xquartz.X11: stty: stdin isn't a terminal
>>> 2/23/12 2:27:40.626 PM defaults:
>>> The domain/default pair of (/Users/billw/Library/Preferences/org.macosforge.xquartz.X11.plist, dpi) does not exist
>>> 2/23/12 2:27:40.640 PM org.macosforge.xquartz.startx: xauth:  file /Users/billw/.serverauth.2808 does not exist
>>> 2/23/12 2:27:42.681 PM org.macosforge.xquartz.startx: /opt/X11/bin/xinit: XFree86_VT property unexpectedly has 0 items instead of 1
>>> 2/23/12 2:27:42.687 PM org.macosforge.xquartz.startx: xrdb: colon missing on line 1, ignoring line
>>> 2/23/12 2:27:42.687 PM org.macosforge.xquartz.startx: xrdb: colon missing on line 3, ignoring line
>>> 2/23/12 2:27:42.687 PM org.macosforge.xquartz.startx: xrdb: colon missing on line 33, ignoring line
>>> 2/23/12 2:27:42.687 PM org.macosforge.xquartz.startx: xrdb: colon missing on line 35, ignoring line
>>> 2/23/12 2:27:42.687 PM org.macosforge.xquartz.startx: xrdb: colon missing on line 43, ignoring line
>>> 2/23/12 2:27:42.687 PM org.macosforge.xquartz.startx: xrdb: colon missing on line 44, ignoring line
>>> 2/23/12 2:27:42.687 PM org.macosforge.xquartz.startx: xrdb: colon missing on line 45, ignoring line
>>> 2/23/12 2:27:42.687 PM org.macosforge.xquartz.startx: xrdb: colon missing on line 51, ignoring line
>>> 2/23/12 2:27:42.687 PM org.macosforge.xquartz.startx: xrdb: colon missing on line 52, ignoring line
>>> 2/23/12 2:27:42.687 PM org.macosforge.xquartz.startx: xrdb: colon missing on line 53, ignoring line
>>> 2/23/12 2:27:42.687 PM org.macosforge.xquartz.startx: xrdb: colon missing on line 57, ignoring line
>>> 2/23/12 2:27:42.687 PM org.macosforge.xquartz.startx: xrdb: colon missing on line 58, ignoring line
>>> 2/23/12 2:27:42.687 PM org.macosforge.xquartz.startx: xrdb: colon missing on line 59, ignoring line
>


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list      (email@hidden)

This email sent to email@hidden


References: 
 >upgrade to Lion broke xterm? (From: "William \"Chops\" Westfield" <email@hidden>)
 >Re: upgrade to Lion broke xterm? (From: Jeremy Huddleston <email@hidden>)
 >Re: upgrade to Lion broke xterm? (From: "William \"Chops\" Westfield" <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2011 Apple Inc. All rights reserved.