GPL Enforcement on Trial: Whose Freedom Is It, the Vizio Case Asks
[Navigation links: not applicable. Linux Wednesday is in its post-arc, news-driven phase; the 20-episode memoir arc concluded at Episode 18. No Part 0 table of contents link is standing for this phase.]
I spent years inside Novell during the Linux Wars, when a licence clause could end up worth more than the code it covered. That is where I first learned that the GNU General Public License's famous promise, you may have the source code, you may study it, modify it, redistribute it, is only ever as real as somebody's ability to make a court enforce it. Episode 9 of this series told the story of SCO demanding a billion dollars from IBM over claims that Unix code had ended up inside Linux. Episode 11 told the story of Novell's own decades-old Unix copyrights turning out to be the thing that stopped SCO cold. Both cases were, underneath the headlines, arguments about who gets to make a licence mean something.
On 10 August 2026, a jury in Orange County, California, was reported to have begun hearing a case that finally puts a version of that question to a jury rather than to a judge's opinion alone [6]. Software Freedom Conservancy says Vizio has been selling GPL-licensed smart TVs since at least 2018 without ever handing over source code that actually compiles. The open question in this trial is not really whether Vizio kept its promise. A judge has already found, on a narrow point, that it did not. The open question is who, other than Vizio itself, gets to make that promise mean anything at all.
Software Freedom Conservancy (SFC) is a small non-profit whose whole purpose is making sure the promise behind free and open source licences actually gets kept. Its case against Vizio, filed in Orange County Superior Court, is not a copyright claim. It is a breach of contract claim, built on the argument that when Vizio distributed televisions loaded with GPLv2 and LGPLv2.1 licensed code, it made a binding promise to whoever bought one: here is the source code, in full, in a form you can actually compile [1].
Vizio's SmartCast platform is built on a distribution of Linux called Ubuntu, running as a layer over a second Linux kernel supplied by the television's chip vendor. Every named Vizio smart TV, in other words, contains two separate Linux kernels. SFC's complaint lists fourteen GPLv2-covered programs bundled inside, including two versions of the Linux kernel itself, GNU bash, BusyBox, coreutils and GNU tar, plus eleven LGPLv2.1-covered libraries, among them the GNU C Library, FFmpeg, glib and systemd [1].
The compliance history, as SFC tells it, runs for years. A staff member bought a Vizio TV in March 2018 and found no source code and no written offer in the box. SFC wrote to Vizio's chief technology officer and general counsel that August; Vizio promised code by the end of the year. What followed, according to the complaint, was six separate "complete" source code submissions between January and December 2019, and not one of them would compile. A phone call in December 2019 produced fresh assurances. A final message in January 2020 promised more once Vizio's chip supplier had, in Vizio's own words, "more substantial updates." SFC followed up six more times over the next five months. Vizio never replied again. When SFC bought three further Vizio models in 2021 specifically to retest compliance, the pattern held. No source code arrived, and the offer buried inside the television's own settings menu does not, SFC argues, meet the GPL's requirements for a valid written offer [1].
Two rulings have come out of this case so far, and it is worth being precise about what each one actually decided, because the gap between what a ruling says and what people claim it means is most of the story to date.
In December 2023, the court rejected Vizio's argument that copyright law alone governs this dispute, and it excluded Vizio's central textual defence, an old FAQ page suggesting only copyright holders can enforce the GPL, as inadmissible hearsay. The court found the central question, whether an ordinary buyer counts as a third party beneficiary of the licence and can therefore sue over it, is a genuine dispute of fact for a jury to decide, not something a judge could settle on the papers [2].
In December 2025, Vizio won a narrower point: nothing in the licence text requires Vizio to guarantee a modified television keeps working after somebody installs their own version of the source code. SFC, in its own public statement on the ruling, was blunt that this settles nothing it actually argued. Vizio must still, on the court's own reading, provide code that can be "obtained and revised... for use in other applications" [3]. Whether Vizio has actually done that, and whether SFC has the standing to force it, remained open questions when the jury trial the case had been heading toward all along was reported to have opened on 10 August 2026 [6].
SFC's own filing states the stakes without much decoration: if an ordinary purchaser cannot enforce the source code promise, "no one other than the purchaser has both the information and motive to enforce" it [1]. The Free Software Foundation, whose decades-old FAQ language sits at the centre of Vizio's argument, was subpoenaed to testify, and has since revised that FAQ to make clear it also encourages using any legal mechanism available to obtain source code, not only litigation brought by a copyright holder [4]. Even the licence's own steward organisation, in other words, has a direct stake in how this comes out.
SFC's complaint also offers a business reason for Vizio's years of half-delivered code. Vizio reported close to US$300 million in gross profit from its advertising and data business in 2022, against roughly US$15 million from selling the hardware itself. A firmware update that let owners genuinely modify their televisions would touch the very software that makes that advertising business work. That is SFC's argument for motive, not a finding any court has made, and the distinction matters. Vizio does have direct history with the underlying data practice: the US Federal Trade Commission fined it US$2.2 million in 2017 for collecting viewing histories from more than eleven million televisions without consent [5].
Even Linus Torvalds, who wrote the kernel both sides are arguing about, was reported to have publicly declined to take either side after the December 2025 ruling, criticising Vizio's years of non-delivery while also suggesting SFC had reached too far in parts of its own case [7]. That is a useful correction against reading this as a clean story with an obvious hero. Two imperfect parties are litigating a genuinely open legal question, and a jury, not a licence FAQ or a blog post, is the one who gets to answer it.
None of this is abstract if you have ever signed off on a vendor contract that references open source components without checking what obligations travel with them. A software bill of materials exists precisely so an organisation can answer, honestly, whether it has met its licence obligations rather than assumed a vendor has. The Vizio case is what happens when nobody checks for six straight years and then somebody finally does. If your organisation embeds GPL or LGPL licensed code in a product it ships, the lesson sitting inside this trial is simple: know which licence terms travel with which component, and know who, other than your own legal team, has standing to ask you to prove it.
Two weeks before the Vizio trial opened, the European Union's Right to Repair Directive became applicable across all twenty seven member states, requiring manufacturers to offer repair, at a reasonable price and within a reasonable time, even after the warranty has expired, and even for products already on shelves before the deadline [9]. It is a different legal instrument aimed at a related question: not who can enforce a software licence, but whether ownership includes a right to keep the thing working and modifiable on your own terms.
New Zealand had its own version of that question in front of Parliament in the same window. Stated plainly, rather than interpreted: a Consumer Guarantees (Right to Repair) Amendment Bill, which would have required manufacturers to make repair parts, tools, software and information available to consumers, passed its first reading and went to select committee. Of the 1,250 submissions the committee received, 95 per cent supported the bill. The committee nonetheless recommended, by majority, that it not proceed [8]. This article takes no position on why the numbers moved the way they did. The fact worth carrying forward is that the same underlying question, whether ownership includes the right to keep a thing working and modifiable, was being tested in three places at once: a Californian jury box, an EU compliance deadline, and a select committee report.
None of this has anything to do with artificial intelligence on its face, and this episode does not need it to. But there is a genuinely open question one step further down the road that a third party beneficiary ruling in SFC's favour would quietly reshape. Open weight AI models increasingly ship under licences modelled on copyleft, community licences and various responsible AI licences among them, promising downstream users certain rights for certain obligations. No court has yet asked whether an ordinary user of one of those models, rather than the company that trained it, could enforce that promise the way SFC is trying to enforce the GPL's. If a jury decides an ordinary purchaser can stand in a copyright holder's shoes to enforce a licence they never individually negotiated, the reasoning does not automatically travel to a different licence text in a different domain. But it becomes available as precedent for someone to try. That is not a legal fact yet. It is the shape of the next fight, and the GPL, thirty five years old this year, is still the licence writing the rules for how these fights get fought.
Strip away the smart TV and the litigation, and what is actually being fought over is a stack of ordinary, working open source infrastructure: the Linux kernel twice over inside a single television, GNU bash, BusyBox, coreutils and GNU tar, the GNU C Library, FFmpeg, glib and systemd, all maintained in the open, all inspectable by anyone who can get at the source. That inspectability is not a side effect. It is the entire mechanism by which a promise like the GPL's gets checked rather than taken on faith, and it is the same mechanism, openly maintained code that anyone can audit rather than a vendor's word, that decides who else ends up trusting a system it did not build.
The US Defense Information Systems Agency publishes Security Technical Implementation Guides for the Linux distributions running inside accredited defence systems, hardening baselines that assume the underlying source is genuinely auditable, not merely licensed. The Defense Federal Acquisition Regulation Supplement, in turn, preserves rather than overrides open source licence terms when that code ends up inside software built for the military, so a GPL obligation does not simply dissolve because the buyer wears a uniform. Whether an ordinary consumer can force a television manufacturer to honour that same obligation is, on the evidence so far, still genuinely unresolved in a California courtroom. Whether a defence acquisition office can, and does, is a question worth asking with exactly as much scrutiny.
- A licence promise is only as real as somebody's standing to enforce it. Check who actually holds that standing before you rely on one, in software or anywhere else.
- "Complete source code" and "a folder that does not compile" are not the same delivery. If you cannot build it, you have not received it.
- Watch this case regardless of the verdict. A jury ruling on third party beneficiary status will shape how the next generation of open source licences gets written, not just how this one gets read.
You have almost certainly agreed, at some point, to terms you never read, for a promise you had no real way to check was being kept. If you found out, years later, that it had quietly been broken the whole time, who did you expect to do something about it, and were you right?
The views expressed in this article are entirely my own, informed by morethan 30 years of professional experience in architecture, security, andtechnology leadership in New Zealand. They do not represent the views ofmy employer, any government agency, or the New Zealand government. Mycommentary on legislation and policy is analytical, drawing on publiclyavailable sources and my professional expertise in architecture, security,and AI governance. I follow the Public Service Commissioner's Code ofConduct for the Public Sector and social media guidance.
About the Author: Andreas Hamberger is a New Zealand-based enterprise architect and technology strategist. Over 30 years, he has moved from compiling kernels on a 486 to leading cloud, cyber, and AI transformation programmes across government, banking, transport, and aviation. He founded Yoper Linux, served as a technology specialist for Novell during the Linux Wars, and is the author of "Generative AI: Skynet or Heaven" and "Space Mafia." "A Concise History of Linux" chronicles the operating system that changed the world and the lessons it holds for the AI era. He can be reached at linux@linux.co.nz.
I use AI tools, including Sudowrite, Claude, Perplexity AI, DeepSeek AI,ChatGPT, Grok, Copilot, Openart and Gemini, as deliberate productiontools, not ghostwriters. This is consistent with my position: AI amplifieshuman judgement; it does not replace it. The frameworks, arguments, andeditorial decisions in this series are original work. AI accelerated theprocess. The thinking is mine.
[1] Software Freedom Conservancy, Inc. v. Vizio, Inc., First Amended Complaint, filed 10 January 2024, Orange County Superior Court. URL: https://usethesource.sfconservancy.org/tmp_vizio_docs/software-freedom-conservancy-v-vizio-first_amended_complaint-2024-01-10.pdf
[2] Superior Court of California, County of Orange, Minute Order, 29 December 2023, Case No. 30-2021-01226723-CU-BC-CJC (Judge Sandy Leal, Dept. C33). URL: https://sfconservancy.org/docs/Order_Denying_Vizio_Motion_for_Summary_Judgement_12-29-23.pdf
[3] Superior Court of California, County of Orange, Minute Order, 23 December 2025, Case No. 30-2021-01226723-CU-BC-CJC (Judge Sandy Leal, Dept. C33), including Software Freedom Conservancy's contemporaneous public statement on the ruling. URL: https://sfconservancy.org/static/docs/2025-12-23_SFC-vs-Vizio_30-2021-01226723-CU-BC-CJC_Leal-minute-order.pdf
[4] Free Software Foundation, "FSF to be deposed in SFC v Vizio, updates relevant FAQ entry," fsf.org, FAQ revision dated 29 April 2024. URL: https://www.fsf.org/news/fsf-to-be-deposed-in-sfc-v-vizio-updates-relevant-faq-entry
[5] Federal Trade Commission, "VIZIO to Pay $2.2 Million to FTC, State of New Jersey to Settle Charges It Collected Viewing Histories on 11 Million Smart Televisions without Users' Consent," press release, 6 February 2017. URL: https://www.ftc.gov/news-events/news/press-releases/2017/02/vizio-pay-22-million-ftc-state-new-jersey-settle-charges-it-collected-viewing-histories-11-million
[6] ppc.land, "The Vizio open-source trial that could shake the smart TV ad industry," retrieved August 2026. URL: https://ppc.land/the-vizio-open-source-trial-that-could-shake-the-smart-tv-ad-industry/
[7] FOSS Force, "After Vizio Ruling, SFC Pushes Back And Torvalds Weighs In," December 2025. URL: https://fossforce.com/2025/12/after-vizio-ruling-sfc-pushes-back-and-torvalds-weighs-in/
[8] Consumer NZ, "The Right to Repair bill now looks unlikely, but we won't give up." URL: https://www.consumer.org.nz/articles/the-right-to-repair-bill-now-looks-unlikely-but-we-wont-give-up
[9] Regulatory Decoded, "EU Right to Repair (Manufacturers) Directive 2024/1799." URL: https://regulatorydecoded.com/eu-right-to-repair-manufacturers-directive-2024-1799/