[Bug]: Google Meet says "You can't join this video call" for signed-out guests when canvas noise is on #2910

Closed
opened 2026-11-14 09:53:41 +00:00 by laaaax · 0 comments
laaaax commented 2026-11-14 09:53:41 +00:00 (Migrated from github.com)

Operating system

Windows

Version

0.21.3.1 (Chromium 157.0.8103.78)

Have you tested that this is not an upstream issue or an issue with your configuration?

  • I have tried reproducing this issue in Chrome and it could not be reproduced there
  • I have tried reproducing this issue in ungoogled-chromium and it could not be reproduced there
  • I have tried reproducing this issue in Helium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there

Description

Can't join Google Meet as a guest. Signed out, I get "You can't join this video call" and a few seconds later it sends me back to the home screen. Turning off #helium-noise-canvas fixes it.

Crash ID

No response

How to Reproduce?

  1. Default flags, open a Meet link while signed out of Google (same in a private window)
  2. Right away I get "You can't join this video call" with the countdown back to the home screen. I never even see the "Continue as guest" button
  3. Go to helium://flags/#helium-noise-canvas, set to Disabled, relaunch
  4. Open the same link again. Guest screen loads, "Continue as guest" works, I get to the waiting room
  5. Set the flag back to Enabled, relaunch, and the error is back

Actual behavior

Meet blocks signed-out guests before the guest join screen even shows. Same link works signed out in Brave on the same PC and network.

Expected behavior

Guest join should work with canvas noise on.

Additional context

Windows 11 24H2, everything else at default, Cloudflare secure DNS on. uBlock Origin is the only extension I have installed in Helium.

Toggling the canvas noise flag switches it both ways. Audio and hardware concurrency noise stayed on the whole time.

Brave works fine on the same machine. Haven't tried Chrome, ungoogled-chromium or a fresh profile.

Might be related:

Possible fixes: skip noise on small constant canvases like Mozilla did, or add a Meet exception like Brave did. I don't know if Meet checks the same thing in Helium, so that's a guess.

### Operating system Windows ### Version 0.21.3.1 (Chromium 157.0.8103.78) ### Have you tested that this is not an upstream issue or an issue with your configuration? - [ ] I have tried reproducing this issue in Chrome and it could not be reproduced there - [ ] I have tried reproducing this issue in ungoogled-chromium and it could not be reproduced there - [ ] I have tried reproducing this issue in Helium with a new and empty profile using `--user-data-dir` command line argument and it could not be reproduced there ### Description Can't join Google Meet as a guest. Signed out, I get "You can't join this video call" and a few seconds later it sends me back to the home screen. Turning off #helium-noise-canvas fixes it. ### Crash ID _No response_ ### How to Reproduce? 1. Default flags, open a Meet link while signed out of Google (same in a private window) 2. Right away I get "You can't join this video call" with the countdown back to the home screen. I never even see the "Continue as guest" button 3. Go to helium://flags/#helium-noise-canvas, set to Disabled, relaunch 4. Open the same link again. Guest screen loads, "Continue as guest" works, I get to the waiting room 5. Set the flag back to Enabled, relaunch, and the error is back ### Actual behavior Meet blocks signed-out guests before the guest join screen even shows. Same link works signed out in Brave on the same PC and network. ### Expected behavior Guest join should work with canvas noise on. ### Additional context Windows 11 24H2, everything else at default, Cloudflare secure DNS on. uBlock Origin is the only extension I have installed in Helium. Toggling the canvas noise flag switches it both ways. Audio and hardware concurrency noise stayed on the whole time. Brave works fine on the same machine. Haven't tried Chrome, ungoogled-chromium or a fresh profile. Might be related: - Brave had the same error for signed-out users and fixed it with a Meet exception delivered by component update: https://github.com/brave/brave-browser/issues/32836 - Firefox had it too with canvas randomization. They found Meet draws a tiny constant canvas, and the fix was to not randomize uniform canvases: https://bugzilla.mozilla.org/show_bug.cgi?id=1852541 Possible fixes: skip noise on small constant canvases like Mozilla did, or add a Meet exception like Brave did. I don't know if Meet checks the same thing in Helium, so that's a guess.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
imputnet/helium#2910
No description provided.