Bug 18390 - screen -r sometimes fails
screen -r sometimes fails
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: screen (Show other bugs)
7.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Lon Hohberger
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-10-05 05:42 EDT by Tim Waugh
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-11-08 05:27:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tim Waugh 2000-10-05 05:42:14 EDT
Sometimes (sorry to be so vague) 'screen -r' will clear the terminal and
exit, leaving the tty raw.  'stty sane' and then 'screen -r' almost
invariably works, after that.  I haven't managed to reproduce it at will;
it just happens every so often.
Comment 1 Crutcher Dunnavant 2001-06-26 16:57:57 EDT
well, this helps.
reopen if this doesnt stop with 3.9.9
Comment 2 Tim Waugh 2001-06-27 10:40:44 EDT
Just happened again, with screen-3.9.9-1.
Comment 3 Tom Tromey 2001-12-12 14:14:13 EST
I've seen this same problem with screen-3.9.9-3 on the alpha.
In my case, if I log out (I'm running screen on a remote box
I access via ssh) and then back in, it starts working.
(Do reports like this ever get reported back to the upstream maintainer?)
Comment 4 Phil Copeland 2002-08-12 15:20:28 EDT
heck, they rarely even get as far as the person the bug was xfered over to
without being notified! (I just came across this bugreport today)

Can you try out with 3.9.11-8 in rawhide for a while and let me know if it still
bails out horribly? I've never encountered this behaviour before in screen, and
I use it a LOT.

Thanks

Phil
=--=
Comment 5 Tim Waugh 2002-11-08 05:27:06 EST
I haven't seen this in ages and ages.
Comment 6 Lon Hohberger 2002-11-11 12:04:39 EST
Assuming fixed upstream and fixes are in current release.  Reopen if appears again.

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