How to get PrintScreen or FreeRDP working in thinstation 5?

Question

linux

Good afternoon.
Faced such a problem. I took a ready-made build of thinstation 5.4 and put users on thin clients. As it turned out, the PrintScreen key does not work. Many forums write that it is better to use freerdp. But for some reason freerdp doesn't start, and everything is ok on rdesktop, except for the printscreen. Does anyone know how to run freerdp?
thinstation.conf.network

SESSION_0_TITLE="terminal"
SESSION_0_TYPE=freerdp
SESSION_0_SCREEN=1
SESSION_0_SCREEN_POSITION=2
SESSION_0_FREERDP_SERVER=ipадрес
SESSION_0_AUTOSTART=On

FREERDP_OPTIONS=--no-tls
FREERDP_USB_NO_MOUNT_DIR=On # Mount USB Drive On/Off
FREERDP_USB=Off # Mount USB Drive On/Off
FREERDP_SOUND=On # Audio, On/Off
FREERDP_AUDIO_IN=On
FREERDP_KEYMAP=409 # Keymap number
FREERDP_CONSOLE=Off # Conect to console, On/Off
FREERDP_SLOWLINK=Off # Slow Network Link, On/Off
FREERDP_COMPRESSION=Off # RDP Compression, On/Off
FREERDP_CDROM=Off # CDROM Drive present, On/Off
FREERDP_CDROM_SATA=Off # SATA CDROM present, On/Off
FREERDP_FDD=Off # Floppy Drive present, On/Off
FREERDP_USBFDD=Off # USB Floppy present, On/Off
FREERDP_HDD=Off # HDD Drive present, On/Off
FREERDP_1394=Off # FireWare HDD present, On/Off
FREERDP_COM3=Off # Redirect COM1, On/Off
FREERDP_COM4=Off # Redirect COM2, On/Off

KEYBOARD_MAP=en_us
TIME_ZONE="Europe/Moscow"
USB_ENABLED=On
RDESKTOP_USB_NO_MOUNT_DIR=On
USB_MOUNT_USELABEL=On
AUDIO_LEVEL=67
MIC_LEVEL=100
AUTOPLAYCD=Off
DAILY_REBOOT=On
CUSTOM_CONFIG=off
RECONNECT_PROMPT=On
NET_HOSTNAME=host
NET_TELNETD_ENABLED=On
VIA_UNI_DRV=On
SCREEN_RESOLUTION="1280x1024"
SCREEN_HORIZSYNC="30-65"
SCREEN_VERTREFRESH="60"
SCREEN_COLOR_DEPTH="24"
MOUSE_PROTOCOL=IMPS/2
MOUSE_RESOLUTION=100
MOUSE_ACCELERATION="1"
X_DRIVER_OPTION1="swcursor On"
PRINTER_0_NAME=parallel
PRINTER_0_DEVICE=/dev/printers/0
PRINTER_0_TYPE=P
PRINTER_1_NAME=usb
PRINTER_1_DEVICE=/dev/usb/lp0
PRINTER_1_TYPE=U

Answer 1

You need to connect to the thin client and see what parameters freerdp starts with, most likely, when generating the startup string, the script substitutes some parameters incorrectly