[GH-ISSUE #1315] Beware, Ubuntu 21.10 likes Wayland! #1040

Closed
opened 2026-05-05 07:24:14 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @frohro on GitHub (Oct 12, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1315

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

Originally created by @frohro on GitHub (Oct 12, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1315 ### 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_
gitea-mirror 2026-05-05 07:24:14 -06:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@jeukel commented on GitHub (Oct 18, 2021):

This is a know issue and support for Wayland is expected over here:
https://github.com/debauchee/barrier/issues/1315

<!-- gh-comment-id:945281090 --> @jeukel commented on GitHub (Oct 18, 2021): This is a know issue and support for Wayland is expected over here: https://github.com/debauchee/barrier/issues/1315
Author
Owner

@Ashark commented on GitHub (Oct 23, 2021):

@jeukel your link it this issue itself, you mean #1251.
Now I think this can be closed, as warning was added for wayland, see #247.

<!-- gh-comment-id:950212875 --> @Ashark commented on GitHub (Oct 23, 2021): @jeukel your link it this issue itself, you mean #1251. Now I think this can be closed, as warning was added for wayland, see #247.
Author
Owner

@shymega commented on GitHub (Oct 23, 2021):

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.

<!-- gh-comment-id:950219549 --> @shymega commented on GitHub (Oct 23, 2021): 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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#1040
No description provided.