Your patch below works perfectly well. Again, I have implemented it with
and without my custom .rcrc and everything will work just as expected.
Thank you very much. I've learned a lot with this.
Kindest regards,
Ricardo Peliquero
> From 200b7d217ee3ac54b376116e7d64ce0844ecbed9 Mon Sep 17 00:00
[2018-12-31 13:46] Ricardo Peliquero
> > * setenv("LANG", "C.UTF-8", 1)
>
> It works as a breeze.
> Able to type 'ñandú' and other stuff with LANG=C.UTF-8.
> I can always put LANG=es_AR.UTF-8 and LANGUAGE=es_AR:es into .rcrc in
> order to fit my local needs, and it still works perfectly well.
Dmitry Bogatov Sat, 29 Dec 2018 18:33:11 +:
> Could you try replace calls to `setlocale(LC_ALL, "")` in previous
> patch with (different variants)
> * setlocale(LC_ALL, "C.UTF-8")
Does not work (patch applies ok but won't be able to type 'ñandú').
> * setenv("LANG", "C.UTF-8", 1)
It wo
[2018-12-27 21:07] Ricardo Peliquero
> Dmitry Bogatov Sat, 22 Dec 2018 13:33:18 +:
>
> > $ dgit clone fgetty
> > $ cd fgetty
> > $ git am /path/to/this/message
> > $ dgit build
> > $ sudo debi
>
> I had to specify xx.changes location to last instruction.
> ; su -c 'debi ../fgetty_0.7
Dmitry Bogatov Sat, 22 Dec 2018 13:33:18 +:
> $ dgit clone fgetty
> $ cd fgetty
> $ git am /path/to/this/message
> $ dgit build
> $ sudo debi
I had to specify xx.changes location to last instruction.
; su -c 'debi ../fgetty_0.7-4_multi.changes'
Patch applied, but no changes after it.
[2018-12-21 13:52] 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.
Okay. Thank you for knowledge you alr
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
[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 bash
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 | grep
>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.
>
>N
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 non-UTF
[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 probl
> control: tags -1 moreinfo
> > It seems to me now that is more a libreadline6/libtinfo5 problem
> > than especifically of fgetty/login1.
>
> Hi, two years after, with libreadline8 in archives, does problem still
> persist?
>
Dear Dmitry,
Yes, the problem still persists; but, after investigati
control: tags -1 moreinfo
[2016-08-10 14:40] Ricardo Fabian Peliquero
> You are right.
>
> It seems to me now that is more a libreadline6/libtinfo5 problem than
> especifically of fgetty/login1.
Hi, two years after, with libreadline8 in archives, does problem still
persist?
You are right.
It seems to me now that is more a libreadline6/libtinfo5 problem than
especifically of fgetty/login1.
Thank you very much! I have learned a lot with this testing.
I've applied your suggestion to .rcrc and have all ttys working as expected.
Regards,
Ricardo
On Wed, Aug 10, 2016
control: tags 833116 +help +reproduce -moreinfo
> [...]
I am sorry. I have to admit, that I do not know, how to help further.
In your particular case, you may want to add
if (~ $RC_BOOTSTRAPPED ()) {
RC_BOOTSTRAPPED = 1
exec $SHELL
}
into your .rcrc.
Try d
On Thu, Aug 04, 2016 at 03:47:19AM +0300, Dmitry Bogatov wrote:
> Please, do following things:
>
> - set emacs (or anything that is interactive and does not link
>readline) as login shell and tell, whether bug arises
ngetty + ed is working ok.
ngetty + francine is working wrong.
> - since
On Thu, Aug 04, 2016 at 03:47:19AM +0300, Dmitry Bogatov wrote:
>
> > > > When trying to login with fgetty, I could read my password on the
> > > > screen while typing. Did not continue.
> > > > ngetty + login behaves good
> > > > ngetty + login1 will get in well, but no key press will echo on th
> > > When trying to login with fgetty, I could read my password on the screen
> > > while typing. Did not continue.
> > > ngetty + login behaves good
> > > ngetty + login1 will get in well, but no key press will echo on the
> > > console.
> >
> > Sorry, I assumed you read C. This is intended be
On Wed, Aug 03, 2016 at 11:52:57AM +0300, Dmitry Bogatov wrote:
>
> > When trying to login with fgetty, I could read my password on the screen
> > while typing. Did not continue.
> > ngetty + login behaves good
> > ngetty + login1 will get in well, but no key press will echo on the console.
>
>
> When trying to login with fgetty, I could read my password on the screen
> while typing. Did not continue.
> ngetty + login behaves good
> ngetty + login1 will get in well, but no key press will echo on the console.
Sorry, I assumed you read C. This is intended behaviour. Please,
continue and
> control: tags -moreinfo +help
>
I have applied the following patch as instructed. Please, see the results at
the bottom.
> - please apply following patch and tell, if anything changes
--- a/login.c
+++ b/login.c
@@ -45,17 +45,9 @@ void die(const char *message) {
struct termios oldtermios;
Made some experiments below. Will continue tonight.
On Tue, Aug 02, 2016 at 02:37:02PM +0300, Dmitry Bogatov wrote:
>
> control: tags -moreinfo +help
>
> Seems I managed to somehow reproduce it. I can reproduce only with
> root login. I need some time to accustomize myself to `la-latin1' and
> t
control: tags -moreinfo +help
> Made some progress here! I haven't tried all your suggestions yet, but please
> see below.
Great.
> On Mon, Aug 01, 2016 at 10:06:49PM +0300, Dmitry Bogatov wrote:
> >
> > How insert this fancy letter "?"? I tried to `loadkeys es', but I
> > failed to locate thi
Made some progress here! I haven't tried all your suggestions yet, but please
see below.
On Mon, Aug 01, 2016 at 10:06:49PM +0300, Dmitry Bogatov wrote:
>
> How insert this fancy letter "?"? I tried to `loadkeys es', but I
> failed to locate this letter.
My keyboard layout is Latin American Spa
> > Do I understand correctly, that /bin/bash, which is execed directly by
> > fgetty behaves bad, but any it's child is okay?
> That is correct. If /bin/bash -or other command interpreters
> available in Debian- are accessed through fgetty, they b ehave bad
> (interpretting [�-�] or "�" key pres
control: tags 833116 +moreinfo
Thank you for your fast response.
>
> > When running virtual ttys with fgetty, I cannot type any spanish
> > accented vowel nor the "eñe" into the console shell.
>
> What do you call 'console shell'? /bin/bash?
The problem only happens after logging into virtual
control: tags 833116 +moreinfo
> When running virtual ttys with fgetty, I cannot type any spanish
> accented vowel nor the "eñe" into the console shell.
What do you call 'console shell'? /bin/bash?
> I suspect it is a checkpassword.login problem.
> If I run a subshell (e.g. bash, rc, dash) or a
Package: fgetty
Version: 0.7-1
Severity: normal
Dear Maintainer,
When running virtual ttys with fgetty, I cannot type any spanish accented vowel
nor the "eñe" into the console shell. I suspect it is a checkpassword.login
problem.
If I run a subshell (e.g. bash, rc, dash) or a readline dependan
29 matches
Mail list logo
