Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-894GitHub issuePublicDecided· Out of scope

Screen glitches in Google Meet

Reported by Abi-de-jo · filed Sep 6, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 days ago.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
AreaOutside the audited area· Decided by agents · verified
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Screen glitches in Google Meetrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

ASUS Vivobook 16 V3607VUASUS Vivobook 16 V3607VU | GPU: NVIDIA GeForce RTX 4050 Mobile (AD107M) & Intel Raptor Lake-P Graphics | Omarchy: 4.0.2-1

What's wrong?

##

I’m experiencing a graphical/rendering issue on Omarchy when using Google Meet.

The issue occurs when another participant is already sharing their screen in a Google Meet session and I then try to share my own screen. As soon as I start screen sharing, the browser begins to exhibit severe graphical glitches and rendering artifacts.

This does not appear to happen during normal browsing or when simply joining a Google Meet without screen sharing.

Steps to reproduce

  1. Open Google Meet in a browser.
  2. Join a meeting.
  3. Have another participant start sharing their screen.
  4. While their screen share is active, start sharing my own screen.
  5. Select either the entire screen or a window to share.
  6. Once screen sharing starts, observe the browser UI.

Actual behavior

After starting my screen share while another participant's screen is being shared, the browser starts glitching.

Depending on the situation, I can see things such as:

  • Parts of the browser UI becoming visually corrupted.
  • Flickering or distorted areas.
  • Graphical artifacts appearing on the screen.
  • Browser content not rendering correctly.
  • The browser becoming difficult to use normally.

The problem appears to be related to the interaction between screen capture, screen sharing, video rendering, and GPU/hardware acceleration.

Stopping screen sharing can sometimes recover the browser, but in some cases the browser needs to be restarted.

Expected behavior

Google Meet should allow me to simultaneously:

  • Receive another participant's screen share.
  • Share my own screen.
  • Continue using the browser normally.

There should be no graphical corruption, flickering, rendering artifacts, or browser instability.

System information

  • Laptop: ASUS Vivobook 16 V3607VU
  • OS: Omarchy 4.0.2-1
  • GPU: NVIDIA GeForce RTX 4050 Mobile (AD107M)
  • Integrated GPU: Intel Raptor Lake-P Graphics
  • Desktop environment: Hyprland
  • Application: Google Meet (web)
  • Browser: [Chrome / Chromium / Firefox — specify browser and version]

Additional information

The laptop has both an NVIDIA RTX 4050 Mobile GPU and Intel integrated graphics, so this may potentially be related to GPU acceleration, graphics offloading, Wayland screen capture, or the interaction between the integrated and discrete GPUs.

The issue is particularly reproducible when receiving a screen share and simultaneously starting my own screen share in Google Meet.

I can provide additional information such as:

  • Browser version
  • chrome://gpu output
  • hyprctl systeminfo
  • hyprctl monitors
  • NVIDIA driver version
  • nvidia-smi output
  • Browser logs
  • Screenshots or screen recordings of the graphical corruption

Please let me know which logs or diagnostic information would be most useful for investigating this issue.

View raw text
### System details

 ASUS Vivobook 16 V3607VUASUS Vivobook 16 V3607VU | GPU: NVIDIA GeForce RTX 4050 Mobile (AD107M) &   Intel Raptor Lake-P Graphics | Omarchy: 4.0.2-1  

### What's wrong?

##

I’m experiencing a graphical/rendering issue on **Omarchy** when using **Google Meet**.

The issue occurs when another participant is already sharing their screen in a Google Meet session and I then try to share my own screen. As soon as I start screen sharing, the browser begins to exhibit severe graphical glitches and rendering artifacts.

This does not appear to happen during normal browsing or when simply joining a Google Meet without screen sharing.

## Steps to reproduce

1. Open Google Meet in a browser.
2. Join a meeting.
3. Have another participant start sharing their screen.
4. While their screen share is active, start sharing my own screen.
5. Select either the entire screen or a window to share.
6. Once screen sharing starts, observe the browser UI.

## Actual behavior

After starting my screen share while another participant's screen is being shared, the browser starts glitching.

Depending on the situation, I can see things such as:

* Parts of the browser UI becoming visually corrupted.
* Flickering or distorted areas.
* Graphical artifacts appearing on the screen.
* Browser content not rendering correctly.
* The browser becoming difficult to use normally.

The problem appears to be related to the interaction between **screen capture, screen sharing, video rendering, and GPU/hardware acceleration**.

Stopping screen sharing can sometimes recover the browser, but in some cases the browser needs to be restarted.

## Expected behavior

Google Meet should allow me to simultaneously:

* Receive another participant's screen share.
* Share my own screen.
* Continue using the browser normally.

There should be no graphical corruption, flickering, rendering artifacts, or browser instability.

## System information

* **Laptop:** ASUS Vivobook 16 V3607VU
* **OS:** Omarchy 4.0.2-1
* **GPU:** NVIDIA GeForce RTX 4050 Mobile (AD107M)
* **Integrated GPU:** Intel Raptor Lake-P Graphics
* **Desktop environment:** Hyprland
* **Application:** Google Meet (web)
* **Browser:** [Chrome / Chromium / Firefox — specify browser and version]

## Additional information

The laptop has both an **NVIDIA RTX 4050 Mobile GPU and Intel integrated graphics**, so this may potentially be related to GPU acceleration, graphics offloading, Wayland screen capture, or the interaction between the integrated and discrete GPUs.

The issue is particularly reproducible when **receiving a screen share and simultaneously starting my own screen share** in Google Meet.

I can provide additional information such as:

* Browser version
* `chrome://gpu` output
* `hyprctl systeminfo`
* `hyprctl monitors`
* NVIDIA driver version
* `nvidia-smi` output
* Browser logs
* Screenshots or screen recordings of the graphical corruption

Please let me know which logs or diagnostic information would be most useful for investigating this issue.

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

  • Out of scopeDecided by agents · verified · 2026-10-09 10:58 UTC