4 ms·

Zoom. I can't share my screen. If it works, it has way less options than in x11. You can't share a display or app, only a region. Autokey shortcuts don't seem

Zoom. I can't share my screen. If it works, it has way less options than in x11. You can't share a display or app, only a region. Autokey shortcuts don't seem to trigger on Wayland, works with x11 Parcellite, I can't make it show up with shortcuts. Those are the ones that made me revert to x11

oxplot 5y ago
As someone mentioned, looks like https://wiki.archlinux.org/title/PipeWire#WebRTC_screen_sharing https://wiki.archlinux.org/title/PipeWire#WebRTC_screen_shar... solves the screen casting issues.
kaba0 5y ago
You can’t take a screenshot is different than Zoom not being able to. You basically can take screenshots/record your screen in every major wayland compositor. On the other hand, screen recording by applications require interfacing with pipewire, which is pretty much done by many programs (including chrome (and thus electron), firefox, obs, etc), but plenty electron apps do not use the necessary flag. If you don’t want to tinker with rebuilds I recommend using the web version of zoom in an up-to-date browser.
- josefx 5y ago
  > On the other hand, screen recording by applications require interfacing with pipewire, which is pretty much done by many programs And why doesn't xwayland support it out of the box? Is crippling existing X11 programs intentional or is it just an inherent limitation of the way wayland works?
  - kaba0 5y ago
    Because seeing other windows is a fundamentally privileged action. Also, the implementation of xwayland is basically a nested X - so by using the X screen recording api, it will simply see other X windows.
jeroenhd 5y ago
The Zoom issue is related to the API they chose to use on Wayland. There's an API for sharing stuff like screens and windows, but Zoom is calling the GNOME (not even standard) screenshot API in a loop instead. As you might expect, that doesn't exactly work smoothly; performance is lacking and window coordinates would need to be tracked manually. There's a whole thread about it here (https://community.zoom.com/t5/Meetings/Wayland-screen-sharing-broken-with-GNOME-41-on-Fedora-35/m-p/22539 https://community.zoom.com/t5/Meetings/Wayland-screen-sharin...) but I don't think Zoom cares enough about their Linux client to fix these issues. I don't know about the shortcut issues you're facing, my guess would be the key logger protections built into wayland prevent your shortcut daemon from capturing the necessary keys. Autokey certainly runs into that problem (https://github.com/autokey/autokey/issues/87 https://github.com/autokey/autokey/issues/87). Other programs seem to get similar features working, but not everyone had the time or expertise to bring out compatible versions of their software.

oxplot 5y ago

As someone mentioned, looks like https://wiki.archlinux.org/title/PipeWire#WebRTC_screen_sharing https://wiki.archlinux.org/title/PipeWire#WebRTC_screen_shar... solves the screen casting issues.

kaba0 5y ago

You can’t take a screenshot is different than Zoom not being able to. You basically can take screenshots/record your screen in every major wayland compositor. On the other hand, screen recording by applications require interfacing with pipewire, which is pretty much done by many programs (including chrome (and thus electron), firefox, obs, etc), but plenty electron apps do not use the necessary flag. If you don’t want to tinker with rebuilds I recommend using the web version of zoom in an up-to-date browser.

josefx 5y ago
> On the other hand, screen recording by applications require interfacing with pipewire, which is pretty much done by many programs And why doesn't xwayland support it out of the box? Is crippling existing X11 programs intentional or is it just an inherent limitation of the way wayland works?
- kaba0 5y ago
  Because seeing other windows is a fundamentally privileged action. Also, the implementation of xwayland is basically a nested X - so by using the X screen recording api, it will simply see other X windows.

jeroenhd 5y ago

The Zoom issue is related to the API they chose to use on Wayland. There's an API for sharing stuff like screens and windows, but Zoom is calling the GNOME (not even standard) screenshot API in a loop instead. As you might expect, that doesn't exactly work smoothly; performance is lacking and window coordinates would need to be tracked manually. There's a whole thread about it here (https://community.zoom.com/t5/Meetings/Wayland-screen-sharing-broken-with-GNOME-41-on-Fedora-35/m-p/22539 https://community.zoom.com/t5/Meetings/Wayland-screen-sharin...) but I don't think Zoom cares enough about their Linux client to fix these issues. I don't know about the shortcut issues you're facing, my guess would be the key logger protections built into wayland prevent your shortcut daemon from capturing the necessary keys. Autokey certainly runs into that problem (https://github.com/autokey/autokey/issues/87 https://github.com/autokey/autokey/issues/87). Other programs seem to get similar features working, but not everyone had the time or expertise to bring out compatible versions of their software.