all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 23194@debbugs.gnu.org
Subject: bug#23194: Benign error in installation image: "stty: standard input: Input/output error"
Date: Mon, 04 Apr 2016 16:50:40 +0200	[thread overview]
Message-ID: <87fuv1ctrz.fsf@gnu.org> (raw)
In-Reply-To: <87lh4v7m5c.fsf@gmail.com> (Chris Marusich's message of "Sat, 02 Apr 2016 14:09:51 -0700")

Chris Marusich <cmmarusich@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.)

The ‘stty’ error you mention also happens when ‘tcgetattr’ fails and
returns EIO (stty.c in Coreutils):

--8<---------------cut here---------------start------------->8---
    device_name = _("standard input");

  if (tcgetattr (STDIN_FILENO, &mode))
    error (EXIT_FAILURE, errno, "%s", device_name);
--8<---------------cut here---------------end--------------->8---

‘tcgetattr’ is actually an alias for the TCGETS ioctl.  Looking at the
kernel, I don’t see under what circumstances we can get EIO.

That’s all I have for now!

Thanks for your report.
Ludo’.

  parent reply	other threads:[~2016-04-04 14:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-02 21:09 bug#23194: Benign error in installation image: "stty: standard input: Input/output error" Chris Marusich
2016-04-03  6:27 ` Efraim Flashner
2016-04-03  6:52   ` Chris Marusich
2016-04-04 14:50 ` Ludovic Courtès [this message]
2017-12-07  9:18   ` Ludovic Courtès
2016-04-04 15:10 ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fuv1ctrz.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=23194@debbugs.gnu.org \
    --cc=cmmarusich@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.