-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Compositor-Proxy-Cli failing to work on newer packages #142
Comments
Should be possible, need to figure out some snags with WSL2 though. |
Having trouble running any I can't get any wayland application ( On Xwayland ( On WSL I've been playing around on the default Ubuntu distribution. |
Hi, could you describe what you are trying to do as it's not entirely clear from your description. Are you simply trying to run it in wsl or something more? |
Yep, right now I'm simply trying to run it in WSL2. I managed to get everything working besides the Compositor Proxy. |
Managed to get the proxy working with docker after booting up a Linux VM and comparing every intermediate output, turns out a file got corrupted for Docker on WSL and reinstalling the distro and packages fixed it. Also managed to reproduce the buffer error with Docker, just switched Going to try to figure out what needs to be pinned / compiled from source so it can be run outside of Docker. |
Got it working e2e on Linux, nothing needed to be pinned, just I can get it working from a Linux browser but if I try to connect from Windows, I can load the webpage and run the command, but no window is created on the browser on the Window's side. |
I'll see if I can get something running and documented in the coming weeks a well. Running on WSL used to work a couple of versions ago, so it should still work but perhaps some things have changed in the meantime. |
Is it possible to have Sommelier as a proxy for a windows to Greenfield? Greenfield looks like it can maybe be used to make wslg far more usable?
The only real condition is for Greenfield to expose its Wayland display via a socket (though they seem to be addressed as URLs here) I believe?
The text was updated successfully, but these errors were encountered: