http://bugzilla.suse.com/show_bug.cgi?id=1143055 Alynx Zhou changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alynx.zhou@suse.com Assignee|bnc-team-screening@forge.pr |mls@suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1143055 http://bugzilla.suse.com/show_bug.cgi?id=1143055#c2 Till Dörges changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(doerges@pre-sense | |.de) | --- Comment #2 from Till Dörges --- (In reply to Michael Schröder from comment #1)

So does screen interpret home/end correctly? I.e. if you enter 'scrollback' mode (C-a ESC), does the cursor move to the start/end of the window if you press the keys?

Indeed that works. After hitting C-a ESC, HOME brings me to the top of the buffer and END to the end.

Or do the applications started insider of screen don't work correctly? In that case, do they work if you use TERM='screen' instead of that screen.xterm-256color entry?

The application then would be bash. export TERM=screen doesn't change the behavior of HOME/END. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1143055 http://bugzilla.suse.com/show_bug.cgi?id=1143055#c4 --- Comment #4 from Michael Schröder --- I'm not sure that bash will pick up the new $TERM with your export command. try: export TERM=screen exec bash Please do not set TERM to screen before starting screen, it'll just mess up screen's key translation. I suspect all this is because the 'screen-xterm-256color' entry is very broken. Which package does it belong to? I.e. what's the output of: rpm -qf /usr/share/terminfo/s/screen-xterm-256color -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1143055 http://bugzilla.suse.com/show_bug.cgi?id=1143055#c6 --- Comment #6 from Till Dörges --- (In reply to Michael Schröder from comment #5)

Here's something else to test: does everything work if you start screen with the '-a' option (which forces it to set $TERM to screen instead of screen.XXX)?

Both your workarounds resolve the problem (HOME and END working as expected in bash) - screen -a - inside screen: export TERM=screen exec bash In both cases TERM is set to "screen". As for the terminfo files I have --- snip --- user@box:~> rpm -qf /usr/share/terminfo/s/screen-xterm-256color error: file /usr/share/terminfo/s/screen-xterm-256color: Datei oder Verzeichnis nicht gefunden user@box:~> ll /usr/share/terminfo/s/screen-*256* -rw-r--r-- 1 root root 1988 27. Apr 21:42 /usr/share/terminfo/s/screen-256color -rw-r--r-- 1 root root 2000 27. Apr 21:42 /usr/share/terminfo/s/screen-256color-bce -rw-r--r-- 1 root root 2032 27. Apr 21:42 /usr/share/terminfo/s/screen-256color-bce-s -rw-r--r-- 1 root root 2018 27. Apr 21:42 /usr/share/terminfo/s/screen-256color-s user@box:~> ll /usr/share/terminfo/s/screen-*xterm* -rw-r--r-- 1 root root 3481 27. Apr 21:42 /usr/share/terminfo/s/screen-bce.xterm-new user@box:~> rpm -qf /usr/share/terminfo/s/screen-*256* /usr/share/terminfo/s/screen-*xterm* terminfo-base-6.1-lp151.5.41.x86_64 terminfo-6.1-lp151.5.41.x86_64 terminfo-6.1-lp151.5.41.x86_64 terminfo-6.1-lp151.5.41.x86_64 terminfo-6.1-lp151.5.41.x86_64 user@box:~> rpm -qf /usr/share/terminfo/x/xterm-256color terminfo-base-6.1-lp151.5.41.x86_64 user@box:~> rpm -ql screen | grep termin user@box:~> --- snap --- -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1143055 http://bugzilla.suse.com/show_bug.cgi?id=1143055#c16 --- Comment #16 from Dr. Werner Fink --- For Factory its SR#723956 For SLES-15/SLES-15-SP1/Leap15/LEap15.1 SR#173129 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1143055 http://bugzilla.suse.com/show_bug.cgi?id=1143055#c18 --- Comment #18 from Michael Schröder --- [back from vacation] It's actually not a new feature, it has been in screen since pretty much the very beginning, i.e. 199X. The intention was to allow the same flexibility as which termcap, where screen would use the $TERMCAP variable to specify a "tweaked" set of capabilities. Nobody used it, so there never was a problem. Now somebody decided it would be good to have some screen.$TERM terminal entries, and we have this mess. It's really a misfeature. Having "screen-256color" is fine, but screen.$TERM makes no sense as $TERM may be something different when reattaching. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1143055 http://bugzilla.suse.com/show_bug.cgi?id=1143055#c21 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maint-coord@suse.de Flags| |needinfo?(maint-coord@suse. | |de) --- Comment #21 from Dr. Werner Fink --- Add maintenance coordination -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1143055 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |ibs:running:12495:moderate -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1143055 http://bugzilla.suse.com/show_bug.cgi?id=1143055#c27 --- Comment #27 from Thomas Dickey --- That's an odd response, since the various terminals actually are different (unless you limit your viewpoint to the subset seen in termcap). In any case, Werner's comments pointed to a problem in libreadline, which should be addressed. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1143055 http://bugzilla.suse.com/show_bug.cgi?id=1143055#c29 --- Comment #29 from Thomas Dickey --- hmm - I missed a detail from Werner's comment #24: while providing some wildcard (or regex) match will "work", it would not for example address the differences between the old/new mapping (referring to xterm-imitators) of shifted F1-F4. For that, libreadline would have to take into account the actual terminal description rather than guessing based on its name. zsh has (incompletely) addressed this as mentioned here https://invisible-island.net/xterm/manpage/xterm.html#h3-Special-Keys but an actual solution for bash/readline is left as an exercise for bash's developer(s). I provided the variations in ncurses because otherwise the user has to resort to hardcoded stuff to get a usable terminal. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1143055 http://bugzilla.suse.com/show_bug.cgi?id=1143055#c31 --- Comment #31 from Thomas Dickey --- yes, I understood that. Matching just on the value of TERM isn't what I would recommend, but given that screen interprets "screen.XXX" as "XXX" (the "." is special too), then something like $if term=screen || term=screen.* (wildcards) is what I assume you suggested as a change. Or perhaps $if term=screen* depending on what libreadline's parser can do. There's no way to ask terminfo/termcap directly if the different terminal descriptions are actually related (the "use=" clause isn't in the compiled terminal description), but then again, bash's users don't appear to care if the terminal description's function-keys actually work because they're hard-coded on a per-user basis. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1143055 http://bugzilla.suse.com/show_bug.cgi?id=1143055#c32 --- Comment #32 from Swamp Workflow Management --- SUSE-RU-2019:2418-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1133773,1143055 CVE References: Sources used: SUSE Linux Enterprise Module for Open Buildservice Development Tools 15-SP1 (src): bash-4.4-9.10.1 SUSE Linux Enterprise Module for Open Buildservice Development Tools 15 (src): bash-4.4-9.10.1 SUSE Linux Enterprise Module for Basesystem 15-SP1 (src): bash-4.4-9.10.1 SUSE Linux Enterprise Module for Basesystem 15 (src): bash-4.4-9.10.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1143055 http://bugzilla.suse.com/show_bug.cgi?id=1143055#c33 --- Comment #33 from Swamp Workflow Management --- openSUSE-RU-2019:2193-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1133773,1143055 CVE References: Sources used: openSUSE Leap 15.1 (src): bash-4.4-lp151.10.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1143055 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:11094:moderate | |obs:running:11092:moderate | -- You are receiving this mail because: You are on the CC list for the bug.