Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Screen sharing blank while using E2EE ("Could not handle E2EE for LocalTrack") #2547

Open
lyoungsdigi opened this issue Jul 23, 2024 · 3 comments

Comments

@lyoungsdigi
Copy link

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:

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:

  1. Open a conference on https://meet.jit.si and turn the camera on from the lobby screen before joining.
  2. Enable E2EE from the security options.
  3. Start sharing your screen.
  4. 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:

  1. Open a conference on https://meet.jit.si and turn the camera on from the lobby screen before joining.
  2. Start sharing your screen.
  3. Join a second client to the call. Screen sharing should work as expected.
  4. Turn on E2EE. Note the console warning and blank screen on the receiving client.

Environment details


  • Current production site @ https://meet.jit.si
  • Google Chrome, Version 126.0.6478.183 (Official Build) (64-bit) on Windows 10
@jallamsetty1
Copy link
Member

@lyoungsdigi Thanks for the report, we are looking into it.

@iospro
Copy link

iospro commented Sep 8, 2024

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

@jallamsetty1
Copy link
Member

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants