Bug 58546
Summary: | nvi-m17n-canna loops by Ctrl-space-key | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kazutoshi Morioka <morioka> |
Component: | nvi-m17n | Assignee: | Akira TAGOH <tagoh> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | mattdm |
Target Milestone: | --- | Keywords: | i18n |
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-04-27 04:08:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Kazutoshi Morioka
2002-01-19 09:06:19 UTC
I just remembered a fact "Red Hat Japan is irresponsible." So I start to debug it. This one seems to be related to key-mapping. I found a patch below gives a workaround. --- nvi-1.79/common/seq.c.orig Thu Feb 14 20:07:20 2002 +++ nvi-1.79/common/seq.c Thu Feb 14 20:15:58 2002 @@ -45,6 +45,8 @@ SEQ *lastqp, *qp; int sv_errno; + if (input == NULL || *input == '\0') + return(0); /* * An input string must always be present. The output string * can be NULL, when set internally, that's how we throw away nvi's source package has it's own curses/termcap functions. One of these functions, tigetstr() do not work properly on Red Hat Linux 7.x. This is heart of the bug. Above patch gives workaround, but cursor-keys still do not work. Fedora Core 2 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC3 updates or in the FC4 test release, reopen and change the version to match. I confirmed latest nvi-m17n-canna-1.79-20011024.19 never shows this bug. I think this had beed fixed at somewhere in the upstream m17n-patches. I don't know why this bug is still opened. thanks. |