Bug 116667
Summary: | line edit gets confused by non-ASCII characters in VT | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alexandre Oliva <oliva> |
Component: | kbd | Assignee: | Miloslav Trmač <mitr> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | twaugh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-02-18 15:11:10 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
Alexandre Oliva
2004-02-24 09:47:00 UTC
Changing component (bash has its own readline). Need to know what locale you are using. Can you confirm that the character you are typing is a question mark (query) inside a circle? Ugh. The character is an a with an acute accent: á. Dunno why it didn't make it properly. locale is en_US.UTF-8. Can't reproduce this. Which terminal are you using? VT1 (text console). Whatever terminal emulation that implies. Can you still reproduce this? 'fraid so, with yesterday's rawhide. Can you try bash-3.0-1 please? No change :-( I'm afraid I haven't been able to reproduce this here. Mind telling me what you tried? I can readily duplicate it on FC2 and FC3test1, on a UTF8 locale and with the us-acentos keyboard configuration on a text console. Note I'm not talking about random terminal emulators, I'm talking about the terminal you get after switching to VT1 with Ctrl-Alt-F1. I switched to VT1 and followed your "steps to reproduce" in the original report. If you can repeat this 100% please try rephrasing how to get this to happen, telling me which keys to press and in which order -- I wasn't sure if I needed to press return or anything (I didn't). I have a US keyboard here: all of the test machines I have access to do. :-( I had to put an a-acute in .bash_history and use C-k/C-y. Tell me a better way to do this. Aha! So you didn't configure the keyboard as US-International (us-acentos in /etc/sysconfig/keyboard)? I suspect that's a key step to duplicate the problem, because us-acentos generates iso-8859-1 even if the default locale is UTF-8. It appears that this is what bash doesn't like: incomplete multi-byte sequences. Sounds like us-acentos needs to be fixed. All bets are off if there are incomplete multi-byte sequences -- there isn't any good behaviour in that case. has multibyte compose sequences been fixed in the kernel yet? if not, this bug is blocked As a work-around, you could choose a keymap that doesn't need dead keys or compose to produce the characters you need, and load it using loadkeys -u. *** This bug has been marked as a duplicate of 143014 *** |