Linus Tech Tips finally published the long-awaited second part of its Linux Challenge, and the video lives up to its title: "The Good, the Bad, and the Ugly Side of Linux." Over the course of 18 minutes, Linus Sebastian, Luke Lafreniere, and Elijah Talbot break down what went right, what went wrong, and what surprised them during their first week of living with Linux as their daily driver. If you’ve ever considered ditching Windows for an open-source alternative, this capsule summary of their experience offers a realistic preview — warts and all.

Linus picks Pop!_OS and immediately regrets it

The trio started with distinct setups. Linus chose Pop!_OS, a Ubuntu-based distribution built by System76 that’s often recommended for people coming from Windows or macOS. But his reasoning wasn’t technical: “Linus WHY POP_OS!,” the chapter title reads, hinting at the self-aware cringe of picking a distro more for reputation than for specific need. He later spent time trying other distributions, which suggests Pop!_OS didn’t solve all his problems out of the box. The video doesn’t specify which distros he tested next, but the fact he needed to shop around tells you something about the state of out-of-the-box Linux for power users who also want simplicity.

Elijah’s network share and gaming headaches

Elijah ran into a show-stopping issue early on: a network share problem that blocked access to files on his local network. The chapter timestamp (3:26) gives only the headline, so the exact cause isn’t detailed, but network shares remain a notorious pain point on Linux, especially when mixing SMB shares from a Windows machine or NAS. Elijah also struggled with gaming, a perennial hurdle for Linux newcomers. Valve’s Proton and Steam Play have made huge strides, but not every title works. The video notes his gaming experience at 6:18, and the presence of an “immutable OS” discovery at 14:38 suggests he may have stumbled into a whole new category of Linux distributions — one that locks down the system files to prevent accidental breakage.

An immutable OS, like Fedora Silverblue or SteamOS itself, treats the root filesystem as read-only during normal operation. It’s great for stability and security but can be a shock for someone used to apt-getting their way out of any jam. For Elijah, it was a discovery that likely added a layer of complexity to an already challenging week.

Luke goes advanced and hits the NTFS wall

Luke, the most technically inclined of the group, tried some advanced stuff early on (chapter 4:38). That likely means manual partition work, custom kernel modules, or desktop environment swapping — because Luke later switched desktop environments, which is a rite of passage for any serious Linux user. The big problem, though, was NTFS. The “NTFS On Linux” segment at 5:20 is a reminder that Microsoft’s NTFS file system has always been a second-class citizen on Linux. While the kernel now includes a native NTFS driver (thanks to Paragon Software’s work), performance and reliability still lag behind ext4 or Btrfs. For someone dual-booting or sharing a drive with Windows, this remains a genuine friction point.

Video codec issues: who to blame?

The team also ran into video codec problems (chapter 7:00). On Windows or macOS, codecs like H.264, HEVC, or AV1 are handled automatically or through a store plug-in. On Linux, they often require manual installation of ffmpeg or proprietary packages, and some distributions make you jump through hoops to enable them due to patent concerns. The video asks “Who Should I Blame?” at 7:35 — a fair question. Is it the distro maintainer for not shipping patents? The hardware vendor for not writing a Linux driver? The upstream developer who refuses to implement MPEG LA royalty payments? Linux users have to answer these questions themselves, and that navigation cost is a real barrier.

Windows is bad, too

The panel acknowledged that Windows also has its problems. A chapter at 12:53 is titled “Windows Bad Also.” The point is familiar to anyone who’s used both: Windows forces updates, shows ads in the Start menu, collects telemetry, and occasionally breaks itself. Linux users trade those indignities for a different set of frustrations. Neither platform is perfect. The challenge was never about proving Linux is better — it was about seeing whether three experienced tech enthusiasts could make it work as a daily driver.

The open-source love remains

Despite the gripes, the video ends on a positive note. A chapter at 16:14 is titled “We Still LOVE Open Source!” and the subsequent segment encourages viewers to join in at home. That’s the real takeaway: Linux is not a polished product you buy. It’s a community-driven ecosystem where you’re expected to contribute, tweak, and sometimes break things. The Good is the flexibility and freedom. The Bad is the learning curve. The Ugly is the file-system hangups, codec dramas, and network share mysteries.

What we learned from week one

PT.2 ends with a promise that PT.3 was filmed the same day, so readers and viewers can expect the resolution soon. In the meantime, the Linux Challenge validates something SysCall News has reported before: the desktop Linux experience has improved dramatically in the last five years, but it still demands a level of technical patience that the average Windows user isn’t prepared to give. Linus’s distro hopping, Luke’s desktop environment swap, and Elijah’s gaming struggles are not anomalies. They are the standard onboarding process for anyone who tries to make Linux their primary OS without prior experience.

For those who love to tinker, that process is part of the fun. For everyone else, the challenge offers a clear-eyed warning: Linux can work, but it will make you work, too.