Bug 132398 - No xterm after some time
Summary: No xterm after some time
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-09-12 12:55 UTC by Nicola
Modified: 2015-01-04 22:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-04-16 04:48:22 UTC


Attachments (Terms of Use)

Description Nicola 2004-09-12 12:55:03 UTC
Description of problem:
After two days uptime, I cannot open xterms anymore:
$ xterm
xterm: Error 32, errno 2: No such file or directory
Reason: get_pty: not enough ptys


Version-Release number of selected component (if applicable):
uname -a
Linux uno.theory.org 2.6.7-1.494.2.2 #1 Tue Aug 3 09:19:06 EDT 2004
x86_64 x86_64 x86_64 GNU/Linux

rpm -q xterm
xterm-179-6.EL


How reproducible:
Waiting for  while?

Steps to Reproduce:
1. Wait for long enough
2. Open an xterm
3.
  
Actual results:
Cannot open new xterm, even when killing old one.

Expected results:
Open xterm

Additional info:

Happened only after 2 days+ uptime. Cannot try latest 2.6.8 kernel
because of other severe cd burning bugs.

Comment 1 Warren Togami 2004-09-12 19:54:44 UTC
Most likely this is a duplicate of Bug #128154 which is solved by
newer kernels.  Please install the latest FC2 kernel (521) or latest
rawhide kernel, both of which should solve this problem.  Please
report back.

Comment 2 Dave Jones 2005-04-16 04:48:22 UTC
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat.  The Fedora legacy project will be producing further kernel
updates for security problems only.

If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.

Thank you.



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