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
X11 applications in Wayland cannot be run in VSCodium #317
Comments
Hi @NetDwarf, can you elaborate more about your problem? |
I am not sure what to elaborate on. I am in Wayland and compile/open an Avalonia GUI application (X11). This fails since #300 (VSCodium running on Wayland by default instead of X11). It's not unexpected, but the README should be updated accordingly to warn Wayland users. |
#300 is about Maybe will be good if you add some steps to reproduce this issue. |
I am wrong. It was #298 . To reproduce: 1.) Run Wayland (Gnome in my case) Result: App crashes, because of no display. Again, this is expected, but the README should reflect that. |
@NetDwarf, now is more clear. Can you make that changes on the README and make a PR? |
It seems there is actually a direct mitigation without user interaction. Disabling fallback-x11 actually fixes the problem as in #322 |
I just upgraded and X11 (GUI) applications (Avalonia UI specifically) fail to start with the following error:
The error happens under Wayland, when starting an X11 application in VSCodium. It was introduced with #300 and is fixed by this.
The issue is mostly the assumption in #300 that
nosocket=waylaynd
is not needed and the wording in the README:As it happens under Wayland as well.
The text was updated successfully, but these errors were encountered: