Add support for Wayland session #59
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for your continued contrinutions ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change ensures compatibility with Wayland by adding a command-line argument to use the X11 platform when the
XDG_SESSION_TYPEenvironment variable is set towayland. If it is not set (i.e. in Windows or MacOS, it does not add the--ozone-platform=x11flag to the arguments to launch the chromium-based browser.This is somewhat a temporary workaround, since it still uses X11 instead of Wayland. I assume if there exist a system that fully uses only Wayland, then this fix would be not applicable to them. But, I have yet to see a system that does that.
Tested on:
Closes #58