Python

idle with subprocess on multiseat

Bug #338379 reported by Markus Schlager on 2009-03-05

Affects		Status	Importance	Assigned to	Milestone
	Python	Fix Committed	Unknown	python-roundup #1529142
	python-defaults (Ubuntu)	Fix Released	Low	Unassigned

Bug Description

Binary package hint: idle

ubuntu dapper,hardy

package: idle

Running with subprocess (default) idle tries to bind to TCP/IP-Port 8833. This prevents running more than one idle-instances on a single computer at the same time. On a multiseat-system with e.g. four simultaneous X-sessions only one user can use idle without the -n-Option.

Is it possible to make idle check the next free port, if 8833 (and 8334 etc.) ist blocked?

Tags:

Revision history for this message

Matthias Klose (doko) wrote on 2009-03-18:

> Is it possible to make idle check the next free port, if 8833 (and 8334 etc.) ist blocked?

not checked, would you provide a patch?

Changed in python-defaults (Ubuntu):
importance:	Undecided → Low
status:	New → Triaged

Revision history for this message

Markus Schlager (m-slg) wrote on 2009-03-18: Re: [Bug 338379] Re: idle with subprocess on multiseat

>
> not checked, would you provide a patch?
>

Sorry, I'm not a developer, only teaching python to pupils.

Richard Hansen (rhansen) on 2009-06-29

tags:

added: multiseat

Revision history for this message

gpolo (ggpolo) wrote on 2009-08-07:

ephemeral_port.diff Edit (4.7 KiB, text/x-diff)

I'm not really involved on how things work around here but I guess I could attach the patch that was applied on idlelib to fix this issue. The patch removes the use of a fixed port number and instead lets the tcp/ip stack choose an ephemeral ort.

Revision history for this message

DustinErnst (dustinernst) wrote on 2012-09-07:

Upstream fixed this years ago.