Created attachment 152431 [details] screencast_double_cursor.png SUMMARY Cursor on wrong screen in pipewire screen capture STEPS TO REPRODUCE 1. I have two monitors, Firefox is opened with bigbluebutton on the left monitor. 2. Open a screencast on the right monitor OBSERVED RESULT When the cursor is on the left screen it is shown in the screencast although the screencast is of the right screen In the attachment you can see a screenshot of my left monitor with Firefox and bigbluebutton on it. As you can see my cursor is located on the sidebar of bigbluebutton and at the same time can be seen in the screencapture of my right screen which shows dolphin EXPECTED RESULT Cursor is shown on the correct screen in a screen capture SOFTWARE/OS VERSIONS git master as of 9/26/22, but I see this at least since 5.25.0 ADDITIONAL INFORMATION
I cannot reproduce it. I used https://mozilla.github.io/webrtc-landing/gum_test.html (Screen capture) for testing.
Are you on wayland or X11 though?
Created attachment 152432 [details] double_cursor2.png On wayland. I have this bug also with the tool you used. Obviously the real problem is that when I use screencasting the other people cannot see my mouse, as it is always on the wrong screen.
Created attachment 152433 [details] kwin_support.txt
Interestingly, it does seem to matter which screen I capture and on which screen firefox is. When I take a screencapture of my right screen with firefox on my right screen I cannot see the mouse at all in the capture (even when I move it to my left screen). When I then move firefox from my right screen to my left screen, I can again see the bug I originally described. Also, when I move my mouse now from the left to the right screen "the wrong mouse in the capture" gets stuck once my mouse crosses the screen border and stays visible in the capture.
I too have been unable to reproduce the problem. I'm surprised because my firefox (105.0.1) doesn't even request a cursor, so I don't really understand why yours does. Are you maybe running a development build? What distro are you on? If I force Plasma (XDPK) to send the cursor, it also does render it in the correct place. :(
Is your firefox running on X11 or Wayland?
I see the cursor appears sometimes when on "no-cursor" mode when hovering an Xwayland client. :|
My best guess so far is that Firefox is trying to get the cursor from X11 events and does a rather poor best guess. Please see if OBS or chromium* work for you. *chromium --enable-features=UseOzonePlatform,WebRTCPipeWireCapturer --ozone-platform=wayland
Firfox is running in X11 mode. Tested with obs, chromium, and chromium --enable-features=UseOzonePlatform,WebRTCPipeWireCapturer --ozone-platform=wayland and it works nicely. I had Aleix patch https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/128 (I know it's probably unrelated, just so you know) during all these tests enabled and verified that firefox is still showing the old behavior.
Firefox has outdated WebRTC with outdated screen sharing support. Luckily, the next Firefox release (106) will have rebased WebRTC and should be finally on par with Chromium and fix your issue. It's hard to say if the issue is now happening because of a bug in Firefox or because there is a bug when an embedded cursor is used (Firefox defaults to embedded cursor instead of metadata). This will be hard to verify as both OBS and Chromium defaults to use cursor metadata for better effeciency. Aleix, you can possibly try to patch OBS and try use embedded cursor instead of metadata. It should be just a matter of changing one value OBS sends to portals.
I can still reproduce this with Firefox 1.06 Operating System: Arch Linux KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 6.0.7-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT
I tested now also with firefox developer edition to make sure none of my settings/addons are responsible for this.
Firefox is still using old WebRTC code for screen sharing, even though they have the new one available. FF is blocked on https://bugzilla.mozilla.org/show_bug.cgi?id=1777345.
Is the issue still reproducible in 6.0.5 or 6.1 beta?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!