-
Notifications
You must be signed in to change notification settings - Fork 317
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
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
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 View similar issuesPlease 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:
|
Diagnostic information
|
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
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:
Any windows launched after this work without the warning!
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: