Pengwin with X410 not working

Created on 20 Feb 2020  路  5Comments  路  Source: WhitewaterFoundry/Pengwin

Describe the bug
On a clean install of freshly purchased pengwin on WSL 2, with clean install of X410 running (purchased because it was recommended by pengwin). Installed everything in GUI sub-menu of pengwin-setup. When installing Windows 10 theme get Error: cannot open display:. When running lxappearance from command line, just hangs for a while before reporting same error.

Installed VSCode, typing code . returns but didn't open VSCode!

glxgears gives Error: couldn't open display 192.168.86.35:0.0 error.

This gave me the hint that it was configured to the external IP address and not 127.0.01. Enabling 'Allow Public Access' on X410 (note this is disabled on X410 on a clean install) then allowed the above allowed VSCode and glxgears to work. However, running lxappearance gave:

(lxappearance:14921): GLib-GIO-CRITICAL **: 01:27:16.705: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

(lxappearance:14921): GLib-GIO-CRITICAL **: 01:27:16.705: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed`

But did run the window.

How do I setup to avoid having X410 needing to 'Allow Public Access'?

Thanks

Answered Bug User Support

All 5 comments

Also should mention that having needed to reinstall after following bug submission guidelines, I again got the error run-detectors: unable to find an interpreter for /mnt/c/Windows/System32/ipconfig.exe on first boot.

Hi,

This is the limitation of WSL2. If you use WSL2, you have to use 'Allow Public Access', regardless of which X server you are using.

For the error, it is the limitation of WSL/WSL2 itself. It is normal and can be ignored.

For the run-detectors problem, we will try to investigate the problem.

Thanks! Is there a way to surface this in the setup app? For example, during setup of GUI check if an external IP is configured and/or if WSL 2, and if a connection to an XClient isn鈥檛 found warn/recommend X410 and mention the setting? Or at least put it as a warning on the link for X410 recommendation when running under WSL 2.

It really wasn鈥檛 obvious what was going on.

Thanks for the suggestion, it would be a great idea

Hello,

Starting X410 with Allow Public Access is something that was kindy fixed by one collaborator and will be available soon: https://github.com/WhitewaterFoundry/pengwin-setup/pull/222

Any case it is described here in the X410 page https://token2shell.com/howto/x410/using-x410-with-wsl2/

The run-detectors problem it is an upstream issue of wsl2 can be solved running wsl --shutdown in Windows command line.

Regards

Was this page helpful?
0 / 5 - 0 ratings

Related issues

BhavyaJain7 picture BhavyaJain7  路  3Comments

mikart143 picture mikart143  路  5Comments

laurin1 picture laurin1  路  4Comments

AceHack picture AceHack  路  4Comments

juliosegarra picture juliosegarra  路  3Comments