Bug 361038 - Terminal goes into no-echo mode after killing some programs with Ctrl+C
Summary: Terminal goes into no-echo mode after killing some programs with Ctrl+C
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 15.12.2
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-27 13:50 UTC by Alexander Potashev
Modified: 2020-11-22 04:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Potashev 2016-03-27 13:50:08 UTC
Killing the program "patch" in the middle of patching turns Konsole into no-echo mode.

See Steps to Reproduce below.

Reproducible: Sometimes

Steps to Reproduce:
1. Create a patch file which won't apply, e.g. /tmp/1.patch:
~~~
diff 1.cpp 2.cpp
--- 1.cpp
+++ 2.cpp
@@ -1,1 +1,1 @@
-1
+2
~~~

2. Run Konsole and run command "patch < /tmp/1.patch" (make sure 1.cpp does not exist, so that the patch does not apply).
3. When "patch" prompts for "File to patch: ", press Ctrl+C.

Actual Results:  
"Patch" exits, but Konsole is now in no-echo mode: typed in letters are not visible. But you can run programs as usual; in the example below after exiting "patch" I typed in "ls -1 | wc -l" and pressed Enter:
=====
aspotashev@cell ~ $ patch < /tmp/1.patch 
can't find file to patch at input line 4
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff 1.cpp 2.cpp
|--- 1.cpp
|+++ 2.cpp
--------------------------
File to patch: ^C
aspotashev@cell ~ $ 109
aspotashev@cell ~ $ 


Expected Results:  
Konsole should be in echo mode after "patch" exits.
Comment 1 Peter Wu 2016-05-03 11:19:36 UTC
Cannot reproduce on Arch Linux with:
Qt: 5.6.0
KDE Frameworks: 5.21.0
Konsole: 16.04.0

After ^C, input is echoed as expected.

If you are still affected, have you tried the "stty echo" command to restore echo?
Comment 2 Alexander Potashev 2016-07-14 07:24:31 UTC
Can't reproduce with "patch" at the moment, but I saw the same behaviour with nodejs today.
Comment 3 Alexander Potashev 2016-07-14 07:27:54 UTC
(In reply to Alexander Potashev from comment #2)
> Can't reproduce with "patch" at the moment, but I saw the same behaviour
> with nodejs today.

However, I've just reproduced the "patch" scenario in Yakuake.

"stty echo" helps, thanks!

Versions installed:
KDE Frameworks 5.23.0
Qt 5.6.1
Konsole 16.04.1
Yakuake KF5 from Git (built 21:56:16 21.05.2015)
Comment 4 Alexander Potashev 2016-07-14 07:45:30 UTC
Not reproducible in Yakuake 3.0.2.
Comment 5 Alexander Potashev 2016-07-14 08:53:27 UTC
Same problem again with Yakuake 3.0.2 when going a "git add -p".
Comment 6 Justin Zobel 2020-10-23 02:20:33 UTC
Alexander, can you please confirm if this is still an issue with Konsole 20.08.1+.
Comment 7 Bug Janitor Service 2020-11-07 04:33:35 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2020-11-22 04:33:50 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!