forked from deskflow/deskflow
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Beware, Ubuntu 21.10 likes Wayland! #1315
Labels
bug
Something isn't working
Comments
This is a know issue and support for Wayland is expected over here: |
This doesn't really add anything to the project, there's already an issue for Wayland... please, before opening issues, do a search on the tracker. Closing. |
ghost
mentioned this issue
Nov 10, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
I upgraded to Ubuntu 21.10 from 21.04. I had a hard time, because first the login defaulted from Xorg to Wayland. I then changed it back to Xorg on the login screen, but barrier still wasn't behaving as expected (connected but could not enter the client screen). I was about at my wit's end when I decided to make sure I was using Xorg, not Wayland so I could make a bug report. I used the following command to check.
$ echo $XDG_SESSION_TYPE
and it say Wayland! I logged out, and the login type was Ubuntu-Xorg, not Ubuntu. So I logged in with a different GUI, and there barrier worked properly. Then I went and logged out of that GUI, and back in as Ubuntu-Xorg, and now the session typ. is x11 in Gnome shell, and barrier works. So watch out, Ubuntu 21.10 loves Wayland, and we barrier users do not!
Version
v2.3.3
Git commit hash (if applicable)
No response
If applicable, where did you install Barrier from?
No response
What OSes are you seeing the problem on? (Check all that apply)
Linux
What OS versions are you using?
Ubuntu 21.10 on clients and server.
Relevant log output
No response
Any other information
No response
The text was updated successfully, but these errors were encountered: