Black, empty screen shared from wayland desktop session

Hi,

just a black screen is transmitted when Jami is instructed to share the screen or a part of it from GNOME 3 wayland sessions. From GNOME 3 Xorg sessions it works as expected, though.

I reproduce this with Jami packaged in Debian. My original bug report is in Debian's bug tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931285

Cheers - Bruno

Yes and it will be the same for a lot of Wayland applications that record the desktop. During a long time, Wayland didn't provide any API for doing such a thing (the only possible thing was to record your app)

https://obsproject.com/mantis/view.php?id=719 or https://github.com/foss-project/green-recorder/issues/82 for example. I don't want to use API from a DE such as GNOME here because it's only made for GNOME. The best thing for now is to use wlroots like https://github.com/ammen99/wf-recorder

Hi Sébastien,

thanks for providing insight into the wlroots alternative.

Hopefully I understood this correctly: from a quick research it seems that gnome-remote-desktop [1] uses pipewire [2] to capture the screen in GNOME sessions on wayland. Did you take this into consideration, too?

Cheers - Bruno

[1] https://wiki.gnome.org/Projects/Mutter/RemoteDesktop [2] https://pipewire.org/

Yeah but as you say, it's for GNOME, and this will not work on all DE. I don't want to implement all API for all DE.

added enhancement + 1 deleted label

@sblin Shouldn't the issue title show where we're going? My suggestion -> "Support Screen Sharing On Wayland Systems"

The PipeWire API is not bound to a specific desktop environment, is it? So would that be a possible solution?

@sblin What do you think about renaming the issue and solving it with PipeWire? Reference here https://git.jami.net/savoirfairelinux/ring-daemon/issues/13

In fact, I think this issue is a duplicate of https://git.jami.net/savoirfairelinux/ring-daemon/issues/13 because, yeah supports pipewire

However, everything seems broken on Wayland, few weeks ago, the latest gtkwebkit release breaks the client, see https://git.jami.net/savoirfairelinux/ring-client-gnome/issues/1100

Well, I'd rather say https://git.jami.net/savoirfairelinux/ring-daemon/issues/13 might be a solution to the problem in this issue, not a duplicate.

Do you have any idea how to solve https://git.jami.net/savoirfairelinux/ring-client-gnome/issues/1100? What is the practical consequence for current Wayland users?

https://git.jami.net/savoirfairelinux/ring-daemon/issues/13 is the current solution for that issue. Without this support, the problem is the same, that's why it's a duplicate

No I don't have any idea for now. Current result is that users on Wayland doesn't see the chatview, that's why it's tagged as Critical

https://git.jami.net/savoirfairelinux/ring-daemon/issues/13 is the current solution for that issue. Without this support, the problem is the same, that's why it's a duplicate

Okey, you're welcome to customize the labels/titles for the two issues. Do you think you/someone from your team can work on a solution?

No I don't have any idea for now. Current result is that users on Wayland doesn't see the chatview, that's why it's tagged as Critical

I see!

Do you think you can work on a solution?

In the following months. Not likely. Hopefully, the other issue on Wayland is way more problematic and must be fixed soon

added to epic &1 (closed)

I close in favor of https://git.jami.net/savoirfairelinux/ring-daemon/issues/13

closed