| 2018-05-03 10:21:26 |
Daniel Axtens |
bug |
|
|
added bug |
| 2018-05-25 18:42:37 |
Mathieu Trudel-Lapierre |
netplan.io (Ubuntu): status |
New |
In Progress |
|
| 2018-05-25 18:42:39 |
Mathieu Trudel-Lapierre |
netplan.io (Ubuntu): importance |
Undecided |
High |
|
| 2018-05-25 18:42:41 |
Mathieu Trudel-Lapierre |
netplan.io (Ubuntu): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2018-06-29 15:19:33 |
Launchpad Janitor |
netplan.io (Ubuntu): status |
In Progress |
Fix Released |
|
| 2018-09-27 20:55:03 |
Mathieu Trudel-Lapierre |
description |
If I do netplan try, press ^C during the wait, and try to type, my characters are not echoed to the terminal.
(This is similar to what powersj found in https://asciinema.org/a/176782 but different in that instead of Enter it's ^C that triggers it.)
I think you'll need to trap KeyboardInterrupt exceptions and reset afterwards? or use a try/finally construct to make sure things are reset? |
[Impact]
All netplan users.
[Test case]
1) Run 'sudo netplan try' to "try" a new netplan config.
2) Hit Control-C during the timer, to escape to the terminal without applying the configuration.
Validate that text typed on the terminal after hitting Control-C is correctly echoed on screen.
[Regression Potential]
Some non-standard shells may behave differently with the console and expect a specific set of modes. Care has been taken to correctly record and restore the original terminal modes and flags, as well as testing on bash, dash, zsh, in a text VT, etc; but it is possible for non-standard terminals to misunderstand the mode changes and thus incorrectly handle Control-C or other mode changes required by 'netplan try' leading to failure to echo characters, mishandling carriage returns, clears, or invalid color schemes on terminal.
--
If I do netplan try, press ^C during the wait, and try to type, my characters are not echoed to the terminal.
(This is similar to what powersj found in https://asciinema.org/a/176782 but different in that instead of Enter it's ^C that triggers it.)
I think you'll need to trap KeyboardInterrupt exceptions and reset afterwards? or use a try/finally construct to make sure things are reset? |
|
| 2018-09-28 00:02:03 |
Mathieu Trudel-Lapierre |
netplan.io (Ubuntu): assignee |
Mathieu Trudel-Lapierre (cyphermox) |
|
|
| 2018-09-28 16:34:55 |
Łukasz Zemczak |
netplan.io (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2018-09-28 16:34:56 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-09-28 16:34:58 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2018-09-28 16:35:00 |
Łukasz Zemczak |
tags |
|
verification-needed verification-needed-bionic |
|
| 2018-10-09 16:53:03 |
Mathieu Trudel-Lapierre |
tags |
verification-needed verification-needed-bionic |
verification-done-bionic |
|
| 2018-10-23 22:00:41 |
Brian Murray |
tags |
verification-done-bionic |
verification-needed verification-needed-bionic |
|
| 2018-10-29 15:50:50 |
Mathieu Trudel-Lapierre |
tags |
verification-needed verification-needed-bionic |
verification-done-bionic |
|
| 2018-11-06 18:13:46 |
Launchpad Janitor |
netplan.io (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2018-11-06 18:15:00 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2018-11-08 17:06:04 |
Steve Langasek |
netplan.io (Ubuntu Bionic): status |
Fix Released |
Fix Committed |
|
| 2018-11-26 19:24:23 |
Adam Conrad |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-11-26 19:24:27 |
Adam Conrad |
tags |
verification-done-bionic |
verification-needed verification-needed-bionic |
|
| 2018-12-04 15:53:45 |
Mathieu Trudel-Lapierre |
tags |
verification-needed verification-needed-bionic |
verification-done-bionic |
|
| 2018-12-05 18:47:48 |
Launchpad Janitor |
netplan.io (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
