Bug 147822
Summary: | rxvt, xterm backdpace key is incorrect | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | patrick |
Component: | ncurses | Assignee: | Eido Inoue <havill> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | hdegoede |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-02-11 20:36:33 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
patrick
2005-02-11 17:42:25 UTC
rxt should be rxvt Could not reproduce using a stock FC-3 (I'm assuming that's what you meant with test3 version) with updates; perl and other apps backspace worked fine (with kbs as ^H)-- in konsole (assuming you were testing with TERM=konsole and TERM=xterm), xterm, and rxvt (assuming TERM=rxvt and TERM=xterm). As rxvt is not included with FC3 Core, I tested against the Fedora Extras version at http://download.fedora.us/fedora/fedora/3/i386/RPMS.extras/. My system was first installed redhat 6.1 and upgraded manually through the years using either rpm -Fvh or apg-get upgarde. It is now the equivalent of fedora core 3. Some time ago this problem started, it affects TERM=rxvt and TERM=xterm (as used by kde's konsole app). It affects all users and has been driving me crazy for some time. So the other day I investigated and found that the terminfo changes fix the problem. However, I have not tried a virgin FC3 install and I have always been baffled as to why this problem had not been fixed. It seems to me that something is mapping my backspace to ^? instead of ^H, I just cant figure out what on earth it could be. It seems this isn't a bug in fc3 after all, but any help in tracking down what the true problem could be would be appreciated. I have tracked down the problem. At somepoint rpm did not upgrade my: /etc/bashrc using the /etc/bashrc.rpmnew I found there has fixed the problem. Sorry to trouble you. The real cause of this is ofcourse bug 142659, the old bashrc contained stty erase `tput kbs` Which appearantly has been removed, relying on the terminal to set the stty erase correct itself, which is okay, but generates an inconcistency between stty erase and terminfo. Havill you might want to read bug 142569 as this is the result of the much discussed bug 122815 and your input there would be very welcome. |