http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c1 Ladislav Slezák <lslezak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |lslezak@suse.com Assignee|yast2-maintainers@suse.de |werner@suse.com Severity|Normal |Major --- Comment #1 from Ladislav Slezák <lslezak@suse.com> --- I found out that the problem is caused by updated terminfo-base package, when I copy the /usr/share/terminfo/x/xterm from openSUSE 42.2 then it works correctly. (I guess 42.3 or SLES12-SP3 should work as well.) The workaround is to run yast with TERM=linux (or something else, depending on the terminal used), in an SSH installation use "TERM=linux yast.ssh" command for starting the installer. Changing the component to Basesystem as the problem seems to in the /usr/share/terminfo/x/xterm file in terminfo-base package (ncurses source RPM). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c2 Ladislav Slezák <lslezak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ihno@suse.com --- Comment #2 from Ladislav Slezák <lslezak@suse.com> --- *** Bug 1054998 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c4 Ladislav Slezák <lslezak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jrauch@suse.com --- Comment #4 from Ladislav Slezák <lslezak@suse.com> --- *** Bug 1055281 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c6 Ladislav Slezák <lslezak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |okurz@suse.com --- Comment #6 from Ladislav Slezák <lslezak@suse.com> --- *** Bug 1054459 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c14 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #14 from Dr. Werner Fink <werner@suse.com> --- For all reporters: Does this bug happen in an XTerm ... no gnome-, no xfce4-, no konsole, no other then XTerm terminal? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c16 Martin Wilck <martin.wilck@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #16 from Martin Wilck <martin.wilck@suse.com> --- clearing needinfo -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c18 --- Comment #18 from Martin Liška <martin.liska@suse.com> --- I can confirm it happens for Xterm in Gnome after I've just updated my TW and rebooted. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c20 --- Comment #20 from Martin Liška <martin.liska@suse.com> --- (In reply to Dr. Werner Fink from comment #19)

Just build latest ncurses 6.0-20170909 from Base:System/ncurses from OBS and at least htop works perfect.

Please for every reporter check out

http://download.opensuse.org/repositories/Base:/System/openSUSE_Factory/ x86_64/libncurses6-6.0-416.2.x86_64.rpm http://download.opensuse.org/repositories/Base:/System/openSUSE_Factory/ x86_64/terminfo-base-6.0-416.2.x86_64.rpm

that is the libraries as well as the terminfo base. Afdter installing both packages please test out your use case within an real(!) XTerm

Just tested and I can verify all works (XTerm: htop, yast2, gdb) and all these also in gnome-terminal. Thanks, good job. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c22 --- Comment #22 from jean-christophe baptiste <jc@phocean.net> --- Fixed for me too. Thanks ! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c24 --- Comment #24 from Ladislav Slezák <lslezak@suse.com> --- *** Bug 1058246 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c26 Ladislav Slezák <lslezak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ldevulder@suse.com --- Comment #26 from Ladislav Slezák <lslezak@suse.com> --- *** Bug 1058660 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c28 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(okurz@suse.com) --- Comment #28 from Dr. Werner Fink <werner@suse.com> --- (In reply to Oliver Kurz from comment #27)

Have to reopen. The verification link I provided was about the installation which I originally reported in another bug which has been closed as a duplicate. The problem is fixed there but not when calling yast2 from within either xterm or gnome-terminal. Reproduced on SLES build 260.4. Confirmed working workaround by calling `TERM=xterm-color yast2`.

And which ncurses version does this SLES build 260.4 include now? Also I'd like to see a screen shot to be clear what we are talking about. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c30 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(okurz@suse.com) --- Comment #30 from Dr. Werner Fink <werner@suse.com> --- (In reply to Oliver Kurz from comment #29)

Created attachment 741109 [details] screenshot of yast ncurses UI within SLES 15 build 260.4

zypper search --details --installed-only ncurses S | Name | Type | Version | Arch | Repository

--+---------------------+---------+------------+--------+-------------------- ------------ i | libncurses6 | package | 6.0-3.6 | x86_64 | SLE-Module-Basesystem15-Pool i | libyui-ncurses-pkg8 | package | 2.48.5-1.2 | x86_64 | SLE-Module-Basesystem15-Pool i | libyui-ncurses8 | package | 2.48.4-1.2 | x86_64 | SLE-Module-Basesystem15-Pool i | ncurses-utils | package | 6.0-3.6 | x86_64 | SLE-Module-Basesystem15-Pool

Useless ... please do rpm -q --changelog libncurses6 | head -n 20 beside this: IS this the latest YaST2 ncurses GUI package? Compare with changelog Tue Jul 4 07:58:10 UTC 2017 - mfilka@suse.com - bnc#1047145 - patch to make the package buildable by gcc7 (by werner@suse.com) - 2.48.3 Tue May 9 14:11:59 CEST 2017 - snwint@suse.de - adjustments needed to work with latest ncurses update (bsc#1034922) - 2.48.2 Also provide a character image with the help of tee. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c33 --- Comment #33 from Dr. Werner Fink <werner@suse.com> --- Got some feedback from upstream, compare with https://lists.gnu.org/archive/html/bug-ncurses/2017-09/msg00013.html that is that the rep (repeate_character) works only for ascii line drawings and only if the ASCII code of the line drawing character is used tput -S <<! smacs rep 45 20 rmacs ! works where as `-' for ASCII character 45 does not tput -S <<! smacs rep - 20 rmacs ! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c35 --- Comment #35 from Dr. Werner Fink <werner@suse.com> --- All four line glpyhs do work tput -S <<! smacs rep 112 20 rmacs ! ⎻⎻⎻⎻⎻⎻⎻⎻⎻⎻⎻⎻⎻⎻⎻⎻⎻⎻⎻⎻ tput -S <<! smacs rep 113 20 rmacs ! ──────────────────── tput -S <<! smacs rep 114 20 rmacs ! ⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼⎼ tput -S <<! smacs rep 115 20 rmacs ! ⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽⎽ -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c42 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner@suse.com Flags| |needinfo? --- Comment #42 from Dr. Werner Fink <werner@suse.com> --- Beside the ncurses GUI of YaST2 ... which ncurses based applications around here do have similar problems with latest ncurses proclaiming the XTerm feature of repeating characters in the terminfo entry xterm? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c44 --- Comment #44 from Imobach Gonzalez Sosa <igonzalezsosa@suse.com> --- (In reply to Dr. Werner Fink from comment #42)

Beside the ncurses GUI of YaST2 ... which ncurses based applications around here do have similar problems with latest ncurses proclaiming the XTerm feature of repeating characters in the terminfo entry xterm?

ncdu, for instance, is having the same problem. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c46 Oliver Kurz <okurz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(okurz@suse.com) | --- Comment #46 from Oliver Kurz <okurz@suse.com> --- (In reply to Dr. Werner Fink from comment #30)

Useless ... please do

rpm -q --changelog libncurses6 | head -n 20

# rpm -q --changelog libncurses6 | head -n 20 * Mon Jul 31 2017 werner@suse.de - Add ncurses patch 20170729

Also provide a character image with the help of tee.

I don't understand what I should do here. I tried 'yast2 2>&1 | tee 2>&1' to no avail - if that would be any useful. (In reply to Dr. Werner Fink from comment #42)

Beside the ncurses GUI of YaST2 ... which ncurses based applications around here do have similar problems with latest ncurses proclaiming the XTerm feature of repeating characters in the terminfo entry xterm?

Something as simple as `dialog --yesno "foo" 3 20` also looks broken on SLES15 build 260.4 so very simple to reproduce I assume. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c48 --- Comment #48 from Dr. Werner Fink <werner@suse.com> --- Created attachment 741365 --> http://bugzilla.suse.com/attachment.cgi?id=741365&action=edit dialog.png with ncurses 6.0-20170916 (In reply to Oliver Kurz from comment #46)

Something as simple as `dialog --yesno "foo" 3 20` also looks broken on SLES15 build 260.4 so very simple to reproduce I assume.

Here I've ncurses 6.0-20170916 with # infocmp -T xterm -1 | grep rep= # rep=%p1%c\E[%p2%{1}%-%db, within an real XTerm (xterm 308) ... I'll try yast2 ncurses as next -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c50 --- Comment #50 from Dr. Werner Fink <werner@suse.com> --- Created attachment 741367 --> http://bugzilla.suse.com/attachment.cgi?id=741367&action=edit yast-nui.png with ncurses 6.0-20170916 and TERM=xterm with rep feature -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c53 --- Comment #53 from Dr. Werner Fink <werner@suse.com> --- (In reply to Nick Singer from comment #52)

(In reply to Dr. Werner Fink from comment #51)

...

Please retest with at least ncurses 6.0-20170916

Do you have any repo I could add to test this newer version?

Just for the record; I've updated my TW today with the following versions and is still broken:

https://download.opensuse.org/repositories/Base:/System/openSUSE_Factory/ or with osc osc ls -b Base:System ncurses openSUSE_Factory/x86_64 ::import::i586::libncurses5-32bit-6.0-421.1.x86_64.rpm ::import::i586::libncurses5-32bit-debuginfo-6.0-421.1.x86_64.rpm ::import::i586::libncurses6-32bit-6.0-421.1.x86_64.rpm ::import::i586::libncurses6-32bit-debuginfo-6.0-421.1.x86_64.rpm ::import::i586::ncurses-devel-32bit-6.0-421.1.x86_64.rpm ::import::i586::ncurses-devel-32bit-debuginfo-6.0-421.1.x86_64.rpm _buildenv _statistics libncurses5-6.0-421.1.x86_64.rpm libncurses5-debuginfo-6.0-421.1.x86_64.rpm libncurses6-6.0-421.1.x86_64.rpm libncurses6-debuginfo-6.0-421.1.x86_64.rpm ncurses-6.0-421.1.src.rpm ncurses-debuginfo-6.0-421.1.x86_64.rpm ncurses-debugsource-6.0-421.1.x86_64.rpm ncurses-devel-6.0-421.1.x86_64.rpm ncurses-devel-debuginfo-6.0-421.1.x86_64.rpm ncurses-utils-6.0-421.1.x86_64.rpm ncurses-utils-debuginfo-6.0-421.1.x86_64.rpm ncurses5-devel-6.0-421.1.x86_64.rpm rpmlint.log tack-6.0-421.1.x86_64.rpm tack-debuginfo-6.0-421.1.x86_64.rpm terminfo-6.0-421.1.x86_64.rpm terminfo-base-6.0-421.1.x86_64.rpm terminfo-iterm-6.0-421.1.x86_64.rpm terminfo-screen-6.0-421.1.x86_64.rpm -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c56 --- Comment #56 from Dr. Werner Fink <werner@suse.com> --- (In reply to Nick Singer from comment #55)

Thanks. I've added this repo and force-installed libncurses6 again. This resulted only in a vendor-change for libncurses6 and ncurses-devel (expected). Now ncurses applications (weechat, tmux, htop, ncmpcpp and ncdu tested) seem to work fine again with rxvt-unicode as terminal emulator and TERM=xterm-256color. I've not tested other terminal emulators / TERM-variables yet.

Seems to be sufficient: infocmp -T xterm-256color -1 | grep rep= rep=%p1%c\E[%p2%{1}%-%db, -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c58 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(okurz@suse.com) --- Comment #58 from Dr. Werner Fink <werner@suse.com> --- (In reply to Oliver Kurz from comment #57)

https://openqa.suse.de/tests/1181415/modules/welcome/steps/1 shows a problem in the installer of SLE15 build 274.1 over a IPMI remote control interface. https://openqa.suse.de/tests/1179378#step/welcome/1 is a reference of SLE12SP2 displayed correctly. Without an updated installer image or at least a DUD for the installation medium I don't think I can be of much help to fix these issues. Of course, when someone supplies me a SLE repo with updated ncurses I can try to fix the issue we already saw in xterm/gnome-terminal. I recommend to regard this ticket with high priority regarding to SLE15 development.

Hmm ... and what exactly can I do here? Maybe it is a better idea to asign this bug to someone which has the decision control about Tumbleweed as well as about SLES15 as otherwise nothing will happen -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c60 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |behlert@suse.com, | |lnussel@suse.com Flags| |needinfo?(behlert@suse.com) --- Comment #60 from Dr. Werner Fink <werner@suse.com> --- Questions:a) whern will the ncurses version from Base:System reach Tumbleweed and b) whern will this happen for SLES-15, and at least but not least c) should I disable the declaration of the "rep" feature (repeat character up to the point where all broken terminal emluators (compare bug#1056020) become fixed e.g. do support the repeat character feature? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c62 --- Comment #62 from Oliver Kurz <okurz@suse.com> --- (In reply to Dr. Werner Fink from comment #60)

Questions:a) whern will the ncurses version from Base:System reach Tumbleweed

I don't see any pending requests in https://build.opensuse.org/package/requests/openSUSE:Factory/ncurses so I guess you refer to https://build.opensuse.org/request/show/527053 that was accepted 7 days ago. According to https://build.opensuse.org/project/dashboard/openSUSE:Factory/ the snapshot under current testing is 20170924 which should include your update but the snapshot was not yet released because there are still some openQA test failures unaccounted for on https://openqa.opensuse.org/tests/overview?distri=opensuse&version=Tumbleweed&group=openSUSE%20Tumbleweed but I assume the new version will be published today as I read out from the chat log on [#opensuse-factory](irc://chat.freenode.net/opensuse-factory) and b) whern will this happen for SLES-15 https://build.suse.de/request/show/141972 is the last auto-submit 5 days ago and already accepted which looks like including the same state as for https://build.opensuse.org/request/show/527053 so the new build should also include that already. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 Roger Whittaker <roger.whittaker@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roger.whittaker@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c66 --- Comment #66 from Dr. Werner Fink <werner@suse.com> --- (In reply to Egmont Koblinger from comment #65)

Nitpicking:

The attached "shell script rep.tst" contains commands like "rep 108 0".

REP, by its nature, contains an important off by one. E.g. to print a character 20 times in total, you print it first and then repeat it 19 times. Apparently the "tput rep" command expects to receive 20 as its argument in this case, and subtracts one for the generated repeater escape sequence "\e[19b".

As a result, "tput rep 108 0" prints the letter "l" once, followed by "\e[-1b" as if it was a valid escape sequence to repeat it -1 times.

xterm silently swallows this, resulting in "l" appearing once. VTE's (gnome-terminal's) forthcoming patch will display garbage. konsole also displays garbage.

I don't think "rep 108 0" or its emitted escape sequence "\e[-1b" are valid ones and I don't think any particular behavior is expected here from terminal emulators.

I've added your comment to bug boo#1056020 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c79 --- Comment #79 from Dr. Werner Fink <werner@suse.com> --- I'm not able anymore to login at https://bugs.kde.org/ ... looks like a disabled account -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c81 Luca Beltrame <lbeltrame@kde.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lbeltrame@kde.org | |) | --- Comment #81 from Luca Beltrame <lbeltrame@kde.org> --- The change highlighted (https://phabricator.kde.org/D10064) is still not merged upstream. We could add it to our package as a workaround. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c83 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(lbeltrame@kde.org | |) --- Comment #83 from Dr. Werner Fink <werner@suse.com> --- Please can you tell me what is the status here? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c85 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kde-maintainers@suse.de, | |opensuse-kde-bugs@opensuse. | |org Flags| |needinfo?(opensuse-kde-bugs | |@opensuse.org), | |needinfo?(kde-maintainers@s | |use.de) --- Comment #85 from Dr. Werner Fink <werner@suse.com> --- Just ported and added the Diff 25855 from to konsole-17.12.1, see SR#571633 please consider to review and if possible to accept and forward this ASAP beause we have several products like Leap15 and SLES15 as well as Tumbleweed user out there -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c90 --- Comment #90 from Tad Bilby <tadbilby@gmail.com> --- No. xterm properly "back spaces". koi8rxterm also works properly. The problem is related to konsole. NAME="openSUSE Tumbleweed" # VERSION="20180205 Linux localhost.localdomain 4.15.0-1-default #1 SMP PREEMPT Wed Jan 31 07:03:28 UTC 2018 (ac01747) x86_64 x86_64 x86_64 GNU/Linux konsole 17.04.2 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c92 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #92 from Dr. Werner Fink <werner@suse.com> --- Next is all other terminal emulators like in gnome, in xfce4 oand other whic hare used with TERM=xterm(-whatever): do they work together with ncurses and its correct terminfo entry for the XTerm? If not please clone this bug and adapt the subject for the specific terminal emulator so that we get those fixed (e.g. support of the REP feature of the XTerm) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c104 --- Comment #104 from Tad Bilby <tadbilby@gmail.com> --- (In reply to Wolfgang Bauer from comment #96)

PS, just noticed this: (In reply to Tad Bilby from comment #90)

...

konsole 17.04.2

Is this really true? The current konsole version in Tumblweed is 17.12.1, and does contain the added REP support.

17.04.2 is Leap 42.3's version.

I'm uncertain to run zypper dup. I believe that would update my console version. I running "zypper up -l --replacefiles -y" and konsole is not updating. I have read that I can create an unstable system since I use the packman repo for multimedia codecs and extensions. zypper dup --allow-vendor-change ## 1st choice, lots of pkgs changed! zypper dup --no-allow-vendor-change ## safer option?! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c106 --- Comment #106 from Tad Bilby <tadbilby@gmail.com> --- Created attachment 759471 --> http://bugzilla.suse.com/attachment.cgi?id=759471&action=edit screenshot of ncurses not displaying correctly. This should be a square box. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1054448 http://bugzilla.suse.com/show_bug.cgi?id=1054448#c121 --- Comment #121 from Tad Bilby <tadbilby@gmail.com> --- Thank you for the script. Tumbleweed has forced me to do a "clean" upgrade by removing all of the third party repos. ncurses properly displays the menu now with xterm-256color. # file /usr/local/bin/vpn /usr/local/bin/vpn: setuid ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, for GNU/Linux 2.6.9, , stripped LSB_VERSION="core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64" NAME="openSUSE Tumbleweed" # VERSION="20180905" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20180905" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20180905" Linux 4.18.5-1-default #1 SMP PREEMPT Fri Aug 24 12:38:43 UTC 2018 (9e91e29) x86_64 x86_64 x86_64 GNU/Linux Time for me to file a new bug. I have a new problem unrelated to this thread.... keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 key The Xauthority error happens when I start any executable as a unprivileged user. I have deleted the .Xauthority file logged out and back in. The binary runs properly. Thanks again, Tad -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1054448 https://bugzilla.suse.com/show_bug.cgi?id=1054448#c125 --- Comment #125 from Oliver Kurz <okurz@suse.com> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: create_hdd_ha_textmode https://openqa.suse.de/tests/5924008 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1054448 https://bugzilla.suse.com/show_bug.cgi?id=1054448#c127 --- Comment #127 from Oliver Kurz <okurz@suse.com> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: create_hdd_textmode https://openqa.suse.de/tests/5989991 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1054448 https://bugzilla.suse.com/show_bug.cgi?id=1054448#c129 --- Comment #129 from openQA Review <openqa-review@suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: create_hdd_textmode https://openqa.suse.de/tests/5989991 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.