Open aytey opened 5 months ago
Some other notes:
[system-distro-env]
;
;enable weston-debug for live debug view message
;weston-debug -l to see available scopes
WESTON_DEBUG_PROTOCOL=true
;
;enable performance timeline
WESTON_LOG_SCOPES=timeline
;
;enable Xwayland debug
WESTON_LOG_SCOPES=xwm-wm-x11
;
;configure idle timeout
;default is 300 seconds
WESTON_IDLE_TIME=300
;
;rdp-backend debug level
;level 0 to 5
WESTON_RDP_DEBUG_LEVEL=5
;
;rdprail-shell debug level
;level 0 to 5
WESTON_RDPRAIL_SHELL_DEBUG_LEVEL=5
;
;shared memory
WESTON_RDP_SHARED_MEMORY=true
;
;window z-order sync with Windows
WESTON_RDP_WINDOW_ZORDER_SYNC=true
;
;window title
WESTON_RDP_APPEND_DISTRONAME_TITLE=true
WESTON_RDP_COPY_WARNING_TITLE=true
;
;Logging level for FreeRDP
;TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF
WLOG_LEVEL=DBG
;
;xkb debugging
;debug, info, warning, error, critical
XKB_LOG_LEVEL=debug
;
;xkb compiler
;0 to 10
XKB_LOG_VERBOSITY=10
;
;disable GPU in system-distro
;(must be disabled in user-distro as well, exporting this env.)
LIBGL_ALWAYS_SOFTWARE=1
;
;restart weston compositor and Xwayland by Left-Ctrl + Left-Atl + Backspace
WESTON_RDPRAIL_SHELL_ALLOW_ZAP=true
I updated WSL via https://github.com/microsoft/WSL/releases (as per the issue template):
WSL version: 2.1.0.0
Kernel version: 5.15.137.3-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22631.3007
Still reproduces.
Windows build number:
10.0.22631.0
Your Distribution version:
22.04
Your WSL versions:
WSL version: 2.0.9.0 Kernel version: 5.15.133.1-1 WSLg version: 1.0.59 MSRDC version: 1.2.4677 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22631.3007
Steps to reproduce:
WSL logs:
pulseaudio.log stderr.log versions.txt weston.log wlog.log
Expected behavior:
I've tried this on a number of other X11 servers (e.g., VcXsrv, Moba, Exceed) and I don't see this crash, so it does seem unique to WSLg.
Actual behavior:
Here's a backtrace from gdb showing what happens when the application crashes: