Nathaniel Graham

Unfortunately, I don't seem to be able to find any crash logs. It crashes immediately without output and when I turn VSCode back on, even some workspace settings have changed...

I will say that most likely it's some interaction too with my linux distribution packages, as I tried downgrading to previous versions of the Go extension, which used to work,...

just fyi, I'm on vacation for the next 6 days, so I'll check back and continue providing information when I get back

ok, it just crashed again, this time with only the go extension enabled. I'm not sure what's going on anymore

I don't know if they're relevant, but here are the Extension Host logs ```bash 2024-08-07 11:44:56.146 [info] Extension host with pid 294056 started 2024-08-07 11:44:56.146 [info] Skipping acquiring lock for...

as a test, I did try running code without the flags `--ozone-platform=wayland --enable-features=UseOzonePlatform`, and the crashes stopped completely

> Steam has some settings to disable Steam Input on Nintendo controllers anyway Why would you want to disable Steam Input though, isn't the fact that Steam can handle any...

I'm also seeing this issue when building for x86_64-pc-windows-gnu

And, using the `rusttls` runtime like you did worked for me as well, thank you!

It turns out that for whatever reason AppImageLauncher was interfering with mangohud. Not sure why though, and I'm interested to see if there's a way to get mangohud to work...