Description of problem: When detaching from a screen session, the terminal is not cleared and restored to the state it was prior to invoking screen. Version-Release number of selected component (if applicable): screen-4.0.3-15.fc12.x86_64 How reproducible: text from ncurses-based apps stays on the screen if you are within an ncurses app when you detach. Steps to Reproduce: 1. invoke screen 2. open an ncurses-based app (i.e. mutt, ncmpc, etc.) 3. detach Actual results: text from the ncurses app stays on the terminal after detaching/exiting. Expected results: terminal should return to its previous state. Additional info: This is new to Fedora 12, I am not experiencing this on my Fedora 11 box.
I've narrowed down the issue to the screenrc patch. Commenting that out in the spec file and rebuilding gets rid of the issue. Maybe this is being caused by some of the termcap/terminfo lines? Unfortunately I don't have any understanding of termcap/terminfo syntax.
I'd like to add that there was a secondary problem that was also (apparently) resolved by not using the screenrc patch: When starting mutt from a window within a screen session, the cursor keys would completely stop working within screen. Some further troubleshooting led to the realization that screen was sending the Application Mode command sequence (for instance, \033OA instead of \033[A for the up cursor). I would have to detach and run "echo -e '\033>'" to toggle Application Mode back to off and regain the use of my cursor keys. Since rebuilding without the screenrc patch, this problem also appears to be gone.
Nevermind, the Application Mode issue still exists. I will open a separate bug report for it. (In reply to comment #2) > I'd like to add that there was a secondary problem that was also (apparently) > resolved by not using the screenrc patch: > > When starting mutt from a window within a screen session, the cursor keys would > completely stop working within screen. Some further troubleshooting led to the > realization that screen was sending the Application Mode command sequence (for > instance, \033OA instead of \033[A for the up cursor). I would have to detach > and run "echo -e '\033>'" to toggle Application Mode back to off and regain the > use of my cursor keys. > > Since rebuilding without the screenrc patch, this problem also appears to be > gone.
I don't see this in xterm or urxvt. Which terminal emulator are you using? Can you try to narrow down exactly which line from the patch causes this?
This is in xterm-color. I'll try to look at it later tonight.
I am seeing this in gnome-terminal-2.30.1.1fc13, with screen-4.0.3.15.fc12. I've found that setting TERM to 'linux' results in correct behavior but with TERM set to 'xterm', the problem is very annoyingly present.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.