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

mstsc.exe exited with status 1 - Graphical apps do not launch #130

Closed
dkozel opened this issue Apr 29, 2021 · 9 comments
Closed

mstsc.exe exited with status 1 - Graphical apps do not launch #130

dkozel opened this issue Apr 29, 2021 · 9 comments
Labels
bug Something isn't working rdp-client-connection

Comments

@dkozel
Copy link

dkozel commented Apr 29, 2021

Environment

Windows build number: 10.0.21364.0
Distribution version: Ubuntu 20.04
WSLg version: 1.0.17.1
WSL Update version: 5.10.16

Steps to reproduce

Launch Ubuntu app (terminal)
Observe:

An error occured mounting one of your file systems. Please run dmesg for more details.

dmesg shows many instances of:

[  752.338494] WSLGd: Exception: No such file or directory @../ProcessMonitor.cpp:56 (LaunchProcess)
[  752.338606] WSLGd: /mnt/c/Windows/System32/mstsc.exe exited with status 1.

WSL logs:

weston.log
pulseaudio.log

Versions.txt:

WSLg ( x86_64 ): 1.0.17+3.Branch.master.Sha.a526dfd5ad03d126bb2d8c528f6c3563e86a40da
Mariner: VERSION="1.0.20210224"
FreeRDP: e4a2fc2053bd8c5f99455fcd08ffee7e5591567a
weston: fd961f5cd116c9358d82ce94d139c1578e21bd00
pulseaudio: 2f0f0b8c3872780f15e275fc12899f4564f01bd5                                                                                                                                                             mesa: 

Expected behavior

mstsc.exe launches normally, the disk mounts, and graphical applications run correctly.

Actual behavior

The above error messages, and graphical applications hang indefinitely when trying to launch. The error message sometimes is

Gdk-CRITICAL **: 21:12:11.016: gdk_seat_get_keyboard: assertion 'GDK_IS_SEAT (seat)' failed

@dkozel dkozel added the bug Something isn't working label Apr 29, 2021
@hideyukn88
Copy link
Member

@dkozel , thanks for reporting, would you please refer #125, and check task manager at Windows to see if mstsc.exe is repeatedly start and terminate with different PID ? We would like to know if mstsc.exe is actually started on Windows (and terminated immediately) or it doesn't start at all, thanks!

@dkozel
Copy link
Author

dkozel commented Apr 29, 2021

Hi @hideyukn88 I have not seen mstsc.exe running at all in the task manager. I'm helping mentor a hackfest at Microsoft today and tomorrow, if I can be of any use directly debugging this please let me know.

@hideyukn88
Copy link
Member

@dkozel , would you please share dmesg (from boot to the first mstsc error message) ?

@spronovo
Copy link
Collaborator

@dkozel could you open a feedback bug using the feedback hub (type feedback in the start menu). Write something like below and the feedback will get routed to us. This will allow us to look at the history of crashes on your system and retrieve any crash dump from mstsc so we can better understand what's going on with your system.

image

@dkozel
Copy link
Author

dkozel commented Apr 30, 2021

I realized that there was an old custom kernel (trying to get USB support working) that was lingering on this system. Sorry for the self-inflicted bug. I've attached the dmesg log (as much as I could get, the ring buffer was overflowing) and had already submitted a feedback report before figuring it out. My graphical application now runs normally and the file system mounts correctly.

@hideyukn88 Here are logs before and after removing the custom kernel incase there is something useful.
dmesg-broken.log
dmesg-working.log

Thank you both and everyone involved in the WSL development, there's a lot of potential for improving software availability and bringing new contributors to projects previously inaccessbile to them.

@dkozel dkozel closed this as completed Apr 30, 2021
@tahmidrafi
Copy link

I am facing similar issue with a custom kernel built following this instructions.

:~$ dmesg
[  163.400167] WSLGd: Exception: No such file or directory @../ProcessMonitor.cpp:56 (LaunchProcess)
[  163.400264] WSLGd: /mnt/c/Windows/System32/mstsc.exe exited with status 1.
[  163.400601] WSLGd: Exception: No such file or directory @../ProcessMonitor.cpp:56 (LaunchProcess)
[  163.400709] WSLGd: /mnt/c/Windows/System32/mstsc.exe exited with status 1.
[  163.401005] WSLGd: Exception: No such file or directory @../ProcessMonitor.cpp:56 (LaunchProcess)
[  163.401135] WSLGd: /mnt/c/Windows/System32/mstsc.exe exited with status 1.

:~$ uname -srvmpio
Linux 4.19.84-microsoft-standard+ #2 SMP Wed May 19 03:41:46 CDT 2021 x86_64 x86_64 x86_64 GNU/Linux

Windows Specifications
Edition: Windos 10 Pro
Version: Dev
OS build: 21382.1
Experience: Windows 10 Feature Experience Pack 321.121000.3

PS C:\Users\USER> wsl --status
Default Distribution: Ubuntu-20.04
Default Version: 2

Windows Subsystem for Linux was last updated on 5/1/2021
WSL automatic updates are on.
Windows updates are paused.

Kernel version: 5.10.16

Also I don't understand one thing wsl -status says kernel version 5.10.16, but when I built the kernel from source code, kernel version is 4.19.84-microsoft-standard+. I tried to build the latest release WSL2-Linux-Kernel-linux-msft-wsl-5.10.16.3 but received a lot of permission errors and invalid statement errors. (p.s. please excuse my ignorance, I am very new to this.)

@onomatopellan
Copy link
Contributor

@tahmidrafi It's easy to compile your custom kernel. Just like this:

sudo apt install build-essential flex bison libssl-dev libelf-dev bc -y
wget https://github.com/microsoft/WSL2-Linux-Kernel/archive/refs/tags/linux-msft-wsl-5.10.16.3.tar.gz
tar xvfz linux-msft-wsl-5.10.16.3.tar.gz
cd WSL2-Linux-Kernel-linux-msft-wsl-5.10.16.3/
make KCONFIG_CONFIG=Microsoft/config-wsl

@sorenwacker
Copy link

Same issue.

[ 469.970967] WSLGd: Exception: No such file or directory @../ProcessMonitor.cpp:56 (LaunchProcess)
[ 469.971356] WSLGd: /mnt/c/Windows/System32/mstsc.exe exited with status 1.

@hideyukn88
Copy link
Member

@sorenwacker, would you please make sure your WSLg is up to date by installing update from aka.ms/wslstorepage, and make sure "remote credential guard" feature is not enabled, please refer #734, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working rdp-client-connection
Projects
None yet
Development

No branches or pull requests

6 participants