alacritty: Cant handle switching between X11 and Wayland

Which operating system does the issue occur on? Linux If on linux, are you using X11 or Wayland? For this issue both.

Seems like alacritty is not able to be started again on X11 if there is still another Wayland compositor running. Terminal output: “wl_drm@36: error 0: authenicate failed thread ‘main’ panicked at ‘called Result::unwrap() on an Err value: Os { code: 71, kind: Other, message: “Protocol error” }’, libcore/result.rs:1009:5”

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 19 (14 by maintainers)

Commits related to this issue

Most upvoted comments

[1]

though it might be nice to recheck once #2438 is finalized.

[2]

Since glutin window example is also fixed, I think if it will be found on #2438 it should be reported directly to winit/glutin as a regression (in case window example will also became broken at some point).

We found out, that the problem was in glutin/winit, you’ve suggested to recheck #2438 when it’ll be ready[1], I’ve decided to add a note[2] that in case we’ll face this bug again on #2438, we should report this as a regression to glutin/winit since everything is fine with glutin/winit/our evlp2 now. Sorry, feel a little bit sleepy today.

, but I wasn’t able to repro it on evlp2 rework and glutin master.

evlp2 rework == #2438

So this issue is resolved in the latest glutin?

Yes, should be added to a list of fixes in #2438 , I guess

XDG_SESSION_TYPE is not something very reliable from my point of view. It can be set to tty if you’ve launched your wm from tty (e.g. sway). Of course login mangers (e.g. sddm) are responsible for setting such variables ( users should remember to set them manually when launching wms from tty though). However I tend to agree, that using XDG_SESSION_TYPE as a “hint” can be a good idea.

It’s probably worth testing how glutins window example behaves in this scenario and also worth checking winit v0.19.1/master docs on how to force specific backend (As far as I remember it’s trying to launch on wayland and fallbacks to X11 if fails).