Visual Studio Code 1.122.1 finally patches a bug that forced Linux users into an unwanted screen sharing permission loop every time the editor launched. The culprit was core workbench code triggering media capture requests during startup, which completely broke normal boot behavior on KDE Plasma 6 Wayland sessions. Updating to this release fixes the issue by tying the prompt strictly to explicit user actions like recording bug reports instead of firing automatically. Staying on version 1.122.0 guarantees repetitive permission dialogs that waste time and annoy privacy focused workflows, so grabbing the update is the only sensible move.

Visual Studio Code 1.122.1 Fixes That Annoying Screen Sharing Prompt on Linux

Visual Studio Code 1.122.1 drops today to squash a persistent bug that forced Linux users into an endless screen sharing permission loop every time the editor launched. The issue specifically targeted KDE Plasma 6 Wayland sessions and triggered unnecessary D-Bus calls during startup. This update restores normal boot behavior without requiring workarounds or fresh profiles.

Why the Screen Share Prompt Appeared at Boot

The root cause traced back to how the application handled media capture services during initialization. A function meant strictly for the issue reporter wizard fired automatically when the interface loaded. This triggered the screen cast portal on Wayland sessions, forcing KDE Plasma to request permission before the desktop environment finished drawing. Attempts to block the behavior through command line flags or clean installation directories failed because the faulty call lived inside core workbench files rather than extension code. The editor essentially asked for recording rights before it actually needed them, which broke trust with privacy focused Linux users and made every startup feel like a security audit gone wrong. IT teams managing fleet deployments often notice this behavior immediately after users migrate from X11 to Wayland sessions, since the display server handles permission requests differently under the hood.

How Visual Studio Code 1.122.1 Resolves the Issue

The patch removes the premature media capture request from the startup sequence. By moving the screen cast logic to only trigger when a user explicitly clicks the recording button, the application respects session boundaries and avoids unnecessary D-Bus traffic. This change aligns with how modern Linux desktop environments expect applications to handle hardware access. Users running Fedora based distributions or Arch derivatives will notice immediate stability improvements during boot. The fix also applies cleanly to insider builds without requiring manual bundle edits or feature flags.

What Happens If You Stay on Version 1.122.0

Remaining on the previous release guarantees a repetitive permission dialog every single time the application starts. This behavior drains system resources by repeatedly querying display servers and confuses users who assume their editor respects privacy defaults. Some administrators tried routing around the problem with environment variables or custom desktop entries, but those methods only masked symptoms rather than fixing the underlying code path. Updating to the latest build eliminates the need for manual intervention and restores expected launch behavior across all supported Linux distributions.

Release Visual Studio Code 1.122.1

The update addresses these issues https://code.visualstudio.com/updates/v1_122

Release Visual Studio Code 1.122.1

Grab the update when you get a chance. The editor works better when it stops asking for permission before it even opens.