Bug 29724 - screen dies after unlocking
Summary: screen dies after unlocking
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: screen
Version: 9
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Lon Hohberger
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-02-27 10:03 UTC by David Balažic
Modified: 2007-04-18 16:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-04-16 14:04:44 UTC
Embargoed:


Attachments (Terms of Use)

Description David Balažic 2001-02-27 10:03:25 UTC
screen-3.9.8-2

Steps to reproduce :

1. run screen as root on VT1
2. open some virtual screens
3. lock screen ( ctrl-a ctrl-x )
4. wait a few minutes
5. unlock it by entering the password
6. boom, screen exits and the terminal is hosed
   The virtual terminals are still alive and can be reattached
   VT1 does not echo any user input, not even "ENTER", but it responds
   to it, and output seem to be unaffected. Sanity is restored
   by "stty sane"

Comment 1 David Balažic 2001-03-05 12:08:32 UTC
Same with screen-3.9.8-3 ( in Wolverine )

Comment 2 David Balažic 2001-03-22 14:16:38 UTC
It happened also when I ulocked right after locking,
so it might not be time related.
I noticed in the source that the password is read by getpass(3),
which is obsolete, according to man page.
getpass() disables echo which is one of the simptoms, so maybe
this is getpass() crashing.

Comment 3 David Balažic 2001-04-26 08:26:11 UTC
The bug is still there in Seawolf , screen-3.9.8-3


Comment 4 Crutcher Dunnavant 2001-06-26 22:12:36 UTC
works for me with 3.9.9

Comment 5 David Balažic 2001-07-26 10:28:46 UTC
I experince the bug with screen-3.9.9-1 on a RH 7.1 system.
Notice that it doesn't happen always , but most of the time !

Comment 6 David Balažic 2002-04-10 15:15:54 UTC
I experienced the same problem with screen-3.9.10-1 in 
redhat 7.2.93 ( skipjack2 ).

Comment 7 Lon Hohberger 2002-11-07 21:28:33 UTC
Is this still a problem on 7.3 or 8.0?  

I haven't been able to reproduce it on 8.0.  If it's present on 7.3/8.0, I'll
look more into it.  Otherwise, I'll assmume it's good, otherwise I'd like to
close it.

Comment 8 Lon Hohberger 2002-12-16 21:33:40 UTC
Any activity here?  Could this be related to the UTF-8 problems seen in versions
prior to 3.9.13?

ftp://ftp.redhat.com/pub/redhat/linux/rawhide/RedHat/RPMS/screen-3.9.13-2.i386.rpm

Comment 9 Lon Hohberger 2003-04-16 14:04:44 UTC
I believe this was fixed with 3.9.11's UTF8 fixes.  Here's a pointer to the
latest packaged screen, which has more UTF8 bugfixes as well:

http://people.redhat.com/lhh/screen-3.9.15-1.i386.rpm
http://people.redhat.com/lhh/screen-3.9.15-1.src.rpm

The above packages should be available in rawhide soon.

Reopen bug if it is still present - I've been unable to reproduce it.


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