Pengwin: Bounty: Help debug quirks with Chrome 69+ on WSL ($50 USD)

Created on 25 Sep 2018 · 8Comments · Source: WhitewaterFoundry/Pengwin

Describe the bug

The new Google Chrome is acting strangely in X clients on WSL.

On VcSrvX it is triggering a core dump: https://twitter.com/ueyasu/status/1044583330912526337

On X410 this is happening:
capture4

This is somewhat erratic, even across other WSL distros, I do not think it is isolated to WLinux.

Commenting out ALWAYS_LIBGL_INDIRECT=0 in /etc/profile sometimes appears to make a difference, _but not consistently_.

To Reproduce

Install WLinux or other Debian-based WSL distro.
$ wget https://github.com/WhitewaterFoundry/WLinux/blob/master/linux_files/installchrome.sh
$ bash installchrome.sh
Accept install.
$ google-chrome

Expected behavior

Chrome works.

Info

X410 1.7.3
Windows Build 17134

Additional context

Because Chrome has announced more logging and tracking of users, I am generally amenably pulling it and shipping a separate browser for people to try on WSL, like Falkon or Epiphany.

Workaround

Comment out ALWAYS_LIBGL_INDIRECT=0 in /etc/profile and restart WLinux or use an alternate browser.

Upstream Issue

Source

sirredbeard

Most helpful comment

for error:
Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Permission denied
Trace/breakpoint trap (core dumped)

Solution:
Below works...
Just Open WSL as Admin and run "$ google-chrome" :) not sure why it needs to be as such

kochandra on 3 Dec 2018

👍5 👎2

All 8 comments

Interesting. On build 18242.1000 chrome directly crashed with following error:

Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Permission denied
[1]    2100 trace trap (core dumped)  google-chrome

It might be the reason that some features required in chrome is not implemented well on WSL

patrick330602 on 25 Sep 2018

One suggestion from Twitter: chrome --disable-gpu link

sirredbeard on 26 Sep 2018

chrome --disable-gpu actually still not working properly in 18242.1000

patrick330602 on 26 Sep 2018

I am converting this to a public bounty. Help WLinux make Chrome 69+ more stable on WSL by (1) submitting a workaround for WSL distros or (2) help us isolate the issue and submit a bug report upstream to Google. Currently $50 USD.

sirredbeard on 27 Sep 2018

Bug bounty is cancelled.

sirredbeard on 18 Oct 2018

for error:
Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Permission denied
Trace/breakpoint trap (core dumped)

Solution:
Below works...
Just Open WSL as Admin and run "$ google-chrome" :) not sure why it needs to be as such

kochandra on 3 Dec 2018

👍5 👎2

Using wsl2 opening wsl bash as admin opens and entirely different environment than the one I'm using in my user account.