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

Emulator defaults to Xwayland despite having Wayland support #1878

Closed
C0rn3j opened this issue Dec 25, 2024 · 3 comments
Closed

Emulator defaults to Xwayland despite having Wayland support #1878

C0rn3j opened this issue Dec 25, 2024 · 3 comments

Comments

@C0rn3j
Copy link
Contributor

C0rn3j commented Dec 25, 2024

Is this intended?

unsetting DISPLAY makes it run under native Wayland, which is preferable, unless there are some major issues, but it seems to work fine on my machine™.

Keeping the possibility to override it to Xwayland would of course make sense.

@ngoquang2708
Copy link
Contributor

It because of this libsdl-org/SDL#9383.

@ngoquang2708
Copy link
Contributor

I made a PR to force Wayland #1827 but decided that just wait for DEs to implement required protocols.

@C0rn3j
Copy link
Contributor Author

C0rn3j commented Dec 25, 2024

One of the needed protocols was just pushed a release behind for kwin which I use... https://invent.kde.org/plasma/kwin/-/merge_requests/6474

But I suppose this is then resolved on shad's side, as it will eventually default to Wayland on its own.

It is worth to mention that messing with DISPLAY is the wrong way to do this based on reading that thread, and export SDL_VIDEO_DRIVER=wayland; shadps4 is actually the way to go.

@C0rn3j C0rn3j closed this as completed Dec 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants