Hello,
On Mon, Nov 07, 2005 at 11:45:07PM +0200, Alexander Gattin wrote:
> On Sun, Nov 06, 2005 at 12:29:43PM +0100, Helge Kreutzmann wrote:
> > I replaced one terminal of mine with:
> > 9:23:respawn:/sbin/mingetty tty9
> >
> > and it at least fixes this bug.
I put in now on all VCs and see if an
Hi!
On Sun, Nov 06, 2005 at 12:29:43PM +0100, Helge Kreutzmann wrote:
> I replaced one terminal of mine with:
> 9:23:respawn:/sbin/mingetty tty9
>
> and it at least fixes this bug.
yes, mingetty is:
1) for virtual consoles only (i.e. no serial lines
support and thus no bitness-autodetection)
Hello Alexander,
On Fri, Sep 30, 2005 at 06:04:37PM +0200, Helge Kreutzmann wrote:
> On Fri, Sep 30, 2005 at 12:24:12AM +0300, Alexander Gattin wrote:
> > IMHO, getty could be patched easily, maybe some option
> > may be added to suppress "tty-bitness-autodetection"
> > feature and this would be do
Hello Alexander,
On Fri, Sep 30, 2005 at 12:24:12AM +0300, Alexander Gattin wrote:
> On Thu, Sep 29, 2005 at 05:53:40PM +0200, Helge Kreutzmann wrote:
> > first of all, I found out, that if I enter a "sane" login name (does
> > not need to exist) and press enter twice, then I can safely enter
> > u
reassign 221290 util-linux
thanks
Hi!
On Thu, Sep 29, 2005 at 05:53:40PM +0200, Helge Kreutzmann wrote:
> first of all, I found out, that if I enter a "sane" login name (does
> not need to exist) and press enter twice, then I can safely enter
> umlauts, even delete them (no visual artefacts) and
Hello,
first of all, I found out, that if I enter a "sane" login name (does
not need to exist) and press enter twice, then I can safely enter
umlauts, even delete them (no visual artefacts) and everything is fine
after login. So only the first call to getty is vulnerable to this
effect. If I exceed
Hi!
On Wed, Sep 28, 2005 at 10:46:23PM +0200, Helge Kreutzmann wrote:
> Hello Alexander,
> On Wed, Sep 28, 2005 at 10:48:46PM +0300, Alexander Gattin wrote:
> > After a small, fast and simple check I conclude that
> > the issue with setting cs7 on terminal after entering
Probably istrip (clear 8t
Hello Alexander,
On Wed, Sep 28, 2005 at 10:48:46PM +0300, Alexander Gattin wrote:
> After a small, fast and simple check I conclude that
> the issue with setting cs7 on terminal after entering
> non-ascii letters into "login:" prompt is really a
> probem with /sbin/getty (util-linux pkg).
Confirm
Hi!
After a small, fast and simple check I conclude that
the issue with setting cs7 on terminal after entering
non-ascii letters into "login:" prompt is really a
probem with /sbin/getty (util-linux pkg).
On Wed, Sep 28, 2005 at 07:49:14PM +0300, Alexander Gattin wrote:
> > When I run stty -a in a
> > Right?
>
> No. Please tag it "help" if you do not know the cause. I tried to have
> a look at the sources, but frankly I don't know how login sets console
> properties, hence I did not find the problematic point.
Well, it seems that my co-maintainers have a better idea than me about
this pr
tags 221290 confirmed
thanks
On Tue, Sep 27, 2005 at 06:13:25PM +0200, Helge Kreutzmann wrote:
> Well, I don't have an all caps afterwards.
Surely, that's completely another thing, for
historical reasons BTW.
> I just checked (on Sarge)
the same, on linux console, vesafb, UA/UTF-8 keymap
> Whe
Hello Christian,
On Wed, Sep 28, 2005 at 06:46:16AM +0200, Christian Perrier wrote:
> > Anyway this is more general problem but not shadow bug (it is about UTF8
> > support, not about umlauts), so probably nothing should be done in
Well, I think there are two issues here: one about UTF8 support wh
On Tue, 27 Sep 2005, Eugeniy Meshcheryakov wrote:
> 27 вересня 2005 о 18:36 +0200 Tomasz Kłoczko написав(-ла):
> > Eugeniy this is incorrect way .. better will be use IUTF8 atribute
> I know that it is incorrect, i sent this patch only as demonstration of
> the problem.
>
> > from tty level desc
28 вересня 2005 о 06:46 +0200 Christian Perrier написав(-ла):
>
> > Anyway this is more general problem but not shadow bug (it is about UTF8
> > support, not about umlauts), so probably nothing should be done in
> > shadow. But some program should set that flag *before* login run and
> > *all* ter
> Anyway this is more general problem but not shadow bug (it is about UTF8
> support, not about umlauts), so probably nothing should be done in
> shadow. But some program should set that flag *before* login run and
> *all* terminal emulators should set this flag when run in UTF-8 locale
> :(
Th
27 вересня 2005 о 18:36 +0200 Tomasz Kłoczko написав(-ла):
> Eugeniy this is incorrect way .. better will be use IUTF8 atribute
I know that it is incorrect, i sent this patch only as demonstration of
the problem.
> from tty level description. Example from my system:
>
> $ stty -a | grep utf
> -i
On Tue, 27 Sep 2005, Eugeniy Meshcheryakov wrote:
> 27 вересня 2005 о 07:38 +0200 Christian Perrier написав(-ла):
> > I was waiting for upstream resync to deal with this bug report but it
> > still seems to be here.
> >
> > When entering high-ascii characters at the login prompt (usually by
> > m
27 вересня 2005 о 18:23 +0200 Helge Kreutzmann написав(-ла):
> Hello,
> On Tue, Sep 27, 2005 at 05:09:41PM +0300, Eugeniy Meshcheryakov wrote:
> > You can switch terminal to all-caps more easyly: just enter you login in
> > all-caps and then password as usual. So, I think it (all-caps) is normal
>
Hello,
On Tue, Sep 27, 2005 at 01:18:52PM +0200, Tomasz K??oczko wrote:
> No but this must be getty/stty and/or terminal definition related.
>
> Look at output of:
>
> [EMAIL PROTECTED] ~]$ infocmp -I | grep kbs
> is2=\E[!p\E[?3;4l\E[4l\E>, il1=\E[L, kb2=\EOE, kbs=\177,
>
Hello,
On Tue, Sep 27, 2005 at 05:09:41PM +0300, Eugeniy Meshcheryakov wrote:
> You can switch terminal to all-caps more easyly: just enter you login in
> all-caps and then password as usual. So, I think it (all-caps) is normal
> behavior (for historic reasons probably).
Yikes! And no, I haven't s
Hello,
On Tue, Sep 27, 2005 at 07:38:12AM +0200, Christian Perrier wrote:
> When entering high-ascii characters at the login prompt (usually by
> mistake), such as "é", and then hitting Backspace to remove them,
> they're not erased at the prompt...and, when entering the correct
> login and validat
27 вересня 2005 о 07:38 +0200 Christian Perrier написав(-ла):
> I was waiting for upstream resync to deal with this bug report but it
> still seems to be here.
>
> When entering high-ascii characters at the login prompt (usually by
> mistake), such as "é", and then hitting Backspace to remove them
On Tue, 27 Sep 2005, Christian Perrier wrote:
> I was waiting for upstream resync to deal with this bug report but it
> still seems to be here.
>
> When entering high-ascii characters at the login prompt (usually by
> mistake), such as "é", and then hitting Backspace to remove them,
> they're not
I was waiting for upstream resync to deal with this bug report but it
still seems to be here.
When entering high-ascii characters at the login prompt (usually by
mistake), such as "é", and then hitting Backspace to remove them,
they're not erased at the prompt...and, when entering the correct
logi
24 matches
Mail list logo
