Skip to content
AnyKey Cafe Curiosity has a table here

OBS Ubuntu NVIDIA Fix

September 3, 2026

OBS Ubuntu NVIDIA Fix

PUBLIC ARCHIVE EDITION

Provenance

  • Provider: ChatGPT
  • Original title: OBS Ubuntu NVIDIA Fix
  • Conversation ID: 6990bb09-4090-8325-b133-31ccea044196
  • Created: 2026-02-14T10:12:26-08:00
  • Updated: 2026-02-14T10:14:01-08:00
  • Models: gpt-5-2
  • Source archive SHA-256: 0f7aee663dace8d779cc4e6f229b4e22a8386f8075b81801a3c8c2b112e1bdd7
  • Source transcript SHA-256: 938800fd33656d1050f6d86048dc06e98fe9168ff882f0b2cc7783e51e82fba8
  • Active-path treatment: active-current-node
  • Alternate messages preserved: 0
  • Attachment state: not-applicable
  • Privacy state: PRIVACY_VERIFIED
  • Publication state: public-archive
  • Record ID: chatgpt:6990bb09-4090-8325-b133-31ccea044196
  • Source member: conversations-001.json
  • Source record SHA-256: cf1f06b88b101d598f4e17f36a43496914952c8ab2fde2199dc9a38229f9a841
  • Transcript verification status: canonical-verified; privacy-verified; source-order-preserved
  • Editorial changes: privacy-approved local edits preserved
  • Publication/version history: public archive edition v1

Conversation

Darren — 2026-02-14T10:12:25-08:00

OBS stopped working for me just now….

ChatGPT — 2026-02-14T10:12:26-08:00 · gpt-5-2

Oof, that’s annoying timing 😅 Let’s get OBS back on its feet. Since you’re on Ubuntu + NVIDIA, here’s a tight triage flow that usually nails it fast:

Quick Triage (2 minutes)

1️⃣ Check if OBS actually launches from terminal
Open a terminal and run:

obs

If it errors, paste the error here. The message usually points straight to the culprit (missing lib, GL error, PipeWire, etc.).

2️⃣ NVIDIA driver sanity check
You already saw nvidia-smi fail earlier, so this is likely related.

nvidia-smi
  • ✅ If it works → good, move on
  • ❌ If it fails → OBS can crash or refuse to start

Quick fix:

sudo ubuntu-drivers autoinstall
sudo reboot

3️⃣ Wayland vs X11 (OBS + NVIDIA still hates Wayland sometimes)

Check:

echo $XDG_SESSION_TYPE

If it says wayland, try logging out and logging back in with “GNOME on Xorg”.
OBS is much more stable there, especially with NVIDIA + screen capture.

4️⃣ PipeWire / audio crash check

If OBS opens but audio devices are gone or it crashes when adding Mic/Desktop:

systemctl --user restart pipewire pipewire-pulse wireplumber

Then relaunch OBS.

If OBS Won’t Start at All

Reinstall OBS cleanly:

sudo apt remove --purge obs-studio
sudo apt install obs-studio

Or if you’re using Flatpak:

flatpak repair
flatpak run com.obsproject.Studio

Common Break Causes (what probably happened)

From what you described earlier, my bets are on:

  • 🎮 A game switched GPU profiles (Intel vs NVIDIA)
  • 🧩 NVIDIA driver partially unloaded
  • 🪟 GNOME session flipped (Wayland/X11 confusion)
  • 🔊 PipeWire glitch (audio stack crash)
  • 🔥 GL context failure after display reset

OBS is super sensitive to all of those.

Nuclear Option (if you just want it working now)

If you don’t want to debug and just want OBS usable:

sudo apt purge nvidia-*
sudo ubuntu-drivers autoinstall
sudo reboot

That fixes ~80% of “OBS suddenly broke” cases on Ubuntu + NVIDIA.

Tell me what you’re seeing

Two super useful bits:

obs
nvidia-smi

Paste whatever errors you get and I’ll laser-target the fix instead of guesswork.

We’ll get your recording rig back online. Linux yak-shaving continues, but at least this yak is familiar 🦬😆