Bug 131214 - Cannot spawn any more xterms
Summary: Cannot spawn any more xterms
Status: CLOSED DUPLICATE of bug 128154
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2004-08-30 03:36 UTC by George Toft
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2006-02-21 19:05:21 UTC

Attachments (Terms of Use)

Description George Toft 2004-08-30 03:36:52 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; X11; Linux i686) Opera 
7.51  [en]

Description of problem:
See bug 128154

Similarity is that I have several xterms open.  I followed advice in 
above bug, including killing off process holding pty/0.  I have not 
upgraded the kernel as this is the FC3T1 distro.

Main difference is that killing off the process that is holding pty/0 
allows me to spawn only 1 more xterm - no net gain.

Other differences - the time before this condition appears ranges 
from an hour to a week, not the 24 hours or so mentioned in the above 
bug.  As this system is being tuned and adjusted, it gets rebooted, 
so it has not been up more than a week - actual time to failure may 
be longer.

Reboot circumvents the problem.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.  Spawn an xterm
2.  When conditions are right, CPU load climbs, then drops off.  No 
xterm appears.


Actual Results:  No xterm appears

Expected Results:  xterm should appear

Additional info:

Comment 1 Warren Togami 2004-08-30 05:01:21 UTC
I'm pretty sure this is a duplicate of 128154, which seems to be fixed
with the latest rawhide kernels.  If you don't want to upgrade to
rawhide, see if it works properly in FC3 test2.

*** This bug has been marked as a duplicate of 128154 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:05:21 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.