When vdeterm fails at start (such as happens when specifying the wrong vde socket), then it does not restore the terminal.
The terminal is thus left in noecho mode.
# lsb_release -rd Description: Ubuntu 10.04.2 LTS Release: 10.04
# apt-cache policy vde2 vde2: Installed: 2.2.3-3 Candidate: 2.2.3-3 Version table: *** 2.2.3-3 0 500 http://fr.archive.ubuntu.com/ubuntu/ lucid/universe Packages 100 /var/lib/dpkg/status
What do I expect: on error, vdeterm should restore the terminal into the state where it found it in
What happens instead: the terminal is left with noecho (... and possibly other settings wrong as well...)
When vdeterm fails at start (such as happens when specifying the wrong vde socket), then it does not restore the terminal.
The terminal is thus left in noecho mode.
# lsb_release -rd
Description: Ubuntu 10.04.2 LTS
Release: 10.04
# apt-cache policy vde2 fr.archive. ubuntu. com/ubuntu/ lucid/universe Packages dpkg/status
vde2:
Installed: 2.2.3-3
Candidate: 2.2.3-3
Version table:
*** 2.2.3-3 0
500 http://
100 /var/lib/
What do I expect:
on error, vdeterm should restore the terminal into the state where it found it in
What happens instead:
the terminal is left with noecho (... and possibly other settings wrong as well...)