“Leave this Europe where they are never done talking of Man, yet murder men everywhere they find them, at every corner of their own streets, in every corner of the globe.” --Franz Fanon

  • 19 posts
  • 5 comments
Joined 7 months ago
Cake day: April 30th, 2026

The first question that gets asked of a Windows user switching to Linux is which distro to install, and for many years, that was the correct one. It used to decide whether your Wi-Fi card would work or your games would launch first try, but now, it has lost a lot of its weight, and I think that’s a good thing.

I’ve run many Linux distros on my desktop over the years, and I’ve settled on CachyOS for a multitude of reasons, but most of those are niche and specific to me. For someone who sees Ubuntu or Fedora and thinks it looks comfortable and welcoming, the best experience they can have on those distros can almost certainly match mine, and the only difference nowadays is defaults, most of which can be easily changed. That shift, more than any single distro getting better, is what gives 2027 a real chance of being the year Linux goes mainstream.

The parts you actually use are pretty much the same everywhere

Linux has most of what you need regardless of distro

Most new users will interact with parts of a Linux system that don’t belong to a single distro. Flathub is a great example of this, and it works as a shared app store across distros, so the same build of Firefox, OBS, or Discord installs and behaves the same way on Fedora, Mint, or an Arch derivative.

For gamers, Steam goes a step further by adding Proton, a compatibility layer that hands a Windows game a standardized set of libraries regardless of the distro running underneath. If I go to run something like Cyberpunk 2077 on a machine running Ubuntu and then one running vanilla Arch, so long as both have the proper GPU drivers, they should run and behave the same way.

The host distro mostly just supplies the kernel, those graphics drivers, and core services like audio. On AMD and Intel hardware, even GPU drivers are the same upstream kernel and Mesa code everywhere; distros differ mainly in how recent a version they ship. Add in the fact that many distros today support either KDE Plasma or GNOME, and what a newcomer might think of as “the OS” is largely a shared experience across dozens of distros.

There are still day-to-day distro differences I’ve run into, but they’re becoming less common as the years go by. For the Ubuntu 26.04 mini PC I run, Snap is the primary format for packages. It’s the default for installing software, and the App Center lists Snap and Deb packages but leaves Flatpak out until you add it yourself. On CachyOS, which is the OS on my main workstation, you’re pointed toward pacman and the wider Arch ecosystem, but you can easily install AppImages, too.

A lot of users probably won’t be picking a distro

Valve might be the reason for that

Perhaps the biggest shift we might see is that the choice of distro is made before the user enters the picture. Valve’s Steam Machine launched at the end of June 2026 running SteamOS, and anyone who buys one gets Linux without ever hearing or seeing the word “distribution.”

SteamOS 3.8 extended that to self-built PCs with AMD graphics, which would help those who want to experience it outside their Steam hardware do so. The scale is still quite modest, and the level to which other OEMs sell machines with Linux as the installed OS is still dwarfed by their Windows sales, but it’s trending upward.

Why 2027, specifically

Windows 10 is on the way out, for real this time

Every year has been the year of the Linux desktop. It’s obviously a bit of a running joke, but in late 2027, there may be an exodus from Windows 10 due to extended security support lapsing. Microsoft recently extended free consumer Extended Security Updates by another year, and coverage now ends on October 12, 2027. That makes late 2027 the real deadline for the large base of PCs that work perfectly well but can’t officially run Windows 11, and unless Microsoft drops the system requirements that bar these systems, it’ll be one of the best natural on-ramps for Linux that we’ve seen in a while.

You still probably shouldn’t dice-roll your distro

At least, not yet

Anti-cheat is the main barrier that gets brought up when it comes to Linux adoption by gamers, and it’s not unwarranted, but there’s growth on that front. Epic announced Easy Anti-Cheat Linux v2 in October 2026, with Fortnite as its first test. Epic hasn’t committed to a date, but if it lands in 2027, that’ll only add to the optimism surrounding the platform.

However, with that said, it also happens to be a reason why you shouldn’t just pick your distro blindly out of a hat. EAC Linux v2 requires Secure Boot and a kernel signed by an organization whose key Epic recognizes, and that list covers the big players like Canonical, Fedora, and Universal Blue distros. My desktop wouldn’t be a candidate, as CachyOS ships its own tuned kernel, so I wouldn’t be able to play, though the developers behind CachyOS are building one. The Steam Deck doesn’t meet the requirements yet either, though Epic says it’s talking with Valve to iron that out.

Then there’s Nvidia, which I’ve conveniently ignored thus far. Getting full performance out of your GPU still means using the proprietary driver, and each distro handles this a bit differently. There are some distros which provide dedicated install images with Nvidia drivers included, and others will install them automatically.

Choose based on support for the things you actually use

Distro choice mattering less than ever is a big part of why Linux could see real growth in 2027, and if you’re switching over from Windows yourself, it has never been easier. Pick a mainstream distro that has the desktop environment you’re looking for, get your apps from its software store and your games from Steam, and stop thinking about it.

System76 has led the charge for merging Linux and hardware for over 20 years. The company has evolved over that time and eventually settled on the Thelio line of desktop PCs. Now, they’re adding a new option to that lineup, a retooling of the original: the Thelio Prime.

The new Thelio Prime is a small form-factor Linux desktop that is the perfect size for a desk, a shelf, or even an entertainment center. While Thelio Prime might be small in size, it’s big in power. Sporting a desktop-class AMD Ryzen CPU, NVIDIA or AMD graphics, and up to 96GB of memory, this little beast can handle everything from everyday work all the way up to 4K gaming.

This new desktop, constructed entirely from aluminum and steel, has an internal volume of just 9.78 liters, which is 48.5 percent smaller than the original. The side panels of the Thelio Prime are smoked, tempered glass and are attached with embedded magnets, to make servicing and upgrades simple. The Thelio Prime is designed for both vertical or horizontal orientation and can be customized to fit your needs.

The specs of the Thelio Prime include an AMD Ryzen CPU, up to the 12-core Ryzen 9 9900X, 16GB AMD Radeon 9060 XT, 16GB NVIDIA RTX 5060 Ti, 12GB RTX 5070 GPU options, up to 96GB of memory, and up to 16TB of NVMe storage. The base system starts at $1,599 and can be purchased from System76.com.

Linux 7.3 is looking like it’ll be the new long-term support (LTS) kernel.

Greg Kroah-Hartman, one of the kernels’ key maintainers, intimated this in early November in a reply on the Linux Kernel Mailing List, discussing the status of Linux 7.4 and when it’s likely to be released.

In a reply to Linus Torvalds, who’d noted people were expecting Linux 7.4 to be designated an LTS (since it’s shaping up to a big release and longterm kernels are picked, partly, based on being a feature-filled one) he said he planned for 7.3 to be LTS.

“If people are trying to force features into 7.4 just to make it an LTS, that is the best possible reason NOT to make it an LTS”, he said, noting that when this has happened in the past it has caused ‘a lot of trouble’ for maintainer.

Rather, he said, developers should “count on 7.3.y to be the next LTS” unless something comes along to scupper plans.

Not quite an inked rubber stamp of a decision, but firm enough to be the impression of one. LTS kernels get fixes for longer

Linux LTS kernels receive maintenance for a much longer duration than a standard stable release (at least 2 years) and receive backports of important bug and security fixes.

As Linux is used across businesses, industry and cloud, many opt for longterm versions for dependability. An LTS kernel’s support window can be extended beyond the initial 2 years if there’s demand (and help) for it from the wider community.

As of writing the kernel releases table doesn’t list v7.3 in the LTS table, but as there hasn’t been a point release since Kroah-Hartman’s message, it’s presumably why.

Linux 7.3 shipped in Ubuntu 26.10 and is back-ported to 26.04 later this year. Among its changes was better gaming on AMD GPUs with low VRAM, faster ext4 I/O and a reworking in how the kernel splits CPU time between groups of apps.

Linux 7.4(.0) is tentatively due on 27 December 2026.

Werner Koch announced a late Friday afternoon “critical security bug” affecting GnuPG’s GPGME library - GnuPG Made Easy. Unfortunately this in turn affects GPGME users like most email clients, most XMPP clients, Flatpak, Samba, and other software.

This critical security bug made public today affects all existing releases of GnuPG Made Easy. A crafted very long user ID can trigger a double-free that in turn can be used to extract data from applications by sending for example signed data. It’s also possible but not confirmed that this bug could be leveraged for mounting a remote code execution (RCE) attack.

Wener Koch is recommending GPGME users immediately update their GPGME to today’s version.

"By using an OpenPGP key containing a crafted very long user id it is possible to trigger a double free. This double free can be used exfiltrate data from applications by sending for example signed data. Exploiting this bug to mount an Remote Code Execution attack (RCE) can't be ruled out. Thus an immediate update is highly suggested.
...
The root cause for this bug are two GPGME internal functions to read the status lines and key listings from gpg. Initially a buffer of 1024 bytes is allocated which is reallocated if more space is required. When reallocating the pointer to the new buffer is used by the function but it is only assigned back to the context object at the end of the function. Thus if the function returns early due to an read error or other events the context is not updated and keeps the stale pointer to the freed memory. Eventually the context is released and the memory freed a second time. Due to other allocations in between the common double free checks of memory allocators may not be triggered."

All applications using existing GPGME versions whether as a shared library, DLL, or statically linked version are affected.

More details via the mailing list announcement. GPGME 2.3.1 is the first fixed version.

FreeDesktop.org has been the hosting hub for the X.Org project, Wayland, and the Mesa projects to other notable open-source Linux desktop projects like PipeWire, GStreamer, and countless other projects. Since it’s launch over two decades ago, it has basically looked the same… A bland Wiki. But on Friday a redesign of FreeDesktop.org was launched.

The main FreeDesktop.org web page has been refreshed as well as improving the FreeDesktop Wiki too. The FreeDesktop.org Wiki has moved to wiki.freedesktop.org.

Matthias Klumpp elaborated in the announcement their motivation for the design refresh:

"Since its inception, the freedesktop.org website was the wiki. Using a Wiki made the pages easy to edit, but it also meant that official project information, finished specifications, half-finished proposals and pages nobody had touched in fifteen years were all sitting next to each other. For people new to freedesktop.org it was often hard to tell what was current and what was merely still around. It also meant an increasingly harder fight to combat spam, which was one of the reasons to switch from MoinMoin to IkiWiki in 2013 (besides the former being based on the end-of-life Python 2).

To solve these issues, we split things up, and each of the two sites now has a clear job."

Further work on the Wiki and fixing up content is planned.

I would say the new FreeDesktop.org certainly looks more visually appealing than before and important given the central role of FreeDesktop.org in open-source Linux desktop software development.

Debian 13.8 is out today as the newest ISO refresh for Debian 13 “Trixie” with 150 security updates noted along with many bug fixes.

Debian 13.8 follows 150 Debian Security Advisories (DSAs) affecting popular software from Chromium to the Linux kernel, the X.Org Server, LibreOffice, WordPress, Redis, Wireshark, XZ-Utils, Firefox ESR, Apache HTTPD, and other common packages.

In addition to the plethora of security fixes given all the ongoing AI/LLM-driven security research, many bug fixes also made it into Debian 13.8. The Debian 13.8 release rebuilds various Rust-based packages with the updated Rust compiler, rebuilding other packages against updated OpenSSL and Glibc libraries, fixing a denial of service issue with FreeType, fixing Wayland color management handling in KDE’s KWin, memory leak fixes, build failure fixes to different packages, and compatibility updates for the Thunderbird 153 mail client.

Downloads and more details on today’s Debian 13.8 release via Debian.org.

Timestamps:

00:00 Intro

00:41 Sponsor

00:53 GrapheneOS claims Google is waging war against alternative ROMs

03:32 Android pushes their sideloading rules in January

05:41 Google confirms native app lock won’t come to older Android versions

07:20 Manjaro members create a non profit to take over the project

09:43 Proton adds a desktop app for their Al tool

11:34 Canonical will ship Al generated patches to Ubuntu

13:59 Developer vibe codes Windows 11 clone

16:02 Snap Store saw several hundred new apps added in one weekend

18:22 Purism makes a Risc V phone for 1600 dollars

21:03 New AMD drivers to reduce stuttering in games

22:13 GNOME launches fundraiser

23:40 Codeberg Domain Suspended by registrar

26:23 Sponsor: Tuxedo Computers

Links:

GrapheneOS claims Google is waging war against alternative ROMS

https://www.androidauthority.com/grapheneos-team-google-pressure-3737525/

Android pushes their sideloading rules in January

https://www.androidauthority.com/android-sideloading-rules-developer-verification-global-3737188/

Google confirms native app lock won’t come to older Android versions

https://www.androidauthority.com/android-native-app-lock-older-versions-3737530/

Manjaro members create a non profit to take over the project

https://linuxiac.com/manjaro-linux-moves-toward-independent-community-governance/

Proton adds a desktop app for their Al tool

https://techcrunch.com/2026/11/17/protons-lumo-a-privacy-focused-alternative-to-chatgpt-and-claude-arrives-on-desktop/

Canonical will ship Al generated patches to Ubuntu

https://feed.itsfoss.com/link/24361/17526502/canonical-surge-announcemengt

Developer vibe codes Windows 11 clone

https://www.tomshardware.com/software/windows/developer-vibe-codes-windows-11-alternative-operating-system-for-amd64-arm64-and-riscv64-hardware-libernt-is-a-free-64-bit-clone-promising-reliable-stable-and-efficient-performance

Snap Store saw several hundred new apps added in one weekend

https://www.omgubuntu.co.uk/2026/11/snap-store-new-app-increase-ai

Purism makes a Risc V phone for 1600 dollars

https://linuxiac.com/purism-unveils-1599-librem-5-v2-linux-phone-powered-by-risc-v/

New AMD drivers to reduce stuttering in games

https://www.phoronix.com/news/AMDGPU-Sparse-Gaming-Valve

GNOME launches fundraiser

https://blogs.gnome.org/foundation/2026/11/18/lets-build-the-future-of-gnome-together/

Codeberg Domain Suspended by registrar

https://linuxiac.com/codeberg-domain-suspended-by-namesilo-disrupting-open-source-projects/

Timestamps:

00:00 Intro

00:34 Sponsor: Joplin

02:00 Starter Distros

03:53 Just read the code / packagebuild

06:16 Keep your politics out of my free sotware

09:33 Linux isn’t ready

11:23 Vibe cloned software will end proprietary software

14:03 Foss developers are lazy

17:14 Fragmentation is killing linux

20:32 Asking for money is “begware”

22:11 Open Source Is Less Secure

24:36 Conclusion

25:38 Sponsor: Tuxedo Computers

Nov 19 (Reuters) - JPMorgan Chase (JPM.N), opens new tab, the largest US lender, said on Thursday that third parties who provide services to the firm were the target of a cyberattack. “Based on our investigation so far, we believe the attackers accessed certain marketing data held by those vendors, which may include some customer names ‌and email addresses,” a JPMorgan spokesperson said, adding that the company would be contacting the affected customers directly.

Jumpstart your morning with the latest legal news delivered straight to your inbox from The Daily Docket newsletter. Sign up here. “There is no connection to service disruption of some customers experienced earlier this week,” the spokesperson added.

Earlier this week, the bank experienced problems processing transactions due to a software bug which also affected other banks and caused some disruptions.

These incidents at JPMorgan followed several other recent problems including a nationwide FAA ground stop that disrupted travel last week and Microsoft’s global email outage, while last month crypto exchange Binance experienced a massive hack.

After the outage, lenders received inquiries from the Office of the Comptroller of the Currency, according to a ⁠an industry executive, who added that the US banking regulator was trying to assess the impact and wanted to know about communication to customers.

The Treasury and the OCC were calling banks minutes after the incident was reported to check that the issue was contained and it was not a cyber-related incident, a second person said adding that the OCC routinely checks after any such incidents.

“Customers don’t distinguish between a bank and a vendor when it comes to a cyberattack, so there is a question of reputational risk here,” said Carissa Robb at SolomonEdwards, a consulting firm. “There needs to be a little bit more pressure on how often companies are scrutinizing the amount of data that is shared with vendors and the necessity of the data being shared,” Robb said.

A cyber extortion group called “n0n” claimed on November 16 to have obtained cardmember engagement records that included “hundreds of thousands of campaign interactions for tens of thousands of distinct cardmember email addresses,” according to a screenshot of the ‌message captured ⁠by cybercrime research platform eCrime.ch.

The data includes what appears to be 124 bank employee email addresses and more than 16,000 customer email addresses, some with phone numbers and postal codes, according to a Reuters review. Reuters could not independently verify the authenticity of the data.

JPMorgan declined to comment on the data. The same hacking group on November 16 posted similar claims regarding Visa and Mastercard and posted data.

A Visa spokesperson said the company is aware of the claims and that they are “associated with an incident involving a third-party service provider in Asia Pacific. ⁠Visa’s systems were not involved and were not impacted. No payments data such as card numbers were affected.”

A Mastercard spokesperson said the company was recently informed of an incident “at a third-party provider that resulted in the exposure of limited amount of email addresses — non-payments information — from a small subset of cardholders enrolled in a specific benefit program. There is no impact ⁠to the Mastercard payment network or the ability for people to use their cards.”

The Visa data posted by the group appears to be primarily focused on Asian-Pacific markets, including Hong Kong, Taiwan, Korea, Japan, Philippines, Singapore, Malaysia, Australia, Macau and others, according to a Reuters review. Across several spreadsheets, the data includes thousands of purported ⁠customer email addresses, phone numbers, and Visa marketing campaign data. Reuters has not verified the authenticity of the data.

The Mastercard data posted by n0n includes marketing data related to customers in North America, the Middle East and Africa, and a small number of Mastercard employee email addresses.

The hacking group has claimed roughly 200 incidents since emerging in September 2026, according to eCrime.ch.

Reporting by Arasu Kannagi Basil in Bengaluru; Editing by Leroy Leo, Chizu Nomiyama and Nick Zieminski

Google has partnered up with Jeff Bezos’ Blue Origin to deploy small satellite data centers into space, as part of its Project Suncatcher project. Each of these satellites will be equipped with “roughly the capacity of a data center rack” and will enter into a sun-synchronous orbit via heavy-lift New Glenn rockets.

The rocket will carry several Google tensor processing units, the company’s proprietary AI chips, along with data center servers. The first launch isn’t scheduled until early 2029, so we have a couple of years to see if this whole project even works.

This is an experiment that Google calls a “long-term moonshot” to see if it’s possible to put AI infrastructure in space by “tapping into the abundant solar power in orbit.” The benefits of this would be massive. Data centers here on Earth are notorious hogs, with their snouts all over electricity grids, land and cooling systems.

The hope is that the harsh vacuum of the cosmos will be a better fit for the technology. After all, in space nobody can hear you make endless industrial noises and high-pitched whirs all day every day. This is a very real situation for folks living near data centers.

Google is far from the only company trying to kick the data center can straight into outer space. Elon Musk’s SpaceX has been experimenting with the idea, though it may involve putting a gigantic catapult on the moon (really.) There are also some startups fiddling with the technology, like Starcloud.

Can this even work? We don’t know yet, though there are some serious hurdles to overcome. Google did deploy its first AI server satellite back in October, but it was sent into low-Earth orbit and can only operate for 15 minutes at a time. Scaling up the affiliated cooling systems looks to be incredibly difficult.

That’s because standard heat dissipation doesn’t work in space, so it has to be released through pipes and panels rather than conventional cooling systems. There’s also the matter of radiation. It’s everywhere and causes something called “bit flip.” This essentially flips the binary code from a one to a zero, or vice versa. Obviously, this would be a major issue for binary-coded systems.

Did I mention the actual launches? It’s extremely expensive to send stuff to space. Just one Falcon 9 launch costs around $74 million and the maximum payload can barely cover the hardware for a small server room, let alone a hyperscale data center.

“Expanding from one satellite to a vast network of them that operate like a giant data center will take years and enormous funds,” Brandon Lucia, a professor of electrical and computer engineering at Carnegie Mellon University, told The New York Times. “If you do this on a large scale, there are additional engineering problems.”

Finally, there’s a risk to us humans here on Earth. Scientists have been considering a theoretical scenario called Kessler syndrome for decades. This is when the density of objects in low-orbit gets so high and collisions become so commonplace that it creates a chain reaction of debris. We would be on the receiving end of that debris.

This theory was posited back when there were just under 2,000 items circling a low-Earth orbit. That number has since risen to over 47,000 and Elon Musk recently floated an idea to add millions of new satellites into the mix.

The uutils project has released Rust Coreutils 0.13, the latest update to its Rust-based alternative to GNU Coreutils, the collection of essential command-line utilities on virtually every Linux system.

According to the official announcement, Rust Coreutils now passes 684 of the 707 GNU compatibility tests that run, achieving a 96.7% success rate. That’s 31 more passing tests than in version 0.12, although the test suite has expanded with 26 additional tests. There are currently 23 failing tests and no errors.

Much of the development work targets subtle differences that can cause existing shell scripts to behave unexpectedly. For example, sort now handles conflicting options more consistently with GNU. date improves formatting behavior, including locale-specific formats and fractional seconds. The dd utility also receives fixes for data conversions and handling certain output conditions.

Other compatibility improvements cover ls, which now handles time formatting and version-based sorting more accurately, and tail, which correctly follows symbolic links to their targets. Commands such as printf, seq, split, stat, and numfmt also receive fixes to make their behavior more closely match GNU Coreutils.

Another important area is file operation safety. The cp command no longer allows recursive copying through a symbolic link at the destination. Additionally, mv and ln now prevent certain operations that would replace directories with symbolic links.

Similarly, chmod, chown, and chgrp improve recursive directory traversal and root preservation checks. These changes are particularly relevant when utilities are used in automated scripts that modify files and directories.

Regarding performance, the biggest improvement concerns basenc, whose Base58 encoding and decoding operations are now about 35 times faster. On top of that, cut gains a 23% performance improvement, date becomes 22% faster, and join sees a 20% increase. The tr utility processes byte deletion more efficiently, while od now streams output line by line instead of buffering it.

Interestingly, the project’s efforts to match GNU behavior have benefited GNU Coreutils itself. During this development cycle, uutils contributors submitted 82 upstream commits, primarily adding tests for previously uncovered edge cases, along with fixes for tail and fmt.

For additional details, see the changelog.

The big Linux desktop environments have largely made up their minds about Wayland.

GNOME finished removing X11 from its login manager in March, and last month, KDE Plasma retired support for starting X11 sessions. Cinnamon is a step behind, but Linux Mint 27, due around Christmas, is set to ship a Wayland session that is no longer experimental. Though X11 stays the default.

Smaller desktops are at different points on the same journey.

LXQt dropped the experimental label from its Wayland session in v2.3.0, and Budgie in the Ubuntu Budgie 26.04 release went Wayland-only with labwc.

MATE, on the other hand, has moved in bits and pieces. Since MATE 1.26, apps like Atril, System Monitor, Pluma, and Terminal can run on Wayland, while the official mate-wayland-session is a simple, experimental setup that relies on Wayfire.

What’s still missing is a Wayland-native window manager for MATE. Its own, Marco, has no Wayland mode, and the following two projects, Polo and MATE Wayland Desktop, now aim to replace it in different ways.

Polo

Polo comes from developer Kerem Söke, and it is a compositor, window manager, and session manager for people who want MATE to look and behave on Wayland the way it does today.

It is written in Vala and C on top of libweston 16, follows Marco’s window management rules, and retains the settings, themes, and keybindings MATE users already have. Apps that still need X11 get a window manager of their own under XWayland.

Polo handles the session too, using the D-Bus interface of mate-session-manager, and the panel, Caja, and the screensaver can talk to it as they would on X11.

It’s first stable release was published on 12 November with support for tiling, workspaces, screen sharing through xdg-desktop-portal, and layer shell compatibility for mate-panel.

A DRM backend is responsible for handling multiple monitors and remembering screen layouts. Effects like wobbly windows and a desktop cube are also included (fans of Compiz, rejoice!).

You can build Polo from source on Fedora 44 or 45, Debian 14, or Ubuntu 26.04 or 26.10. Once installed, a “MATE (Polo)” entry should show up in LightDM.

Kerem has also said that he may host his own .deb repository if the Debian and Ubuntu MATE teams do not ship Wayland-enabled packages.

MATE Wayland Desktop

MATE Wayland Desktop uses an existing compositor instead of writing one. It swaps Marco for labwc and ships as an installable ISO built on Ubuntu 26.04 LTS, with Linux 7.0 and MATE 1.29 components as the foundations.

Eight of those MATE packages are rebuilt from newer upstream code, and one of them is mate-panel 1.29.2 with Wayland support turned on. Apps that only speak X11 run through XWayland.

Installation is handled by Calamares, and it offers optional LUKS2 full-disk encryption.

The project is also clear about the rough edges in it.

The keyboard, mouse, and keyboard shortcuts panels in Control Center crash when running natively, so MATE Wayland Desktop opens them through XWayland instead.

MATE’s own Displays dialog does not work on Wayland either. The “Displays” entry in the launcher opens wdisplays instead.

During installation and usage, Secure Boot has to be off, and the ISO boots up with the open source Nouveau GPU driver. NVIDIA’s own driver can be installed afterward with ubuntu-drivers.

Seeing that this is a new offering, I highly recommend you test it on a spare machine before going for a full installation.

You can get started with its ISO on x86_64 systems by heading over to the official download portal.

If you’ve followed security news this year, you know the number of reported vulnerabilities has gone up sharply. AI-assisted bug hunting means flaws are being found faster than maintainers can patch them, and every distro is feeling the pressure.

Canonical’s answer is to fight fire with fire. They are going to use AI to fix what AI is finding. At the recently concluded Ubuntu Summit 26.10, Canonical introduced Surge, a multi-agent AI system that triages vulnerabilities and writes backported fixes for Ubuntu packages.

Don’t worry. None of this goes into your regular Ubuntu security updates automatically. Surge’s fixes go to a new opt-in repository called the Edge archive, and only reach the normal updates after human-led testing.

The CVE problem Canonical is trying to solve

The announcement came in the security segment of the Summit’s opening remarks, presented by Pierre Guillemin, VP Engineering.

He started with numbers. According to the slides, the “fix velocity” in Ubuntu increased by 119% in one year. The “fix volume by quarter” chart shows roughly 1,400 fixes in early 2025 and about 3,100 a quarter by mid-2026.

That’s not it. Canonical says October 2026 alone had almost as many CVEs as all of 2025. October 2026 had almost as many CVEs as all of 2025

And Canonical doesn’t expect this to slow down. Guillemin said the company expects 2027 to bring “another order of magnitude growth” in CVEs.

How do you keep up with this pace while sticking to the review and testing standards that stable Ubuntu releases are known for? Hiring and working harder cannot practically compete with this pace.

Meet Surge

Surge is “a multi-agent orchestration framework for remediating vulnerabilities in Ubuntu.”

In simpler words, it’s a pipeline where several specialised AI agents handle different steps of fixing a CVE, from finding out whether Ubuntu is affected to producing a patch. Surge is a multi-agent orchestration framework

Guillemin says it builds on Canonical’s 20+ years of Ubuntu security work. The stated goal is to absorb a big influx of CVEs without creating backlogs. Or, as he put it, “fight AI with AI.”

Surge only covers Ubuntu userspace packages, meaning the applications and libraries in the archive. Kernel CVEs are not part of it, as kernel fixes need a different backporting approach and follow their own release cycle. How does Surge work?

The pipeline has six stages, and the interesting part is that it doesn’t trust a single AI model. Surge pipeline slide at Ubuntu Summit 26.10

It starts with intake and sourcing, which takes in vulnerability reports, maps them to packages, and checks whether the affected package is in Ubuntu at all. Then code forensics fetches the upstream patch, analyses the source, and tries to reproduce the vulnerability to confirm Ubuntu’s version is actually affected.

In the backporting engine, instead of one model writing the patch, several competing models each produce a candidate fix.

These candidates then go to consensus judging, where a separate panel of “judge” models evaluates them and has to agree on the right patch. If confidence is low or the judges deadlock, the case goes to human escalation, where Ubuntu security engineers review it manually.

Finally, the patch goes through the same build, verify and publish process as any other Ubuntu package, including deterministic tests, before it is published.

The Edge archive: AI fixes, but only if you ask for them

Surge-generated fixes are not pushed to your system through the usual security updates. Instead, Canonical is launching the Edge archive, an opt-in preview of fixes that are still in development.

Edge gives you machine-generated patches before they’ve gone through Canonical’s full qualification for general availability (GA). So you get fixes at “machine speed,” but with the compromise on the fact they haven’t had the full testing yet.

Canonical stresses that this is not a change in its security policy. It “will not automatically upload Surge-generated fixes to our stable releases.” Your regular security updates stay human-validated and keep coming through the usual channels.

Will you opt-in?

If you’re a regular Ubuntu desktop or server user, nothing changes unless you choose to. Your security updates continue to arrive the way they always have.

If you want to try it, Edge is available through Ubuntu Pro, which remains free for personal use. Canonical has published a guide on how to enable the Edge archive.

I wouldn’t put Edge on a production server, yet. But on a regular desktop machine or a homelab, it’s a good way to help Canonical find problems early.

To be honest, the idea of AI writing security patches will make some of you uneasy, and that’s fair. But we have to “fight AI with AI” because CVEs are not going to stop or reduced. Am I right?

The Manjaro team has registered its own non-profit in Germany. Called Manjaro Project e.V., it has seven founding members and is independent of the commercial-oriented Manjaro GmbH & Co. KG entity.

You might remember earlier this year, in March, a group of team members published a manifesto calling for the project to be split from the company, with a strike following soon after.

While this was announced on the Manjaro Linux forum and not on the main project webpage, the registration is already visible in the German register portal, under the Berlin court.

An e.V.?

An e.V. (eingetragener Verein) is a registered association under German law. It is entered in a register kept by the local court, and its purpose cannot be running a commercial business. Registering gives it its own legal identity, separate from the people in it.

That identity matters to the developers because it lets them hold things as a group.

The manifesto asked for equal ownership among members and open voting on big decisions instead of everything being centered on one person. It now means there’s a body that could own the assets if they’re handed over.

Manjaro GmbH & Co. KG is a different kind of body. A GmbH & Co. KG is a limited partnership where a GmbH takes on the personal liability, with the GmbH’s managing directors handling the running of the business.

Stating the obvious, Manjaro now has two separate bodies behind it, and it’s interesting to see how the project ended up in such a situation.

How Manjaro got here

Manjaro has been a German company since 2019. Way back in April 2024, that company announced a management change when Bernhard Landauer stepped away from the company to focus on other work and a new CTO joined to replace him.

Then came the Manjaro 2.0 Manifesto in March, where signatories said the leadership’s priorities didn’t line up with what the developers and community wanted.

Project lead Philip Müller replied, saying he had no personal objection to an association but wouldn’t help set it up and that any asset transfer would have to be discussed closely with the company.

The team has since managed to push out the most recent Testing and Stable updates without Müller being involved.

What now?

The manifesto suggested handing over assets like the manjaro.org domain, the forum, and community donations. According to the team, no transfer of company assets has happened yet.

Before that, the e.V. has some groundwork to do, such as tidying up its statutes, bringing in more members, and opening its own bank account. Talks with the company come after.

For end users, I don’t expect them to be affected in any major way. This kind of feels like a takeover, but a gentle one so far. The situation for donors who had set up recurring payments is a bit hazy.

You see, donations still go to accounts under the company’s control, possibly Müller’s too, and the e.V. hasn’t settled on whether to start fresh accounts or take over the current ones.

Basically, there’s no new recipient to switch to yet, and the team hasn’t said when that gets decided. A second announcement confirming that assets have moved is what I’d watch for, since that’s when the split becomes more than a register entry.

Then there’s the Orange Pi Neo, a handheld Orange Pi built with Manjaro that was put on hold in March because of skyrocketing memory and SSD prices. The announcement doesn’t say who handles partner projects like it, so that’s an open question.