Bug 56688 - Emacs leaves console in bad state after exit (not under X)
Emacs leaves console in bad state after exit (not under X)
Product: Red Hat Linux
Classification: Retired
Component: emacs (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
Aaron Brown
Depends On:
  Show dependency treegraph
Reported: 2001-11-24 19:06 EST by Leigh L. Klotz, Jr.
Modified: 2007-04-18 12:38 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-11-24 19:06:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Leigh L. Klotz, Jr. 2001-11-24 19:06:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:0.9.6) Gecko/20011120

Description of problem:
This is related to the NOTABUG 55386 but since I'm not that bug's owner I
couldn't re-open it.  I have included steps to reproduce the bug here.

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

How reproducible:

Steps to Reproduce:
1. Install RedHat Linux 7.2 with current updates, including emacs and
emacs-nox.  Set defualt runlevel to 3 -- do not start X.
2. Log in to console.  Do not start X.
3. Type "emacs".
4. Type "control-x control-c"
5. Note that the terminal now no longer echoes.  
6. Type "reset" at the shell to fix things.
7. Start "emacs" again.
8. Suspened emacs by typing "control-x control-z"
9. Observe that the shell is fine now.

Actual Results:  Shell doesn't echo and requires 'reset'

Expected Results:  Shell does echo and does not require 'reset'

Additional info:

I have seen this bug on three different systems.  "->" indicates an
upgrade, all with installations upgraded to current patch levels.

#1 7.0->7.1->7.2 Pentium II 450
#2 7.0->7.1->7.2 K6-II 450
#3 6.2->7.0->7.1->7.2 Pentium II 200
Comment 1 Trond Eivind Glomsrxd 2001-11-26 11:44:51 EST
I can't reproduce this on a vanilla+updates RHL 7.2 system with this procedure.
I don't experience any problems at all...

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