[debbugs-tracker] bug#23194: closed (Benign error in installation image: "stty: standard input: Input/output error")

[GNU bug Tracking System]

Your message dated Thu, 07 Dec 2017 10:18:16 +0100
with message-id <address@hidden>
and subject line Re: bug#23194: Benign error in installation image: "stty: 
standard input: Input/output error"
has caused the debbugs.gnu.org bug report #23194,
regarding Benign error in installation image: "stty: standard input: 
Input/output error"
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
23194: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23194
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: Benign error in installation image: "stty: standard input: Input/output error" Date: Sat, 02 Apr 2016 14:09:51 -0700

Hi,

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"

The error appears to be benign because I encountered no actual problems
with input or output.  However, it would be nice to find out why this is
being emitted and fix it, so that errors are not the first thing that
new GuixSD users see when installing the system.

-- 
Chris

signature.asc
Description: PGP signature

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: 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:
>
>   
> https://git.savannah.gnu.org/cgit/guix.git/commit/?h=version-0.14.0&id=787e8a80d54d8bd5320d76276dc5f4bafe5b86c0
>
> 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’.
>
> Ludo’.
>
>
> --- End Message ---