[Python-bugs-list] [ python-Bugs-474913 ] 2.2b1 won't start in remote shell

noreply@sourceforge.net noreply@sourceforge.net
Thu, 25 Oct 2001 08:48:56 -0700


Bugs item #474913, was opened at 2001-10-25 08:48
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=474913&group_id=5470

Category: Macintosh
Group: Python 2.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Jack Jansen (jackjansen)
Summary: 2.2b1 won't start in remote shell

Initial Comment:
Seems possibly related to #466907

This does not seem to occur with 2.2a4, but does 
with 2.2b1.

I tried this on three different Macs, each/all OS X 
10.1 (relatively clean installs) with the 10-19-2001 
security (and MS IE) patch. All are G4 machines w/ 
lots of memory.

2.2b1seems to build (configure --with-suffix=.exe), 
install, and run just fine on all machines when 
working from a local terminal window. However I 
see strange behavior when trying to run remotely.

1. If I connect to one of the machines remotely 
using ssh (e.g. ssh to my dual G4, which is faster 
than my home machine) and try and start python, I 
see the following errors:

	[mac-welch:~/proj/python] welch% python
	kCGErrorIllegalArgument : CGSNewConnection 
cannot get connection port
	kCGErrorIllegalArgument : CGSNewConnection 
cannot get connection port
	kCGErrorInvalidConnection : CGSGetEventPort: 
Invalid connection
	[mac-welch:~/proj/python] welch%

2. If I su to root in the same remote session, 
python starts just fine!

If I revert to 2.2a4 it seems to work fine.

Thanks (in advance) folks.


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=474913&group_id=5470