This also seems to effect games using current versions(0.12.x) of node.js and has been hampering CrossCode Linux testing efforts.
Do you have an example of such a game that we could reproduce the issue on?
CrossCode is all that I'm aware of at the moment
Today's beta client update seems to resolve things. Thank you!
Awesome! Feel free to close this issue
On 26 Jan 2016 6:35 p.m., "Cheese" [email protected] wrote:
Today's update seems to resolve things. Thank you!
—
Reply to this email directly or view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/4182#issuecomment-174841343
.
@aaronfranke, please retest when you have some free time.
I can confirm that launching Chrome now works as it is supposed to. Issue closed as fixed.
The process starts but no window appears. The same commands ran from a Terminal work fine.
Specs: Xubuntu 15.10 64-bit, latest Steam for Linux (opted into the beta), latest Google Chrome 47 Linux 64-bit, rests of my specs.