GNU bug report logs - #23194
Benign error in installation image: "stty: standard input: Input/output error"

Previous Next

Package: guix;

Reported by: Chris Marusich <cmmarusich <at> gmail.com>

Date: Sat, 2 Apr 2016 21:11:02 UTC

Severity: normal

Done: ludo <at> gnu.org (Ludovic Courtès)

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Chris Marusich <cmmarusich <at> gmail.com>
Subject: bug#23194: closed (Re: bug#23194: Benign error in installation
 image: "stty: standard input: Input/output error")
Date: Thu, 07 Dec 2017 09:19:02 +0000
[Message part 1 (text/plain, inline)]
Your bug report

#23194: Benign error in installation image: "stty: standard input: Input/output error"

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 23194 <at> debbugs.gnu.org.

-- 
23194: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23194
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: ludo <at> gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich <at> gmail.com>
Cc: 23194-done <at> debbugs.gnu.org
Subject: Re: bug#23194: Benign error in installation image: "stty: standard
 input: Input/output error"
Date: Thu, 07 Dec 2017 10:18:16 +0100
Hi Chris,

ludo <at> gnu.org (Ludovic Courtès) skribis:

> Chris Marusich <cmmarusich <at> gmail.com> 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’.

[Message part 3 (message/rfc822, inline)]
From: Chris Marusich <cmmarusich <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: Benign error in installation image: "stty: standard input:
 Input/output error"
Date: Sat, 02 Apr 2016 14:09:51 -0700
[Message part 4 (text/plain, inline)]
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 (application/pgp-signature, inline)]

This bug report was last modified 7 years and 164 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.