User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:74.0) Gecko/20100101 Firefox/74.0

Steps to reproduce:

1. Open Firefox
2. Open https://mozilla.github.io/webrtc-landing/gum_test.html
3. Select Screen Capture
4. Allow any Window or entire Screen
5. Moving mouse over Windows or Desktop

Actual results:

Mouse pointer is invisible

Expected results:

Mouse pointer is visible

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

I'm having the same issue, and I had reported it in the KDE bug-tracker (https://bugs.kde.org/show_bug.cgi?id=436771), but was asked to do so here, and found this bug.

The mouse pointer isn't visible when sharing screen, whether specific windows, or the whole display. This is so with both Zoom as well as Google Meet.

Is that Wayland/Pipewire or X11?

You're right, I do see it with PipeWire enabled. I'm not sure if it's even possible to share the mouse cursor.

When you say that you do see it, you mean that you see the issue, right?

Why is it not possible with Wayland? Does the protocol not allow for that?

Yes I see the bug on Wayland. On Wayland we just display what we get - we don't have any control over the data we display. So it's perhaps a bug of PipeWire sharing system.

Gnome issue is tracked here: https://gitlab.gnome.org/GNOME/mutter/-/issues/1184

A comment in that link says:

If I share only current tab through Google Chrome, both the screen sharing and the mouse cursor work as expected.

So is Chrome doing something different that allows them to share the pointer as well?

There is a closed issue on the Pipewire bug-tracker about the same:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/571

But obviously, they don't seem to think its an issue at their end, but I've commented there anyway.

(In reply to physkets from comment #9)

A comment in that link says:

If I share only current tab through Google Chrome, both the screen sharing and the mouse cursor work as expected.

So is Chrome doing something different that allows them to share the pointer as well?

Chrome is not running under Wayland/Pipewire, it uses direct access to X11. Firefox supports both backends, X11 and Wayland.

I'm not sure if you're also running Wayland, please attach content of your about:support.

Yes, I see you're running Wayland here, it means screen sharing is done via PipeWire so the https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/571 apply to you.

I expect Chrome shows the mouse cursor only when you share Chrome window, not when you share system screen or different window, right?

so the https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/571 apply to you.

Ya, but they've "Closed" the issue, implying that there's not problem at their end, correct? Or is there?

Should I open a new issue with them?

I expect Chrome shows the mouse cursor only when you share Chrome window, not when you share system screen or different window, right?

• When sharing the "entire screen", the audience only sees a black, blank screen, BUT with the mouse visible; nothing else.
• When I try to pick a window, only X11 windows are presented as options. None of the Wayland applications (including Chromium itself) are available for selection.
• When I use the Chromium tab sharing option, it shares it properly, along with the mouse.

Note that in trying this, I used Chromium with its Wayland backed (Ozone).

I forgot to add that in scenario (2), when sharing specific X11 windows, the mouse is visible when I move it inside that window.

Please reopen the PipeWire issue or create a new one and post the link here. I believe it needs to be fixed on PW side.
Thanks.

Done: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1236

But like someone in the same issue in Mutter's tracker pointed out, OBS-Studio is able to record the mouse cursor without any issue, and they're using pipewire: https://github.com/obsproject/obs-studio/blob/master/plugins/linux-capture/pipewire.c

Pipewire has confirmed that this is an issue with Firefox. Cursor metadata support has to be implemented:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1236#note_1337102

(In reply to physkets from comment #19)

Pipewire has confirmed that this is an issue with Firefox. Cursor metadata support has to be implemented:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1236#note_1337102

Also affected by this and looking for a fix.

Do you know if the issue has been reported on the Firefox bug tracker, by any chance?

Thanks