Session not closing after closing an app

[RuiFPB]

After opening an app (say Word) and closing it, the freerdp session continues running in the background.

The session does not close automatically and, if the process is killed, windows never logs out the user. When opening the same app again, or any other app, it launches the process inside windows, but never creates an window on the desktop. Every time I have to open a new RDP session to the windows desktop, logout the bugged session and open the apps again.

---

Two user sessions on Windows:

Word and Powerpoint open on the user, but not shown on the desktop:

Winapps.conf:

##################################
#   WINAPPS CONFIGURATION FILE   #
##################################

# INSTRUCTIONS
# - Leading and trailing whitespace are ignored.
# - Empty lines are ignored.
# - Lines starting with '#' are ignored.
# - All characters following a '#' are ignored.

# [WINDOWS USERNAME]
RDP_USER="Docker"

# [WINDOWS PASSWORD]
RDP_PASS="********"

# [WINDOWS DOMAIN]
# DEFAULT VALUE: '' (BLANK)
RDP_DOMAIN=""

# [WINDOWS IPV4 ADDRESS]
# NOTES:
# - If using 'libvirt', 'RDP_IP' will be determined by WinApps at runtime if left unspecified.
# DEFAULT VALUE:
# - 'docker': '127.0.0.1'
# - 'podman': '127.0.0.1'
# - 'libvirt': '' (BLANK)
RDP_IP="127.0.0.1"

# [WINAPPS BACKEND]
# DEFAULT VALUE: 'docker'
# VALID VALUES:
# - 'docker'
# - 'podman'
# - 'libvirt'
# - 'manual'
WAFLAVOR="docker"

# [DISPLAY SCALING FACTOR]
# NOTES:
# - If an unsupported value is specified, a warning will be displayed.
# - If an unsupported value is specified, WinApps will use the closest supported value.
# DEFAULT VALUE: '100'
# VALID VALUES:
# - '100'
# - '140'
# - '180'
RDP_SCALE="180"

# [ADDITIONAL FREERDP FLAGS & ARGUMENTS]
# DEFAULT VALUE: '/cert:tofu /sound /microphone'
# VALID VALUES: See https://github.com/awakecoding/FreeRDP-Manuals/blob/master/User/FreeRDP-User-Manual.markdown
RDP_FLAGS="/cert:tofu /sound /microphone /kbd:layout:0x00000816"

# [MULTIPLE MONITORS]
# NOTES:
# - If enabled, a FreeRDP bug *might* produce a black screen.
# DEFAULT VALUE: 'false'
# VALID VALUES:
# - 'true'
# - 'false'
MULTIMON="false"

# [DEBUG WINAPPS]
# NOTES:
# - Creates and appends to ~/.local/share/winapps/winapps.log when running WinApps.
# DEFAULT VALUE: 'true'
# VALID VALUES:
# - 'true'
# - 'false'
DEBUG="true"

# [AUTOMATICALLY PAUSE WINDOWS]
# NOTES:
# - This is currently INCOMPATIBLE with 'docker' and 'manual'.
# - See https://github.com/dockur/windows/issues/674
# DEFAULT VALUE: 'off'
# VALID VALUES:
# - 'on'
# - 'off'
AUTOPAUSE="off"

# [AUTOMATICALLY PAUSE WINDOWS TIMEOUT]
# NOTES:
# - This setting determines the duration of inactivity to tolerate before Windows is automatically paused.
# - This setting is ignored if 'AUTOPAUSE' is set to 'off'.
# - The value must be specified in seconds (to the nearest 10 seconds e.g., '30', '40', '50', etc.).
# - For RemoteApp RDP sessions, there is a mandatory 20-second delay, so the minimum value that can be specified here is '20'.
# - Source: https://techcommunity.microsoft.com/t5/security-compliance-and-identity/terminal-services-remoteapp-8482-session-termination-logic/ba-p/246566
# DEFAULT VALUE: '300'
# VALID VALUES: >=20
AUTOPAUSE_TIME="300"

# [FREERDP COMMAND]
# NOTES:
# - WinApps will attempt to automatically detect the correct command to use for your system.
# DEFAULT VALUE: '' (BLANK)
# VALID VALUES: The command required to run FreeRDPv3 on your system (e.g., 'xfreerdp', 'xfreerdp3', etc.).
FREERDP_COMMAND=""

Latest logs:

[qua 20 nov 2024 17:22:33 WET-5080] START
[qua 20 nov 2024 17:22:33 WET-5080] SCRIPT_DIR: /home/ruifpb/.local/bin
[qua 20 nov 2024 17:22:33 WET-5080] SCRIPT_ARGS: word-o365
[qua 20 nov 2024 17:22:33 WET-5080] HOME_DIR: /home/ruifpb
[qua 20 nov 2024 17:22:33 WET-5080] LAST_RUN: 1732120202
[qua 20 nov 2024 17:22:33 WET-5080] THIS_RUN: 1732123353
[qua 20 nov 2024 17:22:33 WET-5080] Using FreeRDP command 'xfreerdp'.
[qua 20 nov 2024 17:22:33 WET-5080] END
[qua 20 nov 2024 17:23:37 WET-14924] START
[qua 20 nov 2024 17:23:37 WET-14924] SCRIPT_DIR: /home/ruifpb/.local/bin
[qua 20 nov 2024 17:23:37 WET-14924] SCRIPT_ARGS: word-o365
[qua 20 nov 2024 17:23:37 WET-14924] HOME_DIR: /home/ruifpb
[qua 20 nov 2024 17:23:37 WET-14924] LAST_RUN: 1732123353
[qua 20 nov 2024 17:23:37 WET-14924] THIS_RUN: 1732123417
[qua 20 nov 2024 17:23:37 WET-14924] Using FreeRDP command 'xfreerdp'.
[qua 20 nov 2024 17:23:37 WET-14924] END
[qua 20 nov 2024 17:24:50 WET-25785] START
[qua 20 nov 2024 17:24:50 WET-25785] SCRIPT_DIR: /home/ruifpb/.local/bin
[qua 20 nov 2024 17:24:50 WET-25785] SCRIPT_ARGS: windows
[qua 20 nov 2024 17:24:50 WET-25785] HOME_DIR: /home/ruifpb
[qua 20 nov 2024 17:24:50 WET-25785] LAST_RUN: 1732123417
[qua 20 nov 2024 17:24:50 WET-25785] THIS_RUN: 1732123490
[qua 20 nov 2024 17:24:50 WET-25785] Using FreeRDP command 'xfreerdp'.
[qua 20 nov 2024 17:24:50 WET-25785] WINDOWS
[qua 20 nov 2024 17:24:50 WET-25785] END
[qua 20 nov 2024 17:25:45 WET-26828] START
[qua 20 nov 2024 17:25:45 WET-26828] SCRIPT_DIR: /home/ruifpb/.local/bin
[qua 20 nov 2024 17:25:45 WET-26828] SCRIPT_ARGS: windows
[qua 20 nov 2024 17:25:45 WET-26828] HOME_DIR: /home/ruifpb
[qua 20 nov 2024 17:25:45 WET-26828] LAST_RUN: 1732123490
[qua 20 nov 2024 17:25:45 WET-26828] THIS_RUN: 1732123545
[qua 20 nov 2024 17:25:45 WET-26828] Using FreeRDP command 'xfreerdp'.
[qua 20 nov 2024 17:25:45 WET-26828] WINDOWS
[qua 20 nov 2024 17:28:03 WET-1374] START
[qua 20 nov 2024 17:28:03 WET-1374] SCRIPT_DIR: /home/ruifpb/.local/bin
[qua 20 nov 2024 17:28:03 WET-1374] SCRIPT_ARGS: powerpoint-o365
[qua 20 nov 2024 17:28:03 WET-1374] HOME_DIR: /home/ruifpb
[qua 20 nov 2024 17:28:03 WET-1374] LAST_RUN: 1732123545
[qua 20 nov 2024 17:28:03 WET-1374] THIS_RUN: 1732123683
[qua 20 nov 2024 17:28:03 WET-1374] Using FreeRDP command 'xfreerdp'.
[qua 20 nov 2024 17:28:03 WET-1374] END
[qua 20 nov 2024 17:25:45 WET-26828] END

WinApps Backend: Docker
Windows Version: Windows 11 IoT Enterprise LTSC (Tiny11)
Host OS: Fedora 41 - KDE Spin

[Boyfinn]

I'm having the same concern. Spinning up the container hardly takes over 5-seconds, so it doesn't make sense for me to run it in the background whenever it's not in use.

[AkechiShiro]

May be related to #297 @KernelGhost what do you think ?