You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Screen sharing with E2EE enabled shows a black screen in certain circumstances, including sharing before another user joins or toggling E2EE mid-session. Reproducible on https://meet.jit.si.
Current behavior
When screen sharing with E2EE enabled, other users in the session see a black screen.
At the time of the issue, the sending client gets the following warning:
KeyHandler.js:159 2024-07-23T14:03:27.620Z [modules/e2ee/KeyHandler.js] <fo._setupSenderE2EEForTrack>: Could not handle E2EE for LocalTrack[2,video]: sender not found in TPC[id=1,type=JVB]
overrideMethod @ console.js:288
r @ Logger.js:155
_setupSenderE2EEForTrack @ KeyHandler.js:159
_onMediaSessionStarted @ KeyHandler.js:118
o.emit @ events.js:158
(anonymous) @ JitsiConference.js:2261
(anonymous) @ JingleSessionPC.js:978
(anonymous) @ strophe.umd.js:3396
run @ strophe.umd.js:2507
(anonymous) @ strophe.umd.js:3843
(anonymous) @ strophe.umd.js:3840
forEachChild @ strophe.umd.js:1502
_dataRecv @ strophe.umd.js:3838
_onMessage @ strophe.umd.js:6187
socket.onmessage @ strophe.umd.js:5920
Expected Behavior
Visible screen share or an error message.
Possible Solution
When this happens, under _setupSenderE2EEForTrack->pc.findSenderForTrack you can see it try to compare against an RTCRtpSender with null values for 'rtcpTransport' and 'track'. Presumably this is supposed to be the track for the screen share?
User can work around by toggling the screen off and back on.
Steps to reproduce
Repro by turning on E2EE prior to others joining:
Open a conference on https://meet.jit.si and turn the camera on from the lobby screen before joining.
Enable E2EE from the security options.
Start sharing your screen.
Join a second client to the call. Note the console warning and black screen for the "(name)'s Screen" tile on the receiving side.
Repro by turning on E2EE mid-session:
Open a conference on https://meet.jit.si and turn the camera on from the lobby screen before joining.
Start sharing your screen.
Join a second client to the call. Screen sharing should work as expected.
Turn on E2EE. Note the console warning and blank screen on the receiving client.
We also bump into black screen when share screen user comes after others. It's not permanent situation, but sometimes we need to re-enter the room to get share picture
@iospro Can you pls share some more details? Are you seeing this on meet.jit.si? What version of Chrome are you seeing this on? Have you tried with the latest?
Description
Screen sharing with E2EE enabled shows a black screen in certain circumstances, including sharing before another user joins or toggling E2EE mid-session. Reproducible on https://meet.jit.si.
Current behavior
When screen sharing with E2EE enabled, other users in the session see a black screen.
At the time of the issue, the sending client gets the following warning:
Expected Behavior
Visible screen share or an error message.
Possible Solution
When this happens, under _setupSenderE2EEForTrack->pc.findSenderForTrack you can see it try to compare against an RTCRtpSender with null values for 'rtcpTransport' and 'track'. Presumably this is supposed to be the track for the screen share?
User can work around by toggling the screen off and back on.
Steps to reproduce
Repro by turning on E2EE prior to others joining:
Repro by turning on E2EE mid-session:
Environment details
The text was updated successfully, but these errors were encountered: