microsoft / wslg

Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
MIT License
10.07k stars 304 forks source link

Odd message in debug console, and WARN: COPY_MODE on window titles #1278

Open rowleya opened 1 month ago

rowleya commented 1 month ago

Windows Version

Microsoft Windows [Version 10.0.22631.3880]

WSL Version

2.3.12.0

Are you using WSL 1 or WSL 2?

Kernel Version

6.6.36.3-1

Distro Version

Ubuntu 22.04

Other Software

Anything graphical, but mainly using Eclipse (in x11 mode) and Chrome (in Wayland mode)

Repro Steps

  1. Add debugConsole=true to .wslconfig (only required to see the odd message, the WARN still appears without this)
  2. Start up a WSL prompt and watch the debug console.
  3. Before the debug console shows a login prompt, start a window-based application.

Expected Behavior

The application starts and the title bar shows just the application name.

Actual Behavior

The debug console shows a message repeatedly (the odd characters are there), with the time increasing: A start job is running for Wait for…k to be Configured (6s / no limit)

The window has "WARN: COPY_MODE" in it before the title.

Eventually (around 2 minutes later) the debug console shows: [FAILED] Failed to start Wait for Network to be Configured.

followed by:

[KSee 'systemctl status systemd-networkd-wait-online.service' for details.
[  OK  ] Reached target Network is Online.

Any windows launched after this work without the warning!

Diagnostic Logs

No response

github-actions[bot] commented 1 month ago

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs Download and execute [collect-wsl-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-wsl-logs.ps1) in an **administrative powershell prompt**: ``` Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1 ``` The script will output the path of the log file once done. If this is a networking issue, please use [collect-networking-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

rowleya commented 1 month ago

WslLogs-2024-07-24_08-52-53.zip

github-actions[bot] commented 1 month ago
Diagnostic information ``` .wslconfig found Detected appx version: 2.3.12.0 optional-components.txt not found ```