0.5.29 (introduced Dec 12), 0.5.28 (introduced Nov 18) and 0.5.27 (introduced Nov 5) are all broken which makes me believe that a change in the platform introduced this bug.
To install an older click as phablet user:
$ click list
...
com.ubuntu.terminal 0.5.29
...
After launching the terminal app, I verified that the correct version was running:
$ sudo aa-status
com.ubuntu.terminal_terminal_0.5.28
com.ubuntu.terminal_terminal_0.5.29
...
com.ubuntu.terminal_terminal_0.5.28 (18108)
com.ubuntu.terminal_terminal_0.5.28 (18132)
(the last two indicate that PIDs 18108 and 18132 are running under the com.ubuntu.terminal_terminal_0.5.28 profile, which can only happen with the 0.5.28 app).
It was believed that the bug was introduced in the latest terminal app. Older versions of the app can be found here: people. canonical. com/~ubuntu- archive/ click_packages/
http://
0.5.29 (introduced Dec 12), 0.5.28 (introduced Nov 18) and 0.5.27 (introduced Nov 5) are all broken which makes me believe that a change in the platform introduced this bug.
To install an older click as phablet user:
$ click list
...
com.ubuntu.terminal 0.5.29
...
$ pkcon install-local /tmp/com. ubuntu. terminal_ 0.5.28_ armhf.click
$ click list
...
com.ubuntu.terminal 0.5.28
...
After launching the terminal app, I verified that the correct version was running: ubuntu. terminal_ terminal_ 0.5.28 ubuntu. terminal_ terminal_ 0.5.29 ubuntu. terminal_ terminal_ 0.5.28 (18108) ubuntu. terminal_ terminal_ 0.5.28 (18132)
$ sudo aa-status
com.
com.
...
com.
com.
(the last two indicate that PIDs 18108 and 18132 are running under the com.ubuntu. terminal_ terminal_ 0.5.28 profile, which can only happen with the 0.5.28 app).