Linux Mint 22.2 ‘Zara’ Released: Polished, Modern, and Built for Longevity

1 week ago
by George Whittaker Introduction

The Linux Mint team has officially unveiled Linux Mint 22.2, codenamed “Zara”, on September 4, 2025. As a Long-Term Support (LTS) release, Zara will receive updates through 2029, promising users stability, incremental improvements, and a comfortable desktop experience.

This version is not about flashy overhauls; rather, it’s about refinement — applying polish to existing features, smoothing rough edges, weaving in new conveniences (like fingerprint login), and improving compatibility with modern hardware. Below, we’ll delve into what’s new in Zara, what users should know before upgrading, and how it continues Mint’s philosophy of combining usability, reliability, and elegance.

What’s New in Linux Mint 22.2 “Zara”

Here’s a breakdown of key changes, refinements, and enhancements in Zara.

Base, Support & Kernel Stack
  • Ubuntu 24.04 (Noble) base: Zara continues to use Ubuntu 24.04 as its upstream base, ensuring broad package compatibility and long-term security support.

  • Kernel 6.14 (HWE): The default kernel for new installations is 6.14, bringing support for newer hardware.

  • However — for existing systems upgraded from Mint 22 or 22.1 — the older kernel (6.8 LTS) remains the default, because 6.14’s support window is shorter.

  • Zara is an LTS edition, with security updates and maintenance promised through 2029.

Major Features & Enhancements Fingerprint Authentication via Fingwit

Zara introduces a first-party tool called Fingwit to manage fingerprint-based authentication. With compatible hardware and support via the libfprint framework, users can:

  • Enroll fingerprints

  • Use fingerprint login for the screensaver

  • Authenticate sudo commands

  • Launch administrative tools via pkexec using the fingerprint

  • In some cases, bypass password entry at login (unless home directory encryption or keyring constraints force password fallback)

It is important to note that fingerprint login on the actual login screen may be disabled or limited depending on encryption or keyring usage; in those cases, the system falls back to password entry.

UI & Theming Refinements
  • Sticky Notes app now sports rounded corners, improved Wayland compatibility, and a companion Android app named StyncyNotes (available via F-Droid) to sync notes across devices.

Go to Full Article
George Whittaker

Secure your future in cybersecurity — save up to 40% now!

1 week ago

Your Cybersecurity Career Starts Here Boost Your Cyber Skills — Check out our FREE Cybersecurity Courses! Use code: OCT25CYBER to Save 40% on Cybersecurity Courses & CertificationsUse code: OCT25THRIVE to Save 30% on THRIVE-ONE Annual SubscriptionUse code: OCT25 to Save 30% on All Other Courses & Certifications *Offer ends October 21, 2025 ADVANCE NOW

The post Secure your future in cybersecurity — save up to 40% now! appeared first on Linux.com.

Linux.com Editorial Staff

Kubernetes on Bare Metal for Maximum Performance

1 week ago

When teams consider deploying Kubernetes, one of the first questions that arises is: where should it run? The default answer is often the public cloud, thanks to its flexibility and ease of use. However, a growing number of organizations are revisiting the advantages of running Kubernetes directly on bare metal servers. For workloads that demand […]

The post Kubernetes on Bare Metal for Maximum Performance appeared first on Linux.com.

Linux.com Editorial Staff

[Testing Update] 2025-10-13 - Kernels, Qt 6.10, KDE Frameworks & Gear

1 week 1 day ago

Hello community, here we have another set of package updates. Welcome to our new development cycle of Manjaro 25.1.0, code-named ‘Anh-Linh’. It is not sure yet if we will focus on Plasma 6.4 series or adopt 6.5 series early on. For sure we will introduce GNOME 49 and maybe Cosmic 1.0 (Beta).

Current Promotions Recent News Valkey to replace Redis in the [extra] Repository (click for more details) Previous News Finding information easier about Manjaro (click for more details) Notable Package Updates
  • Some Kernels got updated
    • kernel 6.16 series is now marked EOL
    • including new firmware
  • Qt 6.10
  • KDE Frameworks 6.19.0
  • KDE Gear 25.08.2
  • New update to grub to fix installations on older UEFI systems
  • amdvlk got removed
  • LiberOffice 25.8.2
  • Pipewire 1.4.9
  • ROCm 6.4.4
  • Vulkan SDK 1.4.328.1
  • Haskell and Python updates
Additional Info Python 3.13 info (click for more details) Info about AUR packages (click for more details)

Get our latest daily developer images now from Github: Plasma, GNOME, XFCE. You can get the latest stable releases of Manjaro from CDN77.

Our current supported kernels
  • linux54 5.4.300
  • linux510 5.10.245
  • linux515 5.15.194
  • linux61 6.1.155
  • linux66 6.6.111
  • linux612 6.12.52
  • linux616 6.16.12 [EOL]
  • linux617 6.17.2
  • linux618 6.18.0-rc1
  • linux61-rt 6.1.151_rt54
  • linux66-rt 6.6.106_rt61
  • linux612-rt 6.12.49_rt13
  • linux615-rt 6.15.0_rt2
  • linux616-rt 6.16.0_rt3

Package Changes (10/13/25 11:28 CEST)

  • testing core x86_64: 37 new and 37 removed package(s)
  • testing extra x86_64: 2489 new and 2518 removed package(s)
  • testing multilib x86_64: 25 new and 28 removed package(s)

A list of all changes can be found here.

Click to view the poll.

Check if your mirror has already synced:

7 posts - 7 participants

Read full topic

philm

Ubuntu Update Backlog: How a Brief Canonical Outage Cascaded into Multi-Day Delays

1 week 5 days ago
by George Whittaker Introduction

In early September 2025, Ubuntu users globally experienced disruptive delays in installing updates and new packages. What seemed like a fleeting outage—only about 36 minutes of server downtime—triggered a cascade of effects: mirrors lagging, queued requests overflowing, and installations hanging for days. The incident exposed how fragile parts of Ubuntu’s update infrastructure can be under sudden load.

In this article, we’ll walk through what happened, why the fallout was so severe, how Canonical responded, and lessons for users and infrastructure architects alike.

What Happened: Outage & Immediate Impact

On September 5, 2025, Canonical’s archive servers—specifically archive.ubuntu.com and security.ubuntu.com—suffered an unplanned outage. The status page for Canonical showed the incident lasting roughly 36 minutes, after which operations were declared “resolved.”

However, that brief disruption set off a domino effect. Because the archives and security servers serve as the central hubs for Ubuntu’s package ecosystem, any downtime causes massive backlog among mirror servers and client requests. Mirrors found themselves out of sync, processing queues piled up, and users attempting updates or new installs encountered failed downloads, hung operations, or “404 / package not found” errors.

On Ubuntu’s community forums, Canonical acknowledged that while the server outage was short, the upload / processing queue for security and repository updates had become “obscenely” backlogged. Users were urged to be patient, as there was no immediate workaround.

Throughout September 5–7, users continued reporting incomplete or failed updates, slow mirror responses, and installations freezing mid-process. Even newly provisioning systems faced broken repos due to inconsistent mirror states.

By September 8, the situation largely stabilized: mirrors caught up, package availability resumed, and normal update flows returned. But the extended period of degraded service had already left many users frustrated.

Why a Short Outage Turned into Days of Disruption

At first blush, 36 minutes seems trivial. Why did it have such prolonged consequences? Several factors contributed:

  1. Centralized repository backplane Ubuntu’s infrastructure is architected around central canonical repositories (archive, security) which then propagate to mirrors worldwide. When the central system is unavailable, mirrors stop receiving updates and become stale.

Go to Full Article
George Whittaker