Re: [gentoo-user] Re: Shell echo missing after ctrl+c

[Neil Bothwick]

On Sun, 19 Mar 2017 16:37:50 +, Peter Humphrey wrote:

> > > I'm using plasma and I don't have any problem with CTRL-C. Well,
> > > unless I'm interrupting something so deeply nested in the call
> > > stack that there's no way back out all the way to the command line,
> > > as happens sometimes when emerging -j . Then I have to kill
> > > Konsole and start it again.  
> > 
> > kill -9 works for me in that situation.  
> 
> Yes, that's what I meant. Sometimes I can pick out the process holding 
> things up, other times I can't reliably and kill the konsole containing
> it, preferring not to resort to guesswork with such a sharp knife.  :8

pgrep --full --list-full emerge

works for emerge processes. So far, I haven't killed the wrong process...
so far.


-- 
Neil Bothwick

Theory is when you know everything, but nothing works.
Reality is when everything works, but you don't know why.
However, usually theory and reality are mixed together :
Nothing works, and nobody knows why not.


pgpDde5octlvk.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Re: Shell echo missing after ctrl+c

[Peter Humphrey]

On Sunday 19 Mar 2017 16:23:34 Neil Bothwick wrote:
> On Sun, 19 Mar 2017 14:50:14 +, Peter Humphrey wrote:
> > I'm using plasma and I don't have any problem with CTRL-C. Well, unless
> > I'm interrupting something so deeply nested in the call stack that
> > there's no way back out all the way to the command line, as happens
> > sometimes when emerging -j . Then I have to kill Konsole and
> > start it again.
> 
> kill -9 works for me in that situation.

Yes, that's what I meant. Sometimes I can pick out the process holding 
things up, other times I can't reliably and kill the konsole containing it, 
preferring not to resort to guesswork with such a sharp knife.  :8

> I also don't see the behaviour described by the others.

-- 
Regards
Peter

Re: [gentoo-user] Re: Shell echo missing after ctrl+c

[Neil Bothwick]

On Sun, 19 Mar 2017 14:50:14 +, Peter Humphrey wrote:

> I'm using plasma and I don't have any problem with CTRL-C. Well, unless
> I'm interrupting something so deeply nested in the call stack that
> there's no way back out all the way to the command line, as happens
> sometimes when emerging -j . Then I have to kill Konsole and
> start it again.

kill -9 works for me in that situation.

I also don't see the behaviour described by the others.


-- 
Neil Bothwick

Get your grubby hands off my tagline! I stole it first!


pgp14D_Y_Uug_.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Re: Shell echo missing after ctrl+c

[Peter Humphrey]

On Sunday 19 Mar 2017 10:59:45 Mick wrote:

> Not sure this will help, but none of my systems have this problem.  urxvt,
> xterm, konsole, terminology, all display anything I enter in the keyboard
> after I have pressed Ctrl+c.  I run enlightenment, or fluxbox, I have not
> tried with the plasma DE yet.

I'm using plasma and I don't have any problem with CTRL-C. Well, unless I'm 
interrupting something so deeply nested in the call stack that there's no 
way back out all the way to the command line, as happens sometimes when
emerging -j . Then I have to kill Konsole and start it again.

-- 
Regards
Peter

Re: [gentoo-user] Re: Shell echo missing after ctrl+c

[Dale]

Kai Krakow wrote:
> Am Sun, 19 Mar 2017 06:27:15 -0500
> schrieb Dale :
>
>
>
> Here is mine:
>
> root@fireball / # uname -r
> 4.5.2-gentoo
> root@fireball / #
>
> As far as I know, I use bash.  If you are talking about what I think
> you are talking about. 
> Yes, that's what I was talking about.
>
> Run ps, it should tell you the processes running in your current shell,
> including the shell itself:
>
> # ps
>   PID TTY  TIME CMD
>  1256 pts/200:00:00 ps
> 32059 pts/200:00:00 bash
>
> And you can see your default shell this way:
>
> # realpath /bin/sh
> /bin/dash
>
> Yes, dash for me, because it spawns much faster than bash, at least
> when running scripts. This can make a big difference with openrc.
> Meanwhile, I'm using systemd.

root@fireball / # ps | grep bash
 8515 pts/000:00:00 bash
root@fireball / # realpath /bin/sh
/bin/bash
root@fireball / #

Looks like bash for me. 


>> [IP-] [  ] app-shells/bash-4.3_p48-r1:0
> Here, too:
>
> # equery list bash
> [IP-] [  ] app-shells/bash-4.3_p48-r1:0
>
>> Given the age of your kernel, maybe it is above that level anyway.  I
>> don't update my kernel often either. 
>>
>> I'm going to be watching this thread tho.  If I can share info which
>> may help narrow things down, I'll do that for sure. 
> The problem is that this bug is totally non-deterministic... It fails
> once, next try it works as it should.
>
> If you can work out a way to reliably reproduce this bug, let me know.
> Then I'll try to work out what the problem is. 
>


I think our other Alan posted a way to reproduce it.  I see you replied
so maybe his post will help and I'll read your reply next.  Maybe if we
share enough between several of us, we can at least rule out some stuff
and narrow it down a bit. 

Dale

:-)  :-) 

Re: [gentoo-user] Re: Shell echo missing after ctrl+c

[Dale]

Mick wrote:
> On Sunday 19 Mar 2017 05:40:09 Dale wrote:
>>
>> I've likely had it happen on a regular console too.  I have just got so
>> used to it, I don't pay it any attention.  I suspect this is a deep
>> issue somewhere.  Maybe even as low level as the kernel somehow or close
>> to it.
>>
>> It will be interesting to see what it is tho.  Given how long it has
>> been doing it here at least, it's going to be a old commit/change which
>> may be difficult to track back.
>>
>> Dale
>>
>> :-)  :-)
> Not sure this will help, but none of my systems have this problem.  urxvt, 
> xterm, konsole, terminology, all display anything I enter in the keyboard 
> after I have pressed Ctrl+c.  I run enlightenment, or fluxbox, I have not 
> tried with the plasma DE yet.

Be interesting to see what happens when you try that.  I have KDE for my
main desktop.  I do have others, Fluxbox etc, for backup usage tho. 

If we keep posting what we use and what is affected, or not, maybe we
can find something common that points to the problem.  Maybe.

Dale

:-)  :-) 

Re: [gentoo-user] Re: Shell echo missing after ctrl+c

[Dale]

Kai Krakow wrote:
> Am Sun, 19 Mar 2017 05:40:09 -0500
> schrieb Dale :
>
>> Kai Krakow wrote:
>>> Am Sun, 19 Mar 2017 04:12:38 -0500
>>> schrieb Dale :
>>>  
 Kai Krakow wrote:  
>>  [...]  
 I don't have a solution but wanted to reply to say that this
 happens to me too.  I have a regular desktop running KDE.  I use
 Konsole for most of my command line activity.  I've noticed that
 this happens with a lot of programs.  It has been happening so
 long, I thought maybe it was the new way things are done.  It is
 aggravating and confusing at times. 

 You are not alone on this.  I'm hoping someone will post a fix.   
>>> KDE with konsole here, too... But I don't think that's the common
>>> denominator. It's also happening from PuTTY in Windows.
>>>  
>> I've likely had it happen on a regular console too.  I have just got
>> so used to it, I don't pay it any attention.  I suspect this is a deep
>> issue somewhere.  Maybe even as low level as the kernel somehow or
>> close to it. 
>>
>> It will be interesting to see what it is tho.  Given how long it has
>> been doing it here at least, it's going to be a old commit/change
>> which may be difficult to track back.
> Well, I shouldn't say that probably, but some affected servers are
> still running on 3.0 or 3.2 kernels. Only the rest of the system was
> upgraded (mostly "glsa-check -f affected" only). So, I suspected an
> issue because of old kernel but new user space tools.
>
> But since some time ago my desktop machines are also affected (and those
> are almost bleeding edge, with ~amd64 gentoo-sources).
>
> So, more likely it's something in bash... Which is what I use. Which
> shell do you use? I could try using zsh tho I absolutely hate how it
> tries to be smarter about tab-completion and always steals trailing "/"
> away - which especially with rsync and mv can do some serious damage or
> at least unexpected results.
>


Here is mine:

root@fireball / # uname -r
4.5.2-gentoo
root@fireball / #

As far as I know, I use bash.  If you are talking about what I think you
are talking about. 

[IP-] [  ] app-shells/bash-4.3_p48-r1:0

Given the age of your kernel, maybe it is above that level anyway.  I
don't update my kernel often either. 

I'm going to be watching this thread tho.  If I can share info which may
help narrow things down, I'll do that for sure. 

Dale

:-)  :-) 

Re: [gentoo-user] Re: Shell echo missing after ctrl+c

[Mick]

On Sunday 19 Mar 2017 05:40:09 Dale wrote:
> Kai Krakow wrote:
> > Am Sun, 19 Mar 2017 04:12:38 -0500
> > 
> > schrieb Dale :
> >> Kai Krakow wrote:
> >>> Hello!
> >>> 
> >>> More and more of my Gentoo systems are exhibiting the following
> >>> strange and unexpected behavior:
> >>> 
> >>> After ctrl+c'ing out of programs like tailf, SSH password prompts,
> >>> in the middle of a shell scripts, the shell echo is not restored -
> >>> that is: If I type characters I no longer see the characters (but
> >>> they are received and can be executed by "enter"). If experiencing
> >>> this, I have to ctrl+c again to discard what I was typing, the
> >>> blindly type "reset" to reset the terminal, then echo is enabled
> >>> again.
> >>> 
> >>> I'm not sure which update or configuration is causing this. It
> >>> started out on our Gentoo servers some years ago (which I'm only
> >>> SSH'ed into, no physical access), now since a few weeks, also my
> >>> desktop machines are affected. I have no explanation for this.
> >>> 
> >>> But maybe anyone?
> >>> 
> >>> BTW: I know from the old times (some 15-20 years ago) that ctrl+c
> >>> out of a program (i.e. rsync) that starts a subshell (i.e. ssh)
> >>> that in turn shows a password prompt, will leave you with an
> >>> echoless shell. But it shows up on almost any occasion now.
> >> 
> >> I don't have a solution but wanted to reply to say that this happens
> >> to me too.  I have a regular desktop running KDE.  I use Konsole for
> >> most of my command line activity.  I've noticed that this happens
> >> with a lot of programs.  It has been happening so long, I thought
> >> maybe it was the new way things are done.  It is aggravating and
> >> confusing at times.
> >> 
> >> You are not alone on this.  I'm hoping someone will post a fix.
> > 
> > KDE with konsole here, too... But I don't think that's the common
> > denominator. It's also happening from PuTTY in Windows.
> 
> I've likely had it happen on a regular console too.  I have just got so
> used to it, I don't pay it any attention.  I suspect this is a deep
> issue somewhere.  Maybe even as low level as the kernel somehow or close
> to it.
> 
> It will be interesting to see what it is tho.  Given how long it has
> been doing it here at least, it's going to be a old commit/change which
> may be difficult to track back.
> 
> Dale
> 
> :-)  :-)

Not sure this will help, but none of my systems have this problem.  urxvt, 
xterm, konsole, terminology, all display anything I enter in the keyboard 
after I have pressed Ctrl+c.  I run enlightenment, or fluxbox, I have not 
tried with the plasma DE yet.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Re: Shell echo missing after ctrl+c

[Dale]

Kai Krakow wrote:
> Am Sun, 19 Mar 2017 04:12:38 -0500
> schrieb Dale :
>
>> Kai Krakow wrote:
>>> Hello!
>>>
>>> More and more of my Gentoo systems are exhibiting the following
>>> strange and unexpected behavior:
>>>
>>> After ctrl+c'ing out of programs like tailf, SSH password prompts,
>>> in the middle of a shell scripts, the shell echo is not restored -
>>> that is: If I type characters I no longer see the characters (but
>>> they are received and can be executed by "enter"). If experiencing
>>> this, I have to ctrl+c again to discard what I was typing, the
>>> blindly type "reset" to reset the terminal, then echo is enabled
>>> again.
>>>
>>> I'm not sure which update or configuration is causing this. It
>>> started out on our Gentoo servers some years ago (which I'm only
>>> SSH'ed into, no physical access), now since a few weeks, also my
>>> desktop machines are affected. I have no explanation for this.
>>>
>>> But maybe anyone?
>>>
>>> BTW: I know from the old times (some 15-20 years ago) that ctrl+c
>>> out of a program (i.e. rsync) that starts a subshell (i.e. ssh)
>>> that in turn shows a password prompt, will leave you with an
>>> echoless shell. But it shows up on almost any occasion now.
>>>  
>> I don't have a solution but wanted to reply to say that this happens
>> to me too.  I have a regular desktop running KDE.  I use Konsole for
>> most of my command line activity.  I've noticed that this happens
>> with a lot of programs.  It has been happening so long, I thought
>> maybe it was the new way things are done.  It is aggravating and
>> confusing at times. 
>>
>> You are not alone on this.  I'm hoping someone will post a fix. 
> KDE with konsole here, too... But I don't think that's the common
> denominator. It's also happening from PuTTY in Windows.
>

I've likely had it happen on a regular console too.  I have just got so
used to it, I don't pay it any attention.  I suspect this is a deep
issue somewhere.  Maybe even as low level as the kernel somehow or close
to it. 

It will be interesting to see what it is tho.  Given how long it has
been doing it here at least, it's going to be a old commit/change which
may be difficult to track back. 

Dale

:-)  :-)