Bug 57124 - controlling tty randomly disappears after upgrading to util-linux-2.11f-11.7.1.i386.rpm
Summary: controlling tty randomly disappears after upgrading to util-linux-2.11f-11.7....
Status: CLOSED DUPLICATE of bug 54741
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: util-linux (Show other bugs)
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Elliot Lee
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2001-12-05 12:38 UTC by Andreas Beck
Modified: 2007-04-18 16:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-12-05 12:38:10 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Andreas Beck 2001-12-05 12:38:06 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [de] (X11; U; Linux 2.4.9-12custom i686)

Description of problem:
Since upgrading my RH 7.1 system to util-linux-2.11f-11.7.1.i386.rpm, I
often (not always) loose the controlling tty when logging in on a console.
This annoys programs like su,ssh and xggi that need a controlling tty for
various reasons. You have the problem, if you get
[becka@cupido becka]$ cat </dev/tty
bash: /dev/tty: No such device or address
right after logging in. The problem dis-/reappears in a random fashion with
each new login. Going back to /bin/login from
util-linux-2.10s-13.7.i386.rpm (only the login binary was fetched form
there) fixes it. Seemingly the fix for Bug 51646 has an unwanted side
effect. Note, that I am using fbdev with the matrox driver. Kernel version
has no influence (tried with 2.4.2 and 2.4.9 from source RPM).

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

How reproducible:

Steps to Reproduce:
1. Log in on a VT on a machine running the abovementioned configuration.
2. enter cat </dev/tty

Actual Results:  bash: /dev/tty: No such device or address

Expected Results:  The cat should have echoed typed characters. Break with

Additional info:

Comment 1 Elliot Lee 2001-12-05 15:54:19 UTC

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

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