Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gui for nedit doesn't work #364

Closed
gobbedy opened this issue Jul 14, 2021 · 7 comments
Closed

gui for nedit doesn't work #364

gobbedy opened this issue Jul 14, 2021 · 7 comments
Labels
bug Something isn't working

Comments

@gobbedy
Copy link

gobbedy commented Jul 14, 2021

Environment

Windows build number: 10.0.22000.65
Your Distribution version: ubuntu 20.04
Your WSLg version: 1.0.24

Steps to reproduce

Install nedit (sudo apt-get install nedit)
Run nedit: nedit

nedit GUI app does not open, unless I manually open an X-server as before.

Note that gedit GUI does work as expected, so it does appear that my GUI apps work in general.

Please let me know if you need logs, though I suspect it will be trivial to reproduce on your end.

@gobbedy gobbedy added the bug Something isn't working label Jul 14, 2021
@mgateno
Copy link

mgateno commented Jul 14, 2021

Interesting that you say that you need to run an xserver in order to get the gui apps to work at all. In theory this should not be necessary. If so, we are having the same problem, I suspect caused because we both did it the other way before.

@onomatopellan
Copy link
Contributor

For diagnosing non working WSLg take a look at the wiki

Normally after using another xserver these should be enough to get WSLg working:

export DISPLAY=:0
sudo rm -r /tmp/.X11-unix
ln -s /mnt/wslg/.X11-unix /tmp/.X11-unix

@gobbedy
Copy link
Author

gobbedy commented Jul 15, 2021

@mgateno I do not need an xserver in order to get gui apps to work.

GUI apps work without an xserver. It's just nedit specifically that only works when I manually start an xserver.

I have updated my original description to make sure there is no ambiguity.

@onomatopellan my WSLg is fully working, as far as I know. Were you unable to reproduce with the steps I gave?

@onomatopellan
Copy link
Contributor

onomatopellan commented Jul 15, 2021

@gobbedy I can reproduce it some times when WSLg gets in an unstable state. After running wsl.exe --shutdown it works again although this #307 still happens.

@mgateno
Copy link

mgateno commented Jul 15, 2021

For diagnosing non working WSLg take a look at the wiki

Normally after using another xserver these should be enough to get WSLg working:

export DISPLAY=:0
sudo rm -r /tmp/.X11-unix
ln -s /mnt/wslg/.X11-unix /tmp/.X11-unix

I was able to get mine to work using this list of commands. The problem was definitely with the X11 mappings. I have two remaining issues:

  1. My Windows environment has mouse buttons swapped, but the linux apps do not obey this and I cannot find a way to configure this in WSL.
  2. Resizing the windows kills the app. As long as I run them as they popped up everything is OK. The minute I try to resize them all heck breaks loose. My computer has both an Intel and Nvidia (RTX2060) GPUs and I have installed the proper drivers for both of them as per the WSLg recommendations.

@hideyukn88
Copy link
Member

Hi. thanks for reporting the issue.

@gobbedy, would you please clarify how do you run X server manually? WSLg should automatically start the X server (Xwayland) inside system-distro by monitoring X11 socket. On WSLg, "gedit" works as Wayland native app rather than X11 app. Thus I guess X server is not auto-starting in your case? How about other X11 app, such as Firefox, does it run without manually starting X server?

@mgateno,
1: currently mouse button swap is not supported, which is reported at #74.
2: crashing on resize is new to us, there is hang on resize is reported #272. Do you see any core dumps at /mnt/wslg/dumps?

Currently currently we are aware of two outstanding issues with nedit, #141 and #307.

Thanks for trying out WSLg!

@gobbedy
Copy link
Author

gobbedy commented Jul 16, 2021

@onomatopellan @mgateno Thanks, those commands did indeed work!

Thanks all for your help. Closing as this is fixed for me.

@gobbedy gobbedy closed this as completed Jul 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants