Gnome-shell-extension-gsconnect: [DEVEL] Mousepad on Wayland
It would be nice if mouse input could be made to work on Wayland too. There may be options, let's gather them here, so that if someone wants to implement it, there are some starting points.
wvengen
All 16 comments
https://stackoverflow.com/questions/31051173 suggests opening /dev/uinput for writing, though that's probably root-only access.
https://superuser.com/questions/1032270 points to some notes
wvengen
on 19 Oct 2018
Do feel free to close when this is out-of-scope (since it is Waylands design to prevent part of this).
wvengen
on 19 Oct 2018
It's in the FAQ.
rugk
on 26 Oct 2018
But I agree that it would be good to have an issue here to track this…
Because AFAIK work is done on this, too, as e.g. remote desktop via pipewire is already an experimental feature.
rugk
on 26 Oct 2018
just installed ubuntu 18.10 and vanilla Gnome. "Remote input" only works in "Gnome on Xorg".
Option "gnome" is wayland isn't it?
nocoZ
on 26 Dec 2018
Correct, currently AT-SPI still doesn't have support for simulating mouse events on Wayland (See: Wayland + Accessibility).
andyholmes
on 26 Dec 2018
It looks like someone has successfully used the remote desktop API to send mouse events: https://bugzilla.gnome.org/show_bug.cgi?id=709999#c5
auscompgeek
on 2 May 2019
Interesting and promising. At the moment, this doesn't seem likely to be usable by GSConnect, since mutter must be compiled with support for remote desktop and it relies on gnome-remote-desktop/pipewire (not core yet I think?).
Hopefully there's some movement on before gnome-shell 3.34, so we might see support included in atspi2. I'll keep an eye on this though, thanks for the link :)
andyholmes
on 2 May 2019
Pipewire support in Mutter 3.32 seems to be enabled by default, judging by how Arch Linux packages it at least.
auscompgeek
on 3 May 2019
It's hard to tell for sure without spinning up some VMs, but Ubuntu seems to explicitly build mutter without remote desktop support, although it's probably on in Fedora.
If it's used by atspi2 we can be sure it will be available, but otherwise we will rely on pipewire, gnome-remote-desktop and gnome-shell >= 3.32. gnome-remote-desktop seem to still be living in a private repository, which is why I don't think it's considered core yet.
A proof-of-concept would be nice here. Implementing a low-latency client for the DBus interface (or two) in GJS might have some performance issues. AT-SPI is also effectively a DBus wrapper, but we use the C library so it's not too bad.
andyholmes
on 3 May 2019
Does the built in mouse accessibility support for gnome-shell/mutter 3.34 that just landed help with this?
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/474
https://gitlab.gnome.org/GNOME/mutter/merge_requests/512
jnsh
on 7 Jun 2019
Does the built in mouse accessibility support for gnome-shell/mutter 3.34 that just landed help with this?
What we really need is for AT-SPI to be supported on Wayland. There seems to be some movement in atspi2-core lately, but we'll have to wait until those changes propagate to see if AT-SPI will work on Wayland.
andyholmes
on 7 Jun 2019
BAM! (needs testing)
andyholmes
on 8 Oct 2019
I see a codename for v27 shaping up: "GSConnemeril Edition".
ferdnyc
on 8 Oct 2019
Has anyone else actually been able to get this working? It doesn't seem to work for me on Arch Linux (despite seeing "screen is being shared" in the system menu).
auscompgeek
on 13 Oct 2019
Just had a look through the dogtail stuff. Looks like you also need to set a dconf key for this to work. (No restart necessary.)
gsettings set org.gnome.desktop.interface toolkit-accessibility true
# or
dconf write /org/gnome/desktop/interface/toolkit-accessibility true
Related issues
danieldeng2
·
4Comments
jorgecodecom
·
6Comments
sk0gen
·
4Comments
AngusLogan02
·
4Comments
ricvelozo
·
4Comments
Most helpful comment
BAM! (needs testing)