Linus Picked the Wrong Distro Again — And the Linux YouTubers Won't Let Him Forget It

You chose Pop OS on the single day it was going to cause an issue. And now you're choosing Pop OS when they just released a brand new desktop. If you had waited like three or four months, it probably would have been a lot better.

— Michael Tunnell, TuxDigital reaction video [2]

Tunnell explained the issue clearly: Pop!_OS has been a reliable recommendation for years because it handled Nvidia drivers cleanly and had Ubuntu as a friendly base. But System76 spent the last two years focused entirely on building Cosmic from scratch. The OS is now on version 1.0.8, barely three months post-launch. Tunnell called it "just too early" for most users. Silas was blunter: "Don't use Pop OS in 2026." [3] The cruel irony is that Linus has now managed to pick Pop!_OS at two terrible moments — first when a 24-hour Steam install bug destroyed his X server in 2022, and now when Cosmic is fresh enough to be experimental. Tunnell joked that Linus has a gift for worst-case timing that transcends normal probability.

Day 1: The Linus Curse Rides Again

Before Linus even got to gaming, he grabbed a drive from the LTT office that had an ancient Fedora 39 install on it — an OS that's been end-of-life for over a year. BIOS threw end-of-life warnings, secure boot enrollment was a confusing multi-step loop (involving typing "universal blue" as a password, which is exactly as weird as it sounds), and the whole process took far longer than the "15 minutes" Linus optimistically predicted. To be fair: he admitted the drive mix-up was entirely his fault. And once he had a clean install, the out-of-the-box experience was genuinely better than 2022. Audio peripherals detected immediately. The Roadcaster showed up without manual driver hunting. No going to manufacturer websites. That part worked. Then he tried to game. Left 4 Dead 2 — a first-party Valve title — crashed the moment he launched it. Mouse locked. Game frozen. Ctrl+Alt+Delete doing nothing (that's a Windows thing). He rejoined his squad on Windows while he figured it out. The fix was a single launch parameter: run the game with Vulkan instead of OpenGL. One line. Done. But as Tunnell noted: "This is a first-party Valve title. The bugginess is immediately apparent, and it's apparently been an issue since at least July of last year." [2] If Valve can't get their own games running smoothly by default on Linux, that's legitimately a problem. PUBG is fully borked — ProtonDB shows a "borked" rating as of two weeks ago. Helldivers 2 eventually worked, but only on controller after mouse input refused to register. Three copies of the Steam window somehow opened simultaneously and operated in sync. Audio routing sent game sound to S/PDIF instead of speakers, requiring a reboot to fix.

I wouldn't call today a success. But it also wasn't a complete failure.

— Linus Sebastian, LTT Linux Challenge Episode 1 [1]

Luke and Elijah: The Control Group

The contrast between the three participants is the most interesting subplot of the challenge. Elijah, on Bazzite, is having the smoothest experience by a significant margin. Bazzite ships with Steam pre-installed and Proton pre-configured. His SMB network share was auto-discovered. OBS worked immediately. Discord worked after install (yes, it threw a "high risk" warning about X11 keystroke capture — which is technically accurate but dramatically worded). He got Left 4 Dead 2 running fine on Day 1 with no crashes. Luke, on CachyOS, sits in the middle. He's been running Arch on his laptop for experimentation, so the curve is less steep. He's treating this as a deeper Arch experiment, specifically because the community flagged CachyOS as better for gaming. He chose a Btrfs filesystem with the Lemonade/Limine theme on install — which he first read as "Limeline," which is relatable. Silas, reacting to the video, flagged something worth noting: CachyOS on Btrfs is notably vulnerable to RAM errors. Bad RAM can cause Btrfs to corrupt itself and lock into read-only mode, requiring a full reinstall. His advice — run memtest before installing — is exactly the kind of critical knowledge that doesn't appear in beginner guides and only surfaces when something goes wrong. [3]

What This Actually Shows About Linux in 2026

Here's the bigger picture buried under all the troubleshooting: the 2026 challenge is already going better than 2022, despite looking chaotic on the surface. The 2022 disaster was a platform-level failure. A Steam install deleted the X server. That's a bug that fundamentally shouldn't exist, and the fallout from Linus's video directly contributed to the maintainers changing the dangerous "yes, do as I say" confirmation flag in Debian. The platform was genuinely broken in ways that weren't Linus's fault. In 2026, the problems are different in character. Left 4 Dead 2 needs a Vulkan flag. Cosmic is too new. Secure boot enrollment requires reading documentation. These are configuration issues and distro-selection mistakes — the kind of friction that exists on Windows and macOS too, just in different places. Tunnell called it directly: "There's no Linux curse. If you said 'Linus curse'... well. Your timing of stuff." [2] The reaction video community's tone has changed too. Four years ago, Linux YouTubers were defensive, framing LTT's problems as user error. This time, the commentary is analytical: "here's what he should have done differently, here's why the timing was bad, here's what actually works." That's a sign that both the platform and the community's confidence in it have matured. The real story isn't whether Linus survives the month. It's that Linux has reached a point where watching someone struggle with it generates interesting commentary rather than pure disaster content. Proton works well enough to fix a Valve game with a single flag. SMB shares auto-discover. Hardware just shows up. The baseline is genuinely higher.

The Month Ahead

Three weeks remain. Linus is committed to Pop!_OS and the Cosmic desktop despite the early turbulence — and honestly, that commitment might produce the most interesting content. Watching someone navigate a brand-new desktop environment in real time, with Linux YouTubers providing running commentary, is exactly the kind of thing that builds actual documentation for new users. Michael Tunnell has promised to react to every episode. The Linux YouTube community has appointed itself a panel of judges. They will have opinions. Many opinions. Loudly. If you want to follow the challenge through a developer lens — understanding why the choices matter, what the distros actually are, and where Linux gaming genuinely stands in 2026 — the reaction video ecosystem is doing the analytical work that the LTT format doesn't have room for. Start with Tunnell's reaction [2] for the technical breakdown. Watch Silas [3] for the more blunt take. And go watch the original LTT video [1] to understand what everyone is yelling about.