Auto login crash

[kabakadev]

What happened?

setup.sh consistently fails the initial FreeRDP connection test (ERROR: REMOTE DESKTOP PROTOCOL FAILURE, exit status 14), even after resolving every other known cause (flatpak sandbox permissions, drive redirection, RDPWrap install/config, credentials, timeouts). The failure is not a connection or timeout problem — FreeRDP connects successfully and loads all channels every time, but the session is ended by Windows itself roughly 2 minutes later via ERRINFO_LOGOFF_BY_USER, regardless of RDP_TIMEOUT value (tested at 30s, 120s, 240s — timing to disconnect was ~2:05–2:25 in all cases, unaffected by the timeout setting).

Windows Event Viewer (TerminalServices-LocalSessionManager/Operational) shows Event ID 42 ("End session arbitration") at the moment of disconnect, naming the RDP session as the one terminated.

Checking Task Manager → Users during a live test confirms two simultaneous sessions exist for the same account — one console session and one RDP session — which Windows arbitrates between, eventually killing the RDP session.

Root cause identified

The dockur/windows container appears to actively log into a console session tied to RDP connection activity, independent of whether the web VNC viewer (:8006) is ever opened. This matches the behavior reported by @CrazyWolf13 in #719 ("I noticed, the docker container seems to be doing autologin, even if I don't access the web-qemu?"), but I was able to isolate it further:

• Disabling AutoAdminLogon directly in the Windows registry (HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon) did not stop the behavior. The VNC console correctly showed a plain, nobody-logged-in login screen after reboot.
• Despite that, the moment setup.sh (or a manual FreeRDP RemoteApp-mode connection) attempted to connect, the console still logged in automatically, producing the same two-session conflict.

This suggests the autologin is not driven by Windows' native Winlogon autologin mechanism at all, but by something in the dockur/windows container's own supervisor/init scripts reacting to incoming RDP activity — independent of the registry setting that normally controls this.

What does NOT reproduce the bug

A full, manually-invoked FreeRDP session (not RemoteApp mode) works perfectly and indefinitely, with working drive redirection (\\tsclient\home):

flatpak run com.freerdp.FreeRDP /v:127.0.0.1:3389 /u:redacted /p:redacted_pass /cert:tofu +home-drive

The bug only manifests when FreeRDP is invoked in RemoteApp mode (/app:program:...), which is what setup.sh's connection test and application-scan steps rely on.

Environment

• Host: Pop!_OS 22.04 LTS (Ubuntu 22.04 "jammy" base)
• Backend: Docker (dockur/windows)
• Windows version: 11 Pro, build 10.0.22621.2070
• FreeRDP: 3.30.0, native binary at /usr/local/bin/xfreerdp3 (also reproduced via the Flathub flatpak build, com.freerdp.FreeRDP, with identical results — see notes on flatpak sandbox permissions below)
• RDPWrap: v1.7.4.0, rdpwrap.ini updated via sebaxakerhtc's maintained fork — confirmed [fully supported] for this exact build
• winapps.conf: RDP_USER/RDP_PASS match compose.yaml's USERNAME/PASSWORD exactly (verified via whoami/net user inside the VM); FREERDP_COMMAND="xfreerdp3" explicitly set

Steps to reproduce

1. Set up dockur/windows via Docker per WinApps' docs/docker.md guide, Windows 11 Pro.
2. Install RDPWrap inside the VM, update rdpwrap.ini to a build-matching version, confirm [fully supported].
3. Run ./setup.sh --user.
4. Observe the connection test fail after ~2 minutes with ERRINFO_LOGOFF_BY_USER, despite a fully valid, working RDP setup (confirmed independently via manual full-session connection).

Tested the community's known fix (type NUL / RAIL window visibility) — does not resolve this case

Issue #719 identified a separate, legitimate bug: type NUL > file never opens a visible window in RAIL/RemoteApp mode, which a FreeRDP developer confirmed breaks RAIL session tracking. The suggested fix was to use a command that does open a visible window, e.g. dir instead of type NUL.

I tested this directly:

xfreerdp3 /cert:tofu /d:"" /u:"redacted" /p:"redacted_pass" /scale:"100" +home-drive +auto-reconnect /app:program:"C:\Windows\System32\cmd.exe",cmd:"/C dir && tsdiscon" /v:"127.0.0.1"

Result: identical failure. Connects, loads all channels (including home drive), then disconnects via ERRINFO_LOGOFF_BY_USER after ~2:35 — same as every other test today, regardless of RDP_TIMEOUT, FreeRDP build, or command used.

This confirms the RAIL-window-visibility bug is a separate, legitimate issue from what I'm hitting — my case is specifically the dockur console-autologin/session-arbitration behavior described above, which persists independent of whether the RemoteApp command produces a visible window.

Confirmed: reproduces identically with native FreeRDP (not just flatpak)

To rule out flatpak sandboxing as a contributing factor, I set FREERDP_COMMAND="xfreerdp3" in winapps.conf to use the native binary (v3.30.0, installed manually to /usr/local/bin/xfreerdp3, not via apt) instead of the Flathub flatpak build, and re-ran ./setup.sh --user.

Result: identical failure. Connects, loads all channels (including the home drive), then disconnects via ERRINFO_LOGOFF_BY_USER after ~3 minutes this time (vs. ~2:05–2:25 with the flatpak build) — same mechanism, same symptom, just a slightly different elapsed time. This confirms the bug is entirely server-side (Windows/dockur), not related to which FreeRDP binary or build is used on the client.

What I've already ruled out

• Flatpak sandbox permissions (fixed: X11/Wayland sockets, /tmp, --filesystem=home)
• Drive redirection (confirmed working via manual full-session test)
• RDPWrap build support (confirmed [fully supported])
• Credentials mismatch (confirmed via whoami/net user)
• RDP_TIMEOUT value (tested 30/120/240s — no effect on the ~2 min disconnect timing)
• "Single session per user" RDPWrap setting (tested both checked and unchecked — no change in outcome)
• AutoAdminLogon registry key (disabled — console correctly shows no auto-login on boot, but still logs in reactively once an RDP connection is attempted)

Question for maintainers

Is there a known workaround for suppressing dockur's console-session behavior specifically during the RemoteApp-mode connection test/app-scan steps? Or is there a recommended alternative connection-test invocation that avoids triggering it?

[+]### Your FreeRDP version and where you got it from[/+]
[+]FreeRDP: version 3.30.0 compiled from source[/+]
[+]### Your Linux distribution and version[/+]
[+]Linux distribution: Pop!_OS 22.04 LTS (based on Ubuntu 22.04 "jammy").[/+]
[+]### Your winapps.conf[/+]
[+]shell[/+] [+]~/.local/bin/winapps-src (main) » cat /etc/os-release iankabaka@pop-os[/+] [+]NAME="Pop!_OS"[/+] [+]VERSION="22.04 LTS"[/+] [+]ID=pop[/+] [+]ID_LIKE="ubuntu debian"[/+] [+]PRETTY_NAME="Pop!_OS 22.04 LTS"[/+] [+]VERSION_ID="22.04"[/+] [+]HOME_URL="https://pop.system76.com"[/+] [+]SUPPORT_URL="https://support.system76.com"[/+] [+]BUG_REPORT_URL="https://github.com/pop-os/pop/issues"[/+] [+]PRIVACY_POLICY_URL="https://system76.com/privacy"[/+] [+]VERSION_CODENAME=jammy[/+] [+]UBUNTU_CODENAME=jammy[/+] [+]LOGO=distributor-logo-pop-os[/+] [+]--------------------------------------------------------------------------------------------------------------------------------------------------------------[/+] [+]~/.local/bin/winapps-src (main) » cat ~/.config/winapps/winapps.conf iankabaka@pop-os[/+] [+]##################################[/+] [+]# 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="redactedUser" not the real user[/+] [+]# [WINDOWS PASSWORD][/+] [+]# NOTES:[/+] [+]# - If using FreeRDP v3.9.0 or greater, you *have* to set a password[/+] [+]# - RDP_ASKPASS is provided as a more secure option to RDP_PASS:[/+] [+]# - Calls an external command and uses its stdout as the password[/+] [+]# - The password is not passed on the command line to freerdp, keeping it out of logs[/+] [+]# - If specified, takes precedence over RDP_PASS[/+] [+]# - Examples to use this:[/+] [+]# - RDP_ASKPASS="~/some-custom-command"[/+] [+]# - RDP_ASKPASS="bash -c 'cat ~/.some-secret-file'"[/+] [+]# - RDP_ASKPASS="bash -c 'kwallet-query --folder winapps --read-password rdp kdewallet'"[/+] [+]#[/+] [+]RDP_PASS="redacted" #not the real password[/+] [+]RDP_ASKPASS=""[/+] [+]# [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"[/+] [+]# [RDP PORT][/+] [+]# NOTES:[/+] [+]# - For Docker and Podman, this is the host port mapped to Windows port 3389.[/+] [+]# - If you changed the host-side RDP port in compose.yaml, set this to match.[/+] [+]# DEFAULT VALUE: '3389'[/+] [+]RDP_PORT="3389"[/+] [+]# [VM NAME][/+] [+]# NOTES:[/+] [+]# - Only applicable when using 'libvirt'[/+] [+]# - The libvirt VM name must match so that WinApps can determine VM IP, start the VM, etc.[/+] [+]# DEFAULT VALUE: 'RDPWindows'[/+] [+]VM_NAME="RDPWindows"[/+] [+]# [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="100"[/+] [+]# [MOUNTING REMOVABLE PATHS FOR FILES][/+] [+]# NOTES:[/+] [+]# - By default, `udisks` (which you most likely have installed) uses /run/media for mounting removable devices.[/+] [+]# This improves compatibility with most desktop environments (DEs).[/+] [+]# ATTENTION: The Filesystem Hierarchy Standard (FHS) recommends /media instead. Verify your system's configuration.[/+] [+]# - To manually mount devices, you may optionally use /mnt.[/+] [+]# REFERENCE: https://wiki.archlinux.org/title/Udisks#Mount_to_/media[/+] [+]REMOVABLE_MEDIA="/run/media"[/+] [+]# [ADDITIONAL FREERDP FLAGS & ARGUMENTS][/+] [+]# NOTES:[/+] [+]# - You can try adding /network:lan to these flags in order to increase performance, however, some users have faced issues with this.[/+] [+]# If this does not work or if it does not work without the flag, you can try adding /nsc and /gfx.[/+] [+]# DEFAULT VALUE: '/cert:tofu /sound /microphone +home-drive'[/+] [+]# VALID VALUES: See https://github.com/awakecoding/FreeRDP-Manuals/blob/master/User/FreeRDP-User-Manual.markdown[/+] [+]RDP_FLAGS="/cert:tofu /sound /microphone +home-drive"[/+] [+]# [NON FULL WINDOWS RDP FLAGS][/+] [+]# NOTES:[/+] [+]# - Use these flags to pass specific flags to the freerdp command when you are starting a non-full RDP session (any other command than winapps windows)[/+] [+]# DEFAULT_VALUES: ''[/+] [+]# VALID_VALUES: See https://github.com/awakecoding/FreeRDP-Manuals/blob/master/User/FreeRDP-User-Manual.markdown[/+] [+]RDP_FLAGS_NON_WINDOWS=""[/+] [+]# [FULL WINDOWS RDP FLAGS][/+] [+]# NOTES:[/+] [+]# - Use these flags to pass specific flags to the freerdp command when you are starting a full RDP session (winapps windows)[/+] [+]# DEFAULT_VALUES: ''[/+] [+]# VALID_VALUES: See https://github.com/awakecoding/FreeRDP-Manuals/blob/master/User/FreeRDP-User-Manual.markdown[/+] [+]RDP_FLAGS_WINDOWS=""[/+] [+]# [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 'manual'.[/+] [+]# 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="xfreerdp3"[/+] [+]# [TIMEOUTS][/+] [+]# NOTES:[/+] [+]# - These settings control various timeout durations within the WinApps setup.[/+] [+]# - Increasing the timeouts is only necessary if the corresponding errors occur.[/+] [+]# - Ensure you have followed all the Troubleshooting Tips in the error message first.[/+] [+]# PORT CHECK[/+] [+]# - The maximum time (in seconds) to wait when checking if the RDP port on Windows is open.[/+] [+]# - Corresponding error: "NETWORK CONFIGURATION ERROR" (exit status 13).[/+] [+]# DEFAULT VALUE: '5'[/+] [+]PORT_TIMEOUT="5"[/+] [+]# RDP CONNECTION TEST[/+] [+]# - The maximum time (in seconds) to wait when testing the initial RDP connection to Windows.[/+] [+]# - Corresponding error: "REMOTE DESKTOP PROTOCOL FAILURE" (exit status 14).[/+] [+]# DEFAULT VALUE: '30'[/+] [+]RDP_TIMEOUT="240"[/+] [+]# APPLICATION SCAN[/+] [+]# - The maximum time (in seconds) to wait for the script that scans for installed applications on Windows to complete.[/+] [+]# - Corresponding error: "APPLICATION QUERY FAILURE" (exit status 15).[/+] [+]# DEFAULT VALUE: '60'[/+] [+]APP_SCAN_TIMEOUT="60"[/+] [+]# WINDOWS BOOT[/+] [+]# - The maximum time (in seconds) to wait for the Windows VM to boot if it is not running, before attempting to launch an application.[/+] [+]# DEFAULT VALUE: '120'[/+] [+]BOOT_TIMEOUT="120"[/+] [+]# FREERDP RAIL HIDEF[/+] [+]# - This option controls the value of the `hidef` option passed to the /app parameter of the FreeRDP command.[/+] [+]# - Setting this option to 'off' may resolve window misalignment issues related to maximized windows.[/+] [+]# DEFAULT VALUE: 'on'[/+] [+]HIDEF="on"[/+] [+]--------------------------------------------------------------------------------------------------------------------------------------------------------------[/+] [+]~/.local/bin/winapps-src (main) » iankabaka@pop-os[/+] [+][/+]
[+]### Logs[/+]
[+]shell[/+] [+]~/.local/bin/winapps-src (main) » ./setup.sh --user 127 ↵ iankabaka@pop-os[/+] [+]################################################################################[/+] [+]# #[/+] [+]# WinApps Install Wizard #[/+] [+]# #[/+] [+]################################################################################[/+] [+]WinApps installation already present at /home/iankabaka/.local/bin/winapps-src. Updating...[/+] [+]Already up to date.[/+] [+]Installing WinApps.[/+] [+]Checking for existing conflicting WinApps installations... Done![/+] [+]Attempting to load WinApps configuration file... Done![/+] [+]Checking whether dependencies are installed... Done![/+] [+]Checking container status... Done![/+] [+]Checking for an open RDP Port on Windows... Done![/+] [+]Attempting to establish a Remote Desktop connection with Windows... Failed![/+] [+]ERROR: REMOTE DESKTOP PROTOCOL FAILURE.[/+] [+]FreeRDP failed to establish a connection with Windows.[/+] [+]--------------------------------------------------------------------------------[/+] [+]Please view the log at /home/iankabaka/.local/share/winapps/FreeRDP_Test_20260718_2236_168346206.log.[/+] [+]Troubleshooting Tips:[/+] [+]- Ensure the user is logged out of Windows prior to initiating the WinApps installation.[/+] [+]- Ensure the credentials within the WinApps configuration file are correct.[/+] [+]- Utilise a new certificate by removing relevant certificate(s) in /home/iankabaka/.config/freerdp/server.[/+] [+]- Try increasing the RDP_TIMEOUT in /home/iankabaka/.config/winapps/winapps.conf.[/+] [+]- If using 'libvirt', ensure the Windows VM is correctly named as specified within the README.[/+] [+]- If using 'libvirt', ensure 'Remote Desktop' is enabled within the Windows VM.[/+] [+]- If using 'libvirt', ensure you have merged 'RDPApps.reg' into the Windows VM's registry.[/+] [+]- If using 'libvirt', try logging into and back out of the Windows VM within 'virt-manager' prior to initiating the WinApps installation.[/+] [+]--------------------------------------------------------------------------------[/+] [+]Exiting with status '14'.[/+] [+]--------------------------------------------------------------------------------------------------------------------------------------------------------------[/+] [+]~/.local/bin/winapps-src (main) » 14 ↵ iankabaka@pop-os[/+] [+]~/.local/bin/winapps-src (main) » cat /home/iankabaka/.local/share/winapps/FreeRDP_Test_20260718_2236_168346206.log 14 ↵ iankabaka@pop-os[/+] [+]F: X11 socket /tmp/.X11-unix/X1 does not exist in filesystem, trying to use abstract socket instead.[/+] [+][22:36:46:446] [2:00000002] [WARN][com.freerdp.client.common.cmdline] - [warn_credential_args]: Using /p is insecure[/+] [+][22:36:46:446] [2:00000002] [WARN][com.freerdp.client.common.cmdline] - [warn_credential_args]: Passing credentials or secrets via command line might expose these in the process list[/+] [+][22:36:46:446] [2:00000002] [WARN][com.freerdp.client.common.cmdline] - [warn_credential_args]: Consider using one of the following (more secure) alternatives:[/+] [+][22:36:46:446] [2:00000002] [WARN][com.freerdp.client.common.cmdline] - [warn_credential_args]: - /args-from: pipe in arguments from stdin, file, file descriptor or environment variable[/+] [+][22:36:46:446] [2:00000002] [WARN][com.freerdp.client.common.cmdline] - [warn_credential_args]: - /from-stdin pass the credential via stdin[/+] [+][22:36:46:446] [2:00000002] [WARN][com.freerdp.client.common.cmdline] - [warn_credential_args]: - set environment variable FREERDP_ASKPASS to have a gui tool query for credentials[/+] [+][22:36:47:018] [2:0000000a] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x55c8e3c23960]: *************************************************[/+] [+][22:36:47:018] [2:0000000a] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x55c8e3c23960]: This build is using [experimental] build options:[/+] [+][22:36:47:018] [2:0000000a] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x55c8e3c23960]: * 'WITH_VAAPI_H264_ENCODING=ON'[/+] [+][22:36:47:018] [2:0000000a] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x55c8e3c23960]: *[/+] [+][22:36:47:018] [2:0000000a] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x55c8e3c23960]: [experimental] build options might crash the application[/+] [+][22:36:47:018] [2:0000000a] [WARN][com.freerdp.core.rdp] - [log_build_warn][0x55c8e3c23960]: *************************************************[/+] [+][22:36:47:145] [2:0000000a] [WARN][com.freerdp.crypto] - [verify_cb]: Certificate verification failure 'self-signed certificate (18)' at stack position 0[/+] [+][22:36:47:145] [2:0000000a] [WARN][com.freerdp.crypto] - [verify_cb]: CN = MYWINDO-G3MV47U[/+] [+][22:36:47:148] [2:0000000a] [ERROR][com.winpr.sspi.Kerberos] - [kerberos_AcquireCredentialsHandleA]: krb5_parse_name (Configuration file does not specify default realm [-1765328160])[/+] [+][22:36:47:148] [2:0000000a] [ERROR][com.winpr.sspi.Kerberos] - [kerberos_AcquireCredentialsHandleA]: krb5_parse_name (Configuration file does not specify default realm [-1765328160])[/+] [+][22:39:50:364] [2:0000000a] [ERROR][com.freerdp.core] - [rdp_set_error_info]: ERRINFO_LOGOFF_BY_USER [0x0001000C][/+] [+][22:36:46:932] [2:00000002] [INFO][com.freerdp.client.SDL] - [winpr_LogOutputFunction]: [SDL_LOG_CATEGORY_RENDER] OpenGL shaders: ENABLED[/+] [+][22:36:46:932] [2:00000002] [INFO][com.freerdp.client.SDL] - [winpr_LogOutputFunction]: [SDL_LOG_CATEGORY_RENDER] Created renderer: opengl[/+] [+][22:36:46:961] [2:0000000a] [INFO][com.freerdp.client.SDL] - [preConnect]: Update size to 1920x1080[/+] [+][22:36:48:229] [2:00000002] [INFO][com.freerdp.client.SDL] - [winpr_LogOutputFunction]: [SDL_LOG_CATEGORY_RENDER] OpenGL shaders: ENABLED[/+] [+][22:36:48:230] [2:00000002] [INFO][com.freerdp.client.SDL] - [winpr_LogOutputFunction]: [SDL_LOG_CATEGORY_RENDER] Created renderer: opengl[/+] [+][22:36:48:230] [2:0000000a] [INFO][com.freerdp.gdi] - [gdi_init_ex]: Local framebuffer format PIXEL_FORMAT_BGRA32[/+] [+][22:36:48:230] [2:0000000a] [INFO][com.freerdp.gdi] - [gdi_init_ex]: Remote framebuffer format PIXEL_FORMAT_BGRA32[/+] [+][22:36:48:243] [2:00000010] [INFO][com.freerdp.channels.rdpdr.client] - [devman_load_device_service]: Loading device service drive [home] (static)[/+] [+][22:36:48:250] [2:0000000a] [INFO][com.freerdp.channels.rdpsnd.client] - [rdpsnd_load_device_plugin]: [static] Loaded pulse backend for rdpsnd[/+] [+][22:36:48:250] [2:0000000a] [INFO][com.freerdp.channels.drdynvc.client] - [dvcman_load_addin]: Loading Dynamic Virtual Channel rdpsnd[/+] [+][22:36:48:250] [2:0000000a] [INFO][com.freerdp.channels.drdynvc.client] - [dvcman_load_addin]: Loading Dynamic Virtual Channel audin[/+] [+][22:36:48:256] [2:0000000a] [INFO][com.freerdp.channels.audin.client] - [audin_load_device_plugin]: Loaded pulse backend for audin[/+] [+][22:36:48:256] [2:0000000a] [INFO][com.freerdp.channels.drdynvc.client] - [dvcman_load_addin]: Loading Dynamic Virtual Channel ainput[/+] [+][22:36:48:256] [2:0000000a] [INFO][com.freerdp.channels.drdynvc.client] - [dvcman_load_addin]: Loading Dynamic Virtual Channel rdpgfx[/+] [+][22:36:48:256] [2:0000000a] [INFO][com.freerdp.channels.drdynvc.client] - [dvcman_load_addin]: Loading Dynamic Virtual Channel disp[/+] [+][22:36:48:655] [2:00000017] [INFO][com.freerdp.channels.rdpsnd.client] - [rdpsnd_load_device_plugin]: [dynamic] Loaded pulse backend for rdpsnd[/+] [+][22:36:50:568] [2:00000010] [INFO][com.freerdp.channels.rdpdr.client] - [device_announce]: registered [ drive] device #1: home (type= 8 id= 1)[/+] [+][22:39:50:364] [2:0000000a] [INFO][com.freerdp.core] - [rdp_print_errinfo]: ERRINFO_LOGOFF_BY_USER (0x0000000C):The disconnection was initiated by the user logging off their session on the server.[/+] [+][22:39:50:365] [2:0000000a] [INFO][com.freerdp.client.SDL] - [sdl_client_thread_run]: Error info says user did not initiate but disconnect ultimatum says they did; treat this as a user logoff[/+] [+]--------------------------------------------------------------------------------------------------------------------------------------------------------------[/+] [+]~/.local/bin/winapps-src (main) » iankabaka@pop-os[/+] [+][/+]
[+]### Terms[/+]
[+]- [x] I am running the latest version.[/+]
[+]- [x] To the best of my knowledge, this is a bug and not a setup nor a FreeRDP problem.[/+]
[+]- [x] I have checked for duplicate issues.[/+]
[+]- [x] I agree to follow this project's Code of Conduct.