Smoothly running xwayland-run to get X11 app to work

[almounah]

Hello,

First of all thank you for niri, very cool project :)

I understand the decision to not pollute niri with cursed X11 code. However sadly all the tools I use require X11 and handle wayland badly. For example I use soapui, burpsuite etc. Lets take google-chrome as an example (I know it has the wayland support flag but lets run it without it for test).

I managed to run chrome with xwayland-satellite. However it is buggy. The three dots are not opening for example.

I tried to run it with cage but it keeps crashing.

The promising thing was xwayland-run.

As you see above, It opens and work correctly but I am missing 2 things:

• The default size. I want to use some xwayland option to be to detect my screen size and size the application correctly at startup
• Resize. I want when I resize my window with Super+F for example, for the application to resize with it

I know you cannot get everything you want in life. But I am sharing this, maybe someone already digged deeper and found a solution and is willing to share to save me time.

I think that if I get chrome to run correctly without bugs, I might get my other tools to work correctly the same way :)

Thanks

[Coruscant11]

Hi could you try _JAVA_AWT_WM_NONREPARENTING=1 for JavaFX applications
For chrome you can enable Wayland flags to use Wayland by default instead of XWayland, this is supported since few years and be much smoother

[almounah]

@Coruscant11 Hey, I tried and now my flatpak application (ex. SoapUI) and Burpsuite work without issue with xwayland-satellite.

Thanks man for pinpoiting this :)

[YaLTeR]

You should also report these application issues to xwayland-satellite so Supreme can figure out how to fix them

[bbb651]

The problem is that xwayland-satellite can't set the enviroment for applications since they are launched through niri, it could be documented better though since it's such a common issue. This pretty much affects only java applications and is completely fixed with the environment variable, I looked into making xwayland-satellite reparenting a couple of months ago and it looks like a pretty big refactor.

Maybe setting _JAVA_AWT_WM_NONREPARENTING=1 by default in niri wouldn't be a bad idea? The main downside I can think of is that it can leak into nested Xwayland sessions with window managers that are reparenting, I'm not sure if it can break applications. Maybe having a generic way to override environment variables through the IPC which xwayland-satellite could use on startup would be better?