[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#23194: Benign error in installation image: "stty: standard input: In

From: Ludovic Courtès
Subject: bug#23194: Benign error in installation image: "stty: standard input: Input/output error"
Date: Thu, 07 Dec 2017 10:18:16 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)

Hi Chris,

address@hidden (Ludovic Courtès) skribis:

> Chris Marusich <address@hidden> skribis:
>> In the installation image for GuixSD v0.10.0, I get some I/O errors on
>> the terminal just before/during/after the MOTD is displayed:
>> "stty: standard input: Input/output error"
> These appear to come from the ‘unicode_start’ command, run by the
> ‘console-font’ services.  ‘unicode_start’ is a shell script in the ‘kbd’
> package that does:
>   stty iutf8
> In a ‘guix system vm gnu/system/install.scm’ VM in current master, I
> sometimes get a different message:
>   unicode_start skipped on not a tty
> The “not a tty” string comes from the ‘tty’ command (Coreutils).  We get
> it when:
>   ttyname (STDIN_FILENO);
> returns NULL; this can happen if ‘tcgetattr’ returns NULL (see ttyname.c
> in libc.)

I’m happy to say that this is fixed in the 0.14.0 installation image:


We now use our ‘tcsetattr’ bindings directly instead of invoking
‘unicode_start’.  Additionally, we wait until the TTY really exists
(i.e., mingetty has become its session leader) by checking the return
value of ‘ttyname’.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]