[Idle-dev] [ idlefork-Bugs-747772 ] RedHat Linux 8.0 problems

[SourceForge.net]

Bugs item #747772, was opened at 2003-06-02 17:41
Message generated for change (Comment added) made by gvanrossum
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109579&aid=747772&group_id=9579

Category: None
Group: None
Status: Open
Resolution: Works For Me
Priority: 5
Submitted By: Bruce Sherwood (bsherwood)
Assigned to: Nobody/Anonymous (nobody)
Summary: RedHat Linux 8.0 problems

Initial Comment:
When installing the latest CVS on RedHat Linux 8.0,
setup failed because it was looking for CREDITS.txt,
HISTORY.txt, INSTALL.txt, LICENSE.txt, NEWS.txt, and
README.txt, all of which were present but with
lower-case file names (which didn't matter on Windows).

The Help for Idle displays "\r" at the end of each line.

I always get the "cannot open socket" message,
sometimes when trying to start Idle, but sometimes not
until I press F5 to run. I don't have this problem with
the old original idlefork.

I had a nonreproducible problem with keyboard shortcuts
such as Ctrl-C for copy. For a while they worked only
for items on the Format menu. Now they all work.
Thought I should at least report it.

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

>Comment By: Guido van Rossum (gvanrossum)
Date: 2003-06-03 13:24

Message:
Logged In: YES 
user_id=6380

Looks to me like maybe Bruce got the files on Windows and
transferred them to Linux from there (or maybe shared them
using VMWARE or SAMBA).


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

Comment By: Kurt B. Kaiser (kbk)
Date: 2003-06-03 13:14

Message:
Logged In: YES 
user_id=149084

First, the CVS issues: If you have lower case .txt
files (except for help.txt) there is something wrong
with your cvs client or other setup.  The repository
is correct.  Also, the line endings for help.txt in the
repository are 0x0a (\n) with no \r involved.  So
again, it sounds like a cvs client problem.

The socket problem: Since you are struggling a bit
you may have moribund IDLEfork processes.  Do a
ps fx  and kill any you see, then try again.  Once the
first instance of IDLEfork is started I would like all
subsequent attempts to fail cleanly, but that is still
not completely robust.  Once it is, we can move on 
to Michael William's request to run multiple copies
of IDLEfork simultaneously.  (To give you an idea of
how flakey this is, /once/ on WinXP I had two copies
running with one printing a string of 1's and
the other a string of 2's.  But it's not supposed to be
possible to have two processes setting up connections
on the same socket.  And I can't reproduce it.)

When this kind of thing happens to me it's usually
because I created a bug that caused IDLE to fail while
initializing, and the stuck process prevents the next
instance from initializing.  ps fx and kill are your friends.

I haven't seen anything like the last problem.  It's 
likely related to incomplete initialization of IDLE on
startup.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109579&aid=747772&group_id=9579