public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Anyone else having a problem with bash?
Date: Tue, 7 Jul 2015 17:48:59 -0700	[thread overview]
Message-ID: <20150707174859.19487edb@a6> (raw)
In-Reply-To: CAJ1xhMU0b4v-wmdD390Ag5pxg8=Afe7kyY+ZZtkPWRDHMfxqUg@mail.gmail.com

On Mon, 6 Jul 2015 20:18:18 +0300
Alexander Kapshuk <alexander.kapshuk@gmail.com> wrote:

> On Mon, Jul 6, 2015 at 8:01 PM, walt <w41ter@gmail.com> wrote:
> > My bash problem started a few weeks ago but I can't remember when.
> > This problem is intermittent and hard to reproduce.  I'm seeing it
> > maybe less than ten times per day but often enough to be really
> > annoying.
> >
> > This is the problem:  occasionally bash gets in a state where it
> > stops echoing the characters I type.  The commands I type continue
> > to work properly and I can see the output from them but I can't see
> > the commands on the screen as I type them.
> >
> > So far I've seen this problem start *after* some bash command has
> > finished executing, e.g. after doing 'git diff'.  It never happens
> > when I open a new xterm, before I run a command.
> >
> > I emerged app-shells/sash and I don't see the problem there, so I
> > think this is a bash problem, but I'm just guessing.
> >
> > Any ideas?
> >
> >
> >
> 
> What's the output of 'stty -a'? Is the 'echo' attribute on, 'echo', or
> off, '-echo'?

Finally, after a very busy day of using bash with no problems, this
happened again and 'echo' was off (-echo).

The command triggering the problem was mpv, which I invoked from a
bash prompt to listen to an mp3 podcast file.

I noticed a warning message that mpv was linked against an earlier
version of ffmpeg than the one I have installed now (I'm on ~amd64 so
my rate of package turnover is quite high, naturally).  IIRC the
warning message was displayed in a different color from my normal black
font.  I think this may be true of other instances as well, not sure.

Anyone know of a mechanism that allows an app like mpv to set -echo?

BTW, I typed 'reset' which evidently restored 'echo' (now I can see the
characters I type) but the 'Backspace' key produces '^H' on the
terminal instead of deleting characters.

Next time this happens I'll include the output of stty -a.



  parent reply	other threads:[~2015-07-08  0:49 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 17:01 [gentoo-user] Anyone else having a problem with bash? walt
2015-07-06 17:18 ` Alexander Kapshuk
2015-07-06 19:07   ` [gentoo-user] " »Q«
2015-07-06 20:43     ` Alex Thorne
2015-07-06 14:09       ` Bill Kenworthy
2015-07-08  4:44         ` Jc García
2015-07-08  5:00           ` Anton Shumskyi
2015-07-08  7:00             ` Alan McKinnon
2015-07-08  9:06               ` Florian Gamböck
2015-07-08  9:28                 ` Stephan Müller
2015-07-08 10:08                   ` Florian Gamböck
2015-07-08 10:13                     ` Joerg Schilling
2015-07-08 10:40                       ` Florian Gamböck
2015-07-08 10:53                         ` Joerg Schilling
2015-07-08  0:48   ` walt [this message]
2015-07-08  7:15     ` Florian Gamböck
2015-07-08 13:10       ` Todd Goodman
2015-07-08 13:46         ` Florian Gamböck
2015-07-08 10:17 ` Nikos Chantziaras
2015-07-08 10:29   ` Joerg Schilling
2015-07-09 11:38 ` [gentoo-user] " Stephan Müller
2015-07-09 11:48   ` Neil Bothwick
2015-07-09 12:01     ` Gevisz
2015-07-09 12:07       ` [gentoo-user] " Nikos Chantziaras
2015-07-09 12:20         ` Gevisz
2015-07-09 16:07         ` Neil Bothwick
2015-07-09 17:45           ` Gevisz
2015-07-09 17:54             ` Neil Bothwick
2015-07-09 23:34           ` Nikos Chantziaras
2015-07-09 23:36             ` Nikos Chantziaras
2015-07-09 23:54               ` wraeth
2015-07-10  5:29               ` Franz Fellner
2015-07-10  8:16               ` Neil Bothwick
2015-07-10 15:00                 ` Gevisz
2015-07-10 17:39                   ` Nikos Chantziaras
2015-07-10 22:18                     ` Marc Joliet
2015-07-11 10:22                       ` Nikos Chantziaras
2015-07-11 10:39                         ` Marc Joliet
2015-07-11 20:56                         ` Martin Vaeth
2015-07-12 16:52                           ` Nikos Chantziaras
2015-07-12 17:01                             ` Neil Bothwick
2015-07-12 22:35                               ` Martin Vaeth
2015-07-11  5:53                     ` Martin Vaeth
2015-07-11 11:04                       ` covici
2015-07-11 20:47                         ` Martin Vaeth
2015-07-13  9:21               ` Joerg Schilling
2015-07-13  9:30                 ` Peter Humphrey
2015-07-10  6:06             ` Martin Vaeth
2015-07-10  6:18           ` Martin Vaeth
2015-07-10  8:35             ` Neil Bothwick
2015-07-10 15:31               ` Martin Vaeth
2015-07-13  9:39                 ` Joerg Schilling
2015-07-13 14:00                   ` Martin Vaeth
2015-07-13 15:03                     ` Joerg Schilling
2015-07-13  9:27             ` Joerg Schilling
2015-07-13 13:55               ` Martin Vaeth
2015-07-13 14:40                 ` Joerg Schilling
2015-07-09 12:19     ` Nikos Chantziaras
2015-07-09 12:24       ` wraeth
2015-07-09 12:37         ` Nikos Chantziaras
2015-07-09 14:46           ` wraeth
2015-07-10 11:46           ` wraeth
2015-07-11 22:21             ` walt
2015-07-09 12:41     ` walt

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=20150707174859.19487edb@a6 \
    --to=w41ter@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox