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

Tracking issue for Wayland development progress #1251

Closed
ghost opened this issue Nov 4, 2021 · 9 comments
Closed

Tracking issue for Wayland development progress #1251

ghost opened this issue Nov 4, 2021 · 9 comments

Comments

@ghost
Copy link

ghost commented Nov 4, 2021

This issue has been migrated from old Barrier Github repository debauchee/barrier#1251

Issue created on: 2021-08-16 by @shymega
Issue last updated on: 2021-09-18

This issue is for Wayland development to be documented, and updates given on the progress of adding Wayland support to Barrier.


Commented on: 2021-08-16 by @shymega

@p12tic Could you please push a branch to the repo with your local Barrier development work when you can, please? That way we can have contributions for Wayland support.


Commented on: 2021-09-18 by @akutoku

The libei project seems to be very interesting in the context of barrier. It seems to be what implementation of barrier working with Wayland compositors needs. Seeing that it's a part of libinput project, seems to be a safe choice to use because it is very likely that this will be used by majority if not all Wayland compositors.

https://gitlab.freedesktop.org/libinput/libei
https://github.com/whot/barrier/tree/wip/ei

@MYanello
Copy link

It seems that they've figured this out for waynergy https://github.com/r-c-f/waynergy

Keyboard mapping is a bit wonky, and only works as a client but it's a start and let's us keep using barrier on wayland for now.

@donjan
Copy link

donjan commented Aug 15, 2022

Ubuntu is rolling out the LTS->LTS upgrade this month, prompting the bulk of its userbase to install 22.04. This time around staying off of Wayland is even more difficult, most people will default to it.
While waynergy works as a client, any Wayland-capable server is needed about now.
A great opportunity for input-leap to distinguish itself from barrier ;)

Just threw $20 at the bounty. Any way to help this further? (my coding time is too limited)
I'll try rkvm again in the next few days, but my previous attempt was unsuccessful.

@p12tic
Copy link
Contributor

p12tic commented Jan 21, 2023

Wayland support has been merged to InputLeap today in #1594. It still requires custom builds of mutter, libportal, xdg-desktop-portal and xdg-desktop-portal-gnome, so the code is not directly useful to the end users just yet. Thanks a lot to @whot and @ofourdan for making this happen.

@p12tic
Copy link
Contributor

p12tic commented Jan 21, 2023

Closing this issue as a duplicate of #109.

@p12tic p12tic closed this as completed Jan 21, 2023
@neofeo
Copy link

neofeo commented Nov 7, 2023

Ubuntu is rolling out the LTS->LTS upgrade this month, prompting the bulk of its userbase to install 22.04. This time around staying off of Wayland is even more difficult, most people will default to it. While waynergy works as a client, any Wayland-capable server is needed about now. A great opportunity for input-leap to distinguish itself from barrier ;)

Just threw $20 at the bounty. Any way to help this further? (my coding time is too limited) I'll try rkvm again in the next few days, but my previous attempt was unsuccessful.

Where those changes on those components upstreamed at some point ?

@ccoenen
Copy link

ccoenen commented Nov 7, 2023

There is no reasonable "upstream" any longer (see this discussion). Nobody maintains barrier. From what I could gather, input-leap is the only reasonable chance at an active fork right now.

Of course there's also always Symless, but I wouldn't hold my breath for them to come forward with a solution first.

@neofeo
Copy link

neofeo commented Nov 7, 2023

I am talking about the patches for their respective git repos....

@neofeo
Copy link

neofeo commented Nov 7, 2023

Mutter, etc

@shymega
Copy link
Member

shymega commented Nov 10, 2023

Symless have already started talking about libei, but didn't really recognise the efforts that originated with this project. I daresay they'll use libei. This is the nature of open source.

With regards to upstream patches for the components needed, this is a good listing: https://gitlab.freedesktop.org/libinput/libei/-/issues/1

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

6 participants