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.

Sign up for GitHub

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

Jump to bottom

Wayland: Add support for reconnecting to the compositor #5667

Open
tronical opened this issue Jul 22, 2024 · 0 comments
Open

Wayland: Add support for reconnecting to the compositor #5667

tronical opened this issue Jul 22, 2024 · 0 comments
Labels
a:backend-winit Winit backend (mS,mO) a:platform-linux issue specific to Linux, X11 or wayland (mO,bT) enhancement New feature or request

Comments

@tronical
Copy link
Member

On X11, when the window manager disappeared and re-appeared, the X server would remaining running and applications would "survive". With wayland, when the compositor crashes or is restarted, we abort the process. Instead, we should try to re-connect.

See also rust-windowing/winit#3427
@tronical tronical added enhancement New feature or request a:platform-linux issue specific to Linux, X11 or wayland (mO,bT) a:backend-winit Winit backend (mS,mO) labels Jul 22, 2024
tronical added a commit that referenced this issue Jul 22, 2024
@tronical
winit: Prefer X11 over Wayland when running in WSL
321f143 
This is a workaround for the compositor on WSL tending to crash.
Unfortunately we can't just try to create an event loop with x11 first
and then re-try with wayland, winit doesn't allow that. So just avoid
wayland for now.

The long term solution #5667

Fixes #5657
@tronical tronical mentioned this issue Jul 22, 2024
Merged
tronical added a commit that referenced this issue Jul 22, 2024
@tronical
winit: Prefer X11 over Wayland when running in WSL
cc90197 
This is a workaround for the compositor on WSL tending to crash.
Unfortunately we can't just try to create an event loop with x11 first
and then re-try with wayland, winit doesn't allow that. So just avoid
wayland for now.

The long term solution #5667

Fixes #5657
tronical added a commit that referenced this issue Jul 22, 2024
@tronical
winit: Prefer X11 over Wayland when running in WSL
32fac37 
This is a workaround for the compositor on WSL tending to crash.
Unfortunately we can't just try to create an event loop with x11 first
and then re-try with wayland, winit doesn't allow that. So just avoid
wayland for now.

The long term solution #5667

Fixes #5657
tronical added a commit that referenced this issue Jul 22, 2024
@tronical
winit: Prefer X11 over Wayland when running in WSL
28f7ee7 
This is a workaround for the compositor on WSL tending to crash.
Unfortunately we can't just try to create an event loop with x11 first
and then re-try with wayland, winit doesn't allow that. So just avoid
wayland for now.

The long term solution #5667

Fixes #5657
@tronical tronical mentioned this issue Jul 22, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
a:backend-winit Winit backend (mS,mO) a:platform-linux issue specific to Linux, X11 or wayland (mO,bT) enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tronical