Pengwin: VSCode not launchable. Installed through wlinux-setup

[PGAnonamous]

Describe the bug
VSCode doesn't run.

To Reproduce
Install wlinux.
Run wlinux-setup
Select Editors: Code; GUI
Let everything install and update
Run code --verbose

Output:

[313:0102/190516.356994:ERROR:bus.cc(395)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
shared memfd open() failed: Function not implemented

Expected behavior
Functional VSCode.

Basic Troubleshooting Checklist

• [x] I have searched Google for the error message.
• [x] I have checked official WSL troubleshooting documentation: https://docs.microsoft.com/en-us/windows/wsl/troubleshooting#confirm-wsl-is-enabled.
• [x] I have searched the official Microsoft WSL issues page: https://github.com/Microsoft/WSL/issues.
• [x] I have searched the WLinux issues page: https://github.com/WhitewaterFoundry/WLinux/issues.
• [x] I have reset WLinux: Settings->Apps->Apps & features->WLinux->Advanced Options->Reset.
• [x] I have disabled and re-enabled WSL in Windows Features.
• [x] I have run Windows 10 updates and restarted.

WLinux Version

1.1.27.0

Windows Build

OS Name:                   Microsoft Windows 10 Education
OS Version:                10.0.17763 N/A Build 17763
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
BIOS Version:              Insyde F.45, 10/16/2018

[michalkvasnicka]

I can confirm that.

[khuongduybui]

First things first, I think the latest batch of Debian updates broke this, not Windows / WSL updates, nor WLinux updates.

Note that:

1. eval $(dbus-launch --auto-syntax) seems to start dbus-daemon as normal, but running /usr/bin/code gives the same error and exits.
   ps aux | grep code yields nothing.

1. sudo service dbus start now seems to take forever, but eventually succeeds (just give it minutes)
   After that, running code --verbose --log trace exits almost immediately with no output
   ps aux | grep code now yields

duybui    8109  0.0  0.0 199520 24692 ?        Sl   00:22   0:00 /usr/share/code/code --type=gpu-process --disable-features=ColorCorrectRendering --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=9,27,84 --disable-gl-extensions=GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent --disable-accelerated-video-decode --gpu-vendor-id=0x0000 --gpu-device-id=0x0000 --gpu-driver-vendor --gpu-driver-version --gpu-driver-date --service-request-channel-token=6A9688FDA241CE1B24F276A5ECE
duybui    8174  0.0  0.0 199520 24684 ?        Sl   00:23   0:00 /usr/share/code/code --type=gpu-process --disable-features=ColorCorrectRendering --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=9,27,84 --disable-gl-extensions=GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent --disable-accelerated-video-decode --gpu-vendor-id=0x0000 --gpu-device-id=0x0000 --gpu-driver-vendor --gpu-driver-version --gpu-driver-date --service-request-channel-token=3B3887EF71C377592CB08122E4E
duybui    8224  0.1  0.0 199520 24692 ?        Sl   00:23   0:00 /proc/self/exe --type=gpu-process --disable-features=ColorCorrectRendering --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=9,27,84 --disable-gl-extensions=GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent --disable-accelerated-video-decode --gpu-vendor-id=0x0000 --gpu-device-id=0x0000 --gpu-driver-vendor --gpu-driver-version --gpu-driver-date --service-request-channel-token=F9EF62BD6FA3DC6B454543F23E47FF37
duybui    8310  0.1  0.0 199520 24700 ?        Sl   00:25   0:00 /usr/share/code/code --type=gpu-process --disable-features=ColorCorrectRendering --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=9,27,84 --disable-gl-extensions=GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent --disable-accelerated-video-decode --gpu-vendor-id=0x0000 --gpu-device-id=0x0000 --gpu-driver-vendor --gpu-driver-version --gpu-driver-date --service-request-channel-token=927D6781C56F0324B41ADE4B0E7

But no VSCode window appears in X410.

PS: Oh, and of course, I produced this result from a brand new installation of WLinux with NOTHING but VSCode installed from wlinux-setup.

[tommyvct]

I'm on Kali, same shit:
tommyvct@TOMMYVCT:~$ code --verbose --log trace [8197:0105/023830.562373:ERROR:bus.cc(395)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory shared memfd open() failed: Function not implemented tommyvct@TOMMYVCT:~$ sudo service dbus start [ ok ] Starting system message bus: dbus. tommyvct@TOMMYVCT:~$ code --verbose --log trace shared memfd open() failed: Function not implemented
My dbus works just fine, started in seconds.
so the only problem is memfd, especially the open() function.

PS i cannot find the log file of vscode, where is it?

[khuongduybui]

On a fresh installation of Ubuntu though, I can start vscode 1.30 even without dbus running. It does give an error message that it cannot connect to dbus but carries on anyway.

[tommyvct]

I tried atom, another editor based on Electron framework, same error.
I deleted kali and now I'm trying to figure out how to get desktop running on ubuntu....

[tommyvct]

I think found it out:
Run the start script in admin mode. Done.
memfd error is not critical, it didn't stop these apps from starting.

[PGAnonamous]

I think found it out:
Run the start script in admin mode. Done.
memfd error is not critical, it didn't stop these apps from starting.

@ws1034106504 May you be a bit more specific. What start script? Please list an exact command.

[C-proton]

@ws1034106504 Would you mind telling us how you solved this issue? step by step. much appreciated.

[tommyvct]

https://token2shell.com/howto/x410/running-xfce-desktop-on-kali-linux-wsl/
change x410 and kali to whatever you need

[khuongduybui]

Oh... So what he really meant is run WSL as Windows Administrator

[tommyvct]

IDK how this worked, but it seems even with dbus shutdown Visual Studio Code still works.
Look at the console when you startup xfce, you will find a lot of memfd shit and it didn't prevent xfce from running.

[C-proton]

@tommyvct thanks for replying. But issues persist. There is not workaround yet.

[wari]

Actually, code seems to be running, but no window appeared for me:

  % ps ax | grep code                                                                                                                             !95
 8542 ?        Sl     0:00 /usr/share/code/code --type=gpu-process --disable-features=ColorCorrectRendering --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=9,27,84 --disable-gl-extensions=GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent --disable-accelerated-video-decode --gpu-vendor-id=0x0000 --gpu-device-id=0x0000 --gpu-driver-vendor --gpu-driver-version --gpu-driver-date --service-request-channel-token=610B19A2437DE237FB4F4C8A4F4

[tommyvct]

Hate to say, but did you tried completely start over, including Windows?

[khuongduybui]

Here's my latest try (which works):

1. Reset WLinux (same as uninstall & reinstall from Microsoft Store)
2. Whatever happens, DO NOT EVER RUN apt upgrade
3. Install VSCode manually using official instructions.

#! /bin/bash

# From https://code.visualstudio.com/docs/setup/linux
wget --no-check-certificate -qO - https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor | sudo apt-key add -
echo "deb [arch=amd64] https://packages.microsoft.com/repos/vscode stable main" | sudo tee /etc/apt/sources.list.d/vscode.list
sudo apt update -y
sudo apt install -y code

echo "fs.inotify.max_user_watches=524288" | sudo tee -a /etc/sysctl.conf
sudo sysctl -p

1. Set up variables DISPLAY = :0, LIBGL_ALWAYS_INDIRECT = 1, NO_AT_BRIDGE = 1
2. Run VSCode simply by code (without even the need to run dbus-daemon).

Right now apt is reporting that the following 80 packages on my WLinux instance have not been upgraded. I am willing to bet the new versions of some of them will break VSCode from launching.

1. apt-transport-https/testing,unstable 1.8.0~alpha3 all [upgradable from: 1.8.0~alpha2]
2. apt-utils/testing,unstable 1.8.0~alpha3 amd64 [upgradable from: 1.8.0~alpha2]
3. apt/testing,unstable 1.8.0~alpha3 amd64 [upgradable from: 1.8.0~alpha2]
4. bsdutils/testing,unstable 1:2.33-0.2 amd64 [upgradable from: 1:2.32.1-0.1]
5. dash/testing,unstable 0.5.10.2-4 amd64 [upgradable from: 0.5.10.2-1]
6. e2fsprogs/testing,unstable 1.44.5-1 amd64 [upgradable from: 1.44.4-2]
7. fdisk/testing,unstable 2.33-0.2 amd64 [upgradable from: 2.32.1-0.1]
8. fonts-noto-mono/testing,unstable 20181227-1 all [upgradable from: 20171026-2]
9. ghostscript/testing,unstable 9.26~dfsg-2 amd64 [upgradable from: 9.26~dfsg-1]
10. grep/testing 3.1-3 amd64 [upgradable from: 3.1-2]
11. groff-base/testing 1.22.4-1 amd64 [upgradable from: 1.22.3-10]
12. gzip/testing,unstable 1.9-3 amd64 [upgradable from: 1.9-2.1]
13. init-system-helpers/testing,unstable 1.56+nmu1 all [upgradable from: 1.56]
14. init/testing,unstable 1.56+nmu1 amd64 [upgradable from: 1.56]
15. iproute2/testing,unstable 4.19.0-2 amd64 [upgradable from: 4.18.0-2]
16. iptables/testing,unstable 1.8.2-3 amd64 [upgradable from: 1.8.2-2]
17. isc-dhcp-client/testing,unstable 4.4.1-2 amd64 [upgradable from: 4.3.5-4+b1]
18. isc-dhcp-common/testing,unstable 4.4.1-2 amd64 [upgradable from: 4.3.5-4+b1]
19. libapparmor1/testing,unstable 2.13.2-3 amd64 [upgradable from: 2.13.1-3+b1]
20. libapt-inst2.0/testing,unstable 1.8.0~alpha3 amd64 [upgradable from: 1.8.0~alpha2]
21. libapt-pkg5.0/testing,unstable 1.8.0~alpha3 amd64 [upgradable from: 1.8.0~alpha2]
22. libassuan0/testing,unstable 2.5.2-1 amd64 [upgradable from: 2.5.1-2]
23. libblkid1/testing,unstable 2.33-0.2 amd64 [upgradable from: 2.32.1-0.1]
24. libcairo2/testing,unstable 1.16.0-2 amd64 [upgradable from: 1.16.0-1]
25. libcap-ng0/testing,unstable 0.7.9-1+b1 amd64 [upgradable from: 0.7.9-1]
26. libcom-err2/testing,unstable 1.44.5-1 amd64 [upgradable from: 1.44.4-2]
27. libcups2/testing,unstable 2.2.10-3 amd64 [upgradable from: 2.2.9-2]
28. libcupsfilters1/testing,unstable 1.21.6-2 amd64 [upgradable from: 1.21.4-1]
29. libcupsimage2/testing,unstable 2.2.10-3 amd64 [upgradable from: 2.2.9-2]
30. libdebconfclient0/testing,unstable 0.246 amd64 [upgradable from: 0.245]
31. libedit2/testing,unstable 3.1-20181209-1 amd64 [upgradable from: 3.1-20180525-1]
32. libelf1/testing,unstable 0.175-2 amd64 [upgradable from: 0.170-0.5]
33. libext2fs2/testing,unstable 1.44.5-1 amd64 [upgradable from: 1.44.4-2]
34. libfdisk1/testing,unstable 2.33-0.2 amd64 [upgradable from: 2.32.1-0.1]
35. libgcrypt20/testing,unstable 1.8.4-4 amd64 [upgradable from: 1.8.4-3]
36. libglib2.0-data/testing,unstable 2.58.2-3 all [upgradable from: 2.58.1-2]
37. libgmp10/testing,unstable 2:6.1.2+dfsg-4 amd64 [upgradable from: 2:6.1.2+dfsg-3]
38. libgpg-error0/testing,unstable 1.33-3 amd64 [upgradable from: 1.32-3]
39. libgs9-common/testing,unstable 9.26~dfsg-2 all [upgradable from: 9.26~dfsg-1]
40. libgs9/testing,unstable 9.26~dfsg-2 amd64 [upgradable from: 9.26~dfsg-1]
41. libharfbuzz0b/testing,unstable 2.3.0-1 amd64 [upgradable from: 2.1.1-1+b1]
42. libip4tc0/testing,unstable 1.8.2-3 amd64 [upgradable from: 1.8.2-2]
43. libip6tc0/testing,unstable 1.8.2-3 amd64 [upgradable from: 1.8.2-2]
44. libiptc0/testing,unstable 1.8.2-3 amd64 [upgradable from: 1.8.2-2]
45. libjansson4/testing,unstable 2.12-1 amd64 [upgradable from: 2.11-1]
46. libk5crypto3/testing,unstable 1.16.2-1 amd64 [upgradable from: 1.16.1-1]
47. libldap-2.4-2/testing,unstable 2.4.47+dfsg-1 amd64 [upgradable from: 2.4.46+dfsg-5+b1]
48. libldap-common/testing,unstable 2.4.47+dfsg-1 all [upgradable from: 2.4.46+dfsg-5]
49. libmount1/testing,unstable 2.33-0.2 amd64 [upgradable from: 2.32.1-0.1]
50. libnghttp2-14/testing,unstable 1.35.1-1 amd64 [upgradable from: 1.34.0-1]
51. libopenjp2-7/testing,unstable 2.3.0-1.1 amd64 [upgradable from: 2.3.0-1]
52. libpango-1.0-0/testing,unstable 1.42.4-6 amd64 [upgradable from: 1.42.4-4]
53. libpangocairo-1.0-0/testing,unstable 1.42.4-6 amd64 [upgradable from: 1.42.4-4]
54. libpangoft2-1.0-0/testing,unstable 1.42.4-6 amd64 [upgradable from: 1.42.4-4]
55. libpaper-utils/testing,unstable 1.1.26 amd64 [upgradable from: 1.1.24+nmu5]
56. libpaper1/testing,unstable 1.1.26 amd64 [upgradable from: 1.1.24+nmu5]
57. libperl5.28/testing,unstable 5.28.1-3 amd64 [upgradable from: 5.28.1-1]
58. libpixman-1-0/testing,unstable 0.36.0-1 amd64 [upgradable from: 0.34.0-2]
59. libsmartcols1/testing,unstable 2.33-0.2 amd64 [upgradable from: 2.32.1-0.1]
60. libss2/testing,unstable 1.44.5-1 amd64 [upgradable from: 1.44.4-2]
61. libudev1/testing,unstable 240-2 amd64 [upgradable from: 239-13]
62. libxcb-render0/testing,unstable 1.13.1-2 amd64 [upgradable from: 1.13.1-1]
63. libxcb-shm0/testing,unstable 1.13.1-2 amd64 [upgradable from: 1.13.1-1]
64. libxtables12/testing,unstable 1.8.2-3 amd64 [upgradable from: 1.8.2-2]
65. libzstd1/testing,unstable 1.3.8+dfsg-3 amd64 [upgradable from: 1.3.5+dfsg-1]
66. lsb-base/testing,unstable 10.2018112800 all [upgradable from: 9.20170808]
67. mount/testing,unstable 2.33-0.2 amd64 [upgradable from: 2.32.1-0.1]
68. perl-base/testing,unstable 5.28.1-3 amd64 [upgradable from: 5.28.1-1]
69. perl-modules-5.28/testing,unstable 5.28.1-3 all [upgradable from: 5.28.1-1]
70. perl/testing,unstable 5.28.1-3 amd64 [upgradable from: 5.28.1-1]
71. python3-pycurl/testing,unstable 7.43.0.2-0.1 amd64 [upgradable from: 7.43.0.1-0.2+b1]
72. rsyslog/testing,unstable 8.40.0-1 amd64 [upgradable from: 8.38.0-1+b1]
73. sed/testing,unstable 4.7-1 amd64 [upgradable from: 4.5-2]
74. sysvinit-utils/testing 2.93-2 amd64 [upgradable from: 2.92~beta-2]
75. tzdata/testing,unstable 2018i-1 all [upgradable from: 2018g-1]
76. ucf/testing,unstable 3.0038+nmu1 all [upgradable from: 3.0038]
77. udev/testing,unstable 240-2 amd64 [upgradable from: 239-13]
78. util-linux/testing,unstable 2.33-0.2 amd64 [upgradable from: 2.32.1-0.1]
79. xdg-user-dirs/testing,unstable 0.17-2 amd64 [upgradable from: 0.17-1]
80. xxd/testing,unstable 2:8.1.0693-2 amd64 [upgradable from: 2:8.1.0549-1]

[tommyvct]

Maybe give Ubuntu a try?

I'm using Ubuntu now, it works just fine.
Install Ubuntu, follow these instructions https://token2shell.com/howto/x410/customizing-xfce-desktop-for-ubuntu-wsl/ then install vscode.
I already tried 2 times according to this guide, both of systems works well, VSCode launching as expected. Except the debugger is not working with vscode C++ plugin, and that's only thing won't work within VSCode so far. Actually it is that crappy C++ plugin's fault, if you use old version of C++ plugin it will work.

I even update the system to 1810, still works just fine.

VSCode need neither dbus nor memfd to launch. There are something under the hood crushed and the process just hang there, with approximately
12MB of RAM occupied in your memory. You can check this out in windows task manager.

I also tried atom, another editor build on Electron framework back a few days ago when I'm still on Kali, same result as vscode on Kali: hang, 12MB RAM.

I didn't try atom on my current Ubuntu WSL yet, I will try that tomorrow. If atom runs, then my conclusion is there are something wrong in the upper stream, in either the Electron framework, chromium, Node.js, or just with Kali or Wlinux.

By the way, chromium and Firefox can be launched in my Ubuntu WSL, but with serious hangs and FC. My laptop only have 4GB of RAM and intel i3-6100U processor, and I think my weak laptop is also a constraint.

[khuongduybui]

I narrowed it down. Upgrading udev & libudev1 from 239-13 to 240-2 seems to be the breaking change.
Why would the latest udev break launching Electron-based apps is still a mystery.

In the mean time, force-installing 239 version of udev & libudev1 seems to fix the issue.
https://packages.debian.org/stretch-backports/amd64/udev/download
https://packages.debian.org/stretch-backports/amd64/libudev1/download

[tommyvct]

I narrowed it down. Upgrading udev & libudev1 from 239-13 to 240-2 seems to be the breaking change.
Why would the latest udev break launching Electron-based apps is still a mystery.

In the mean time, force-installing 239 version of udev & libudev1 seems to fix the issue.
https://packages.debian.org/stretch-backports/amd64/udev/download
https://packages.debian.org/stretch-backports/amd64/libudev1/download

I think you are right. I just find out my ubuntu 'udev' version is '239-7', and that's the reason why ubuntu works and WLinux and Kali don't.
Could you tell me how do you narrow this down?
Like how do you get more verbose output from vscode?

[khuongduybui]

Unfortunately I didn't get any useful output from vscode...
I wrote a script that upgrades each package and launches code until it breaks.

[tommyvct]

Thanks, Finally the moment of truth.
I think we should start another issue on this.

[crramirez]

Unfortunately I didn't get any useful output from vscode...
I wrote a script that upgrades each package and launches code until it breaks.

Haha excellent. A lot of hard work

[crramirez]

Summarizing your findings. The following commands must be executed in order for Visual Studio Code to be operational again:

echo 'deb https://deb.debian.org/debian stretch-backports main' | sudo tee /etc/apt/sources.list.d/stretch-backports.list
sudo apt-get -y  update
sudo apt-get install -y --allow-downgrades -t stretch-backports udev=239-12~bpo9+1 libudev1=239-12~bpo9+1
sudo apt-mark hold udev libudev1

[PGAnonamous]

Summarizing your findings. The following commands must be executed in order for Visual Studio Code to be operational again:

echo 'deb https://deb.debian.org/debian stretch-backports main' | sudo tee /etc/apt/sources.list.d/stretch-backports.list
sudo apt-get -y  update
sudo apt-get install -y --allow-downgrades -t stretch-backports udev=239-12~bpo9+1 libudev1=239-12~bpo9+1
sudo apt-mark hold udev libudev1

This has indeed got it up and running again.

[sirredbeard]

Seems to be a result of a change in udev:
https://github.com/systemd/systemd/issues/11293

[crramirez]

A workaround was added to wlinux-setup based on your findings. This will ensure that new installs won't have the problem and anyone with the problem just run wlinux-setup again.

Thank you everyone for the help

[PGAnonamous]

A workaround was added to wlinux-setup based on your findings. This will ensure that new installs won't have the problem and anyone with the problem just run wlinux-setup again.

Thank you everyone for the help

Thank you!

[ghost]

Wow. You saved my day! Thank you!

[aghArdeshir]

@crramirez

HI! Thanks for your solution.
But it is not working for me. I get errors

E: Version '239-12~bpo9+1' for 'udev' was not found
E: Version '239-12~bpo9+1' for 'libudev1' was not found

and honestly I couldn't find 239 on the web either.

the two commands above ran with no error and warning.

Do you think I'm doing anything wrong?

I have:
uname -a:

Linux MY_PC_NAME 4.4.0-17763-Microsoft #253-Microsoft Mon Dec 31 17:49:00 PST 2018 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a:

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic

code --verbose:

shared memfd open() failed: Function not implemented

Thanks!

[crramirez]

Hello,

You are not running the latest version of wlinux-setup please update it, and try again to install vs code.

If it doesn't work please run it in this way wlinux-setup --debug. This will generate a verbose output that you can send to us for diagnostics.

Regards

[aghArdeshir]

THANKS @crramirez for your fast response!
Yep! Installing that other Ubuntu in Store fixed it!

But why isn't it updateable like any other app? Am I thinking wrong? : )

BTW, don't bother! I'm fine and everything is great

[crramirez]

Ok when you run wlinux-setup it ask you if you want to update it. Say yes. Then install VS Code using wlinux-setup

[JayDoubleu]

I noticed this issue is closed however the Microsoft Store version of pengwin is still affected by this:

code --verbose
[6343:0504/164739.241844:ERROR:bus.cc(394)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

Also mentioned fix with udev does no longer work as these packages are no longer available in stretch backports.

 sudo apt-get install -y --allow-downgrades -t stretch-backports udev=239-12~bpo9+1 libudev1=239-12~bpo9+1
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '239-12~bpo9+1' for 'udev' was not found
E: Version '239-12~bpo9+1' for 'libudev1' was not found

This is fresh out of the box install of pengwin on fresh windows 10. VSCode works out of the box on ubuntu images.

[jvanderberg]

I am having this problem as well, running up to date pengwin-setup does not fix this. This was working last week, broke after I updated my version of git using apt.