Re: Bug#833116: fgetty: Incorrect keystroke interpretation

2018-12-21 Thread Anton Zinoviev
On Thu, Dec 20, 2018 at 06:02:47PM +, Dmitry Bogatov wrote: > > Anton, could you please clarify, how locale is set up by this function > call if process inhereted no locale-related variables. I don't know. Anton Zinoviev

Re: Bug#833116: fgetty: Incorrect keystroke interpretation

2018-12-20 Thread Dmitry Bogatov
[2018-12-19 10:42] Ricardo Peliquero > Anton Zinoviev > Wed, 5 Dec 2018 21:29:10 +0200: > > > On Wed, Dec 05, 2018 at 08:56:16AM +, Dmitry Bogatov wrote: > > > Suppose that we have a working bash shell with UTF-8 console where ñ > > displays properly. Then try this: > > > > LANG=C

Re: Bug#833116: fgetty: Incorrect keystroke interpretation

2018-12-19 Thread Ricardo Peliquero
Dear all, I have tested Anton's suggestions with the following results. Please, see below for more information. Steps made: ; su - -c 'adduser testbash' ... ; cat /etc/passwd | grep testbash testbash:x:1002:1002:Test Bash,,,:/home/testbash:/bin/bash ; cat /etc/inittab | grep /sbin/getty |

Re: Bug#833116: fgetty: Incorrect keystroke interpretation

2018-12-05 Thread Ricardo F. Peliquero
>Suppose that we have a working bash shell with UTF-8 console where ñ >displays properly. Then try this: > >LANG=C bash # run a subshell in a non-UTF8 locale > >If you press ñ, you will see (arg: 1). The programs (including a >subshell) also work incorrectly because the locale is not UTF8. >

Re: Bug#833116: fgetty: Incorrect keystroke interpretation

2018-12-05 Thread Anton Zinoviev
On Wed, Dec 05, 2018 at 08:56:16AM +, Dmitry Bogatov wrote: > > [ Added console-setup maintainers into thread ] > Hello, dear console-setup maintainers. Could you please take a look at > this bug? Maybe the locale is not set properly by some versions of getty? If bash is started in a

Re: Bug#833116: fgetty: Incorrect keystroke interpretation

2018-12-05 Thread Dmitry Bogatov
[2018-12-03 10:48] Ricardo Peliquero > > [ Dmitry Bogatov ] > > Hi, two years after, with libreadline8 in archives, does problem still > > persist? > > > Yes, the problem still persists; but, after investigating a little bit > more, it seems to me that it could be a console-setup package