Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
1 of 2 tasks
rowleya opened this issue Jul 24, 2024 · 3 comments
Open
1 of 2 tasks

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

rowleya opened this issue Jul 24, 2024 · 3 comments

Comments

@rowleya
Copy link

rowleya commented Jul 24, 2024

Windows Version

Microsoft Windows [Version 10.0.22631.3880]

WSL Version

2.3.12.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

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

Copy link

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 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, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] 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
Copy link
Author

rowleya commented Jul 24, 2024

Copy link

Diagnostic information
.wslconfig found
Detected appx version: 2.3.12.0
optional-components.txt not found

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant