Danny Milosavljevic <dan...@scratchpost.org> skribis:
> On Sun, 18 Feb 2018 01:01:31 +0100
> l...@gnu.org (Ludovic Courtès) wrote:
>> The “\x1b;%G” sequences correspond to the “select UTF-8” console code
>> (see console_codes(4)). We’re receiving this as if we were a console,
>> but in fact all we want is to exchange raw bytes between the host and
>> the guest; we don’t want to be a full-fledged console.
> A lot of the tests pass console=... and thus in fact have a real console.
> It might be that our new automatic console getty interferes.
> I doubt it - I checked agetty sources and it doesn't touch iutf8.
> Might still be worth a try to remove agetty from %base-services.
This isn’t the culprit.
I hadn’t noticed this is now part of ‘%base-services’. It would be nice
if it were enabled on ARM only. Thoughts?
>> this happens on ‘core-updates’ and not ‘master’.
> That's a good question.
> Anyway, I think these codes are emitted by unicode_start - so
> as a first step, sabotage the kbd package so that it can't
> use unicode_start. Does it work then?
Commenting out (display "\x1b%G" (fdes->outport fd)) in (gnu services
base) appear to solve the problem. It seems that it used to affect just
the terminal behind FD and now somehow broadcasts to all existing
Anyway, I’m unsure this ‘display’ call was needed at all. It seems
redundant with the ‘tcsetattr’ call below. So I think we’ll just remove