[SOLVED] Extra output feedback with PowerShell console

dougpuob

New Member
Jan 13, 2021
7
0
1
39
I launched a PowerShell (pwsh) in LXC container (Ubuntu20.4), unfortunately the console always append something at the console feedback string. It seems like ANSI escape sequence. I can't duplicate the same issue with QEMU or native machine. Is there any suggestion for this problem?

1612413357814.png

1612413410484.png

END
 
mhmm.. i tried this release https://github.com/PowerShell/PowerShell/releases/tag/v7.1.1
on my host and in a debian container (the tar.gz) and it had no problems whatsoever

maybe it is simply a 'wrong' TERM or LANG variable?

can you post the output of 'env' from within powershell?

also can you please post the output of 'pveversion -v' of your pve?
 
I also installed pwsh on Ubuntu 20.04 its works normally, maybe you need to set the language As my colleague suggested like: locale-gen "en_US.UTF-8"

DeepinScreenshot_select-area_20210204092542.png
 
mhmm.. i tried this release https://github.com/PowerShell/PowerShell/releases/tag/v7.1.1
on my host and in a debian container (the tar.gz) and it had no problems whatsoever

maybe it is simply a 'wrong' TERM or LANG variable?

can you post the output of 'env' from within powershell?

also can you please post the output of 'pveversion -v' of your pve?

Hi @dcsapak:

Thank you for your reply. I found a weird behavior to duplicate my case.
  1. Launch pwsh
  2. Open another browser tab and focus on the same VM.
  3. Try to type something on the pwsh prompt.
It is fine with a single browser tab. I recorded a 30 seconds video to demonstrate my way. https://youtu.be/vmlmR9ANEKM

Providing detailed info for your reference.

Bash:
root@amd-r9-x3900:~# pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.73-1-pve)
pve-manager: 6.3-2 (running version: 6.3-2/22f57405)
pve-kernel-5.4: 6.3-1
pve-kernel-helper: 6.3-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-6
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.3-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.5-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-1
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-1
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1

Code:
PS /root> dir env:
Name                           Value
----                           -----
_                              /usr/bin/pwsh
DBUS_SESSION_BUS_ADDRESS       unix:path=/run/user/0/bus
HOME                           /root
HUSHLOGIN                      FALSE
INVOCATION_ID                  c6d96455d8e64d429b2ba5561c3e8e09
JOURNAL_STREAM                 9:28938702
LANG                           C
LESSCLOSE                      /usr/bin/lesspipe %s %s
LESSOPEN                       | /usr/bin/lesspipe %s
LOGNAME                        root
LS_COLORS                      rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33…
MAIL                           /var/mail/root
MOTD_SHOWN                     pam
PATH                           /opt/microsoft/powershell/7:/usr/local/sbin:/usr/local/bin:/usr/…
PSModulePath                   /root/.local/share/powershell/Modules:/usr/local/share/powershel…
PWD                            /root
SHELL                          /bin/bash
SHLVL                          1
TERM                           linux
USER                           root
XDG_RUNTIME_DIR                /run/user/0
XDG_SESSION_CLASS              user
XDG_SESSION_ID                 867
XDG_SESSION_TYPE               tty
 
ok i can reproduce it, but it has nothing to do with xtermjs

for containers we start the tty in a dtach session, and it seems that either powershell cannot handle that, or dtach has a bug (which seems unlikely since it does work for every other shell?)

you can test it by creating a dtach session e.g. via ssh and connect twice to it

as a workaround you could start a screen/tmux session inside, which then will work

i am not really sure this is a bug with us, but suspect it might be a bug in powershell, since i can bring it to crash by using novnc or using

dtach -c /tmp/test -r none pwsh
 
Hi @dcsapak :
Thank you help me understand what is going on with this issue. Now I can work with pwsh in tmux, thank you for your solution.

And I can duplicate the crash with dtach too. Anyway, your help is great and the PVE is awesome.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!