Give Linux Mint a makeover with Silent Horizon

People often say Linux Mint looks dated, but the Cinnamon desktop is highly customisable – something a new transformation pack shows to eye-catching effect. Silent Horizon is a Linux Mint makeover pack made up of desklets, panel applets, wallpaper, Plank dock theme and minor Cinnamon layout tweaks. The work of ~PersianVibeCoder, it aims to create a “calm, minimal desktop with little details that make it feel alive”. It has little “details” that do add to the dynamism – albeit at the cost of performance on lower spec devices (as I’ll come to in a moment). Take the weather and system […]

You’re reading Give Linux Mint a makeover with Silent Horizon, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

Continue ReadingGive Linux Mint a makeover with Silent Horizon

Era, the new Rust-based calendar for GNOME, is now in beta

Era calendaring app showing month view with lots of colourful event labels in both wide window and mobile sizeEra is a new Rust-based calendar app for GNOME that describes itself as “beautiful and performant”. And you don’t need to schedule a date to try it; a beta release is available to install from Flathub. At first glance, Era looks like GNOME’s Calendar (which got a big update in the GNOME 51, notably in ways you feel rather than see). But then, how could it not? There are only so many ways to arrange a grid of numbers in boxes with room for coloured event labels. Functionally, Era covers the same ground: you can browse dates, add, edit and […]

You’re reading Era, the new Rust-based calendar for GNOME, is now in beta, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

Continue ReadingEra, the new Rust-based calendar for GNOME, is now in beta

Banshee music player is back from the dead (well, kinda)

Illustrated zombie hand coming out of the ground holding the Banshee music player logoA revived Banshee music player is now available on the Snap store, making it possible to use it on modern Linux desktops decades after its last stable release. Packaged by Alan Pope (aka popey), the new Banshee snaps lets you now run Banshee 2.6.2, the final stable release from 2014, on model Linux desktops. Not merely a repack; the Snap Store description mentions this includes ‘compatibility fixes and restores selected online services’, but also notes that not all ‘historical’ services may work. Is it an official continuation? No. This is more ‘reanimated corpse’ than reincarnation. Popey’s Banshee snap is almost […]

You’re reading Banshee music player is back from the dead (well, kinda), a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

Continue ReadingBanshee music player is back from the dead (well, kinda)

The Impact of Digital Sovereignty on Open Source Companies

By Philipp Reisner, CEO LINBIT®

Sovereignty is a word borrowed from statecraft. A sovereign country is independent in its decisions. The term “digital sovereignty” is a more recent invention that applies to organizations and even individuals.

In this article, I discuss what the push for digital sovereignty implies for Linux-focused, open source developers and companies. The framework I use is a European one, because I am Vienna-based and familiar with it. As I discuss later, the implications are not limited to Europe.

A framework for defining and rating digital sovereignty

The European Commission published the EU Cloud Sovereignty Framework (CSF), which breaks sovereignty down into eight objectives:

  • SOV-1, Strategic: Ownership and governance are controlled, avoiding external dependencies.
  • SOV-2, Legal and Jurisdictional: Protects against external laws and unauthorized access.
  • SOV-3, Data and AI: Control and privacy compliance for data and AI models in the cloud.
  • SOV-4, Operational: Day-to-day cloud administration, management, and support are handled securely from within.
  • SOV-5, Supply Chain: Protects against vendor lock-in and external bottlenecks.
  • SOV-6, Technology Openness: Encourages open standards and the freedom to choose technologies.
  • SOV-7, Security and Compliance: Aligns cloud services with European cybersecurity standards, frameworks, and compliance audit rules.
  • SOV-8, Environmental Sustainability: Adoption of energy-efficient infrastructure, environmentally responsible practices, and activity reporting intended to reduce environmental impacts of technological activity.

Rating technology providers for digital sovereignty compliance

The framework rates providers on two scales: a Sovereignty Effectiveness Assurance Level (SEAL), and a complementary Sovereignty Score for cloud services. The first indicates a minimum level of sovereignty objectives met. The second shows a provider’s strengths and weaknesses across the objectives.

Each objective is rated from SEAL-0 to SEAL-4. SEAL-4 means an EU supply chain, from the physical chips up to the software.

The mechanic I find most interesting is that a provider does not get one SEAL level. It receives eight, and the overall level is the lowest of them. Your weakest objective decides your rating, not your average. Anyone who has ever tuned a storage stack will recognize that logic.

Meeting the technology-openness objective

Open source software can put providers in a strong position to address the technology-openness objective, SOV-6, because customers can inspect the code, operate it independently, and avoid dependencies on proprietary implementation. Because the source is open, that argument does not stop at the EU border. A service provider in the US or in Asia aiming for full SEAL-4 is not held back by choosing open source software.

Open standards need open implementations

SOV-6 specifies two things: open standards and the freedom to choose technologies. In software, an open standard might define an interface that anyone can implement, but if only one vendor has implemented it, a buyer still has a single supplier for it. Depending on a single supplier also weakens a provider on SOV-5, the supply-chain objective, which protects against vendor lock-in. Freedom to choose means being able to substitute one implementation for another.

An example is the Container Storage Interface (CSI), a vendor-neutral storage standard developed under the Cloud Native Computing Foundation (CNCF) and used by Kubernetes. CSI is the standard, LINBIT provides a CSI driver for LINSTOR® and its upstream CNCF project, Piraeus Datastore, and a buyer running Kubernetes can use this driver. Because of the open standard nature of the interface, the buyer can also move between storage back ends. This is freedom for the buyer, motivation for providers to make a better solution, and neutrality from a foundation like the CNCF.

Implications of digital sovereignty for cloud and technology services providers

Digital sovereignty is no longer an exercise on paper. In April 2026, [the European Commission awarded a sovereign cloud contract worth up to €180 million over six years to four European providers](https://commission.europa.eu/news-and-media/news/commission-advances-cloud-sovereignty-through-strategic-procurement-2026-04-17_en), with SEAL-2 as the minimum bar for eligibility. Sovereignty has become a procurement instrument with money attached. Predictably, one of the awards is already being publicly contested as “sovereignty-washing”.

What poured oil on the fire was an incident involving the chief prosecutor of the International Criminal Court. After the US sanctioned court officials, the chief prosecutor reportedly lost access to his Microsoft-hosted email account, and bank accounts in the United Kingdom were frozen. Since these actions, some EU banks with US exposure are preferring to over-comply rather than take any risk. Microsoft disputes the framing and maintains it never suspended services to the ICC as an organization. For me, the detail of who pressed which button matters far less than the lesson: neither the email nor the banking depended on a European decision.

In the US, similar discussions have taken place, only with different verbiage. There it is “economic security” and “supply chain resilience”, mostly aimed at China, and where Europe says “technological sovereignty”, Washington says “technological leadership”. Different branding, same substance.

Conclusion

As digital sovereignty gains weight in technology sourcing decisions, smaller vendors benefit.

A framework that asks, “Who owns you? Whose laws apply? Can I operate this without you, and can I read the source?” rewards exactly the properties a small open source company has by default. The hyperscalers will feel some headwind, though they are not standing still, and “sovereign” regions run by local operating entities are their answer. Whether that clears a SEAL-3 or SEAL-4 bar is the argument of the next few years.

LINBIT already made an investment in developing in the open. An open license is necessary but not enough on its own, because a project can be open and still be controlled by a single company that can relicense it. What makes the openness durable is governance that the original vendor cannot reverse. DRBD® ships in the mainline Linux kernel, and we are working to upstream the current DRBD 9 code. Code in the commons, for example, in the mainline kernel, under a foundation such as the CNCF, or in another home that no single vendor controls, is the strongest answer to SOV-6 I know of. Every project that puts it there widens the set of technology a sovereign buyer can choose from.

The post The Impact of Digital Sovereignty on Open Source Companies appeared first on Linux.com.

Continue ReadingThe Impact of Digital Sovereignty on Open Source Companies

systemd 262 Released with Static PID 1, Intel TDX, TPM Improvements, and New Container Features

systemd 262 Released with Static PID 1, Intel TDX, TPM Improvements, and New Container Features

The systemd project has officially released systemd 262, delivering another substantial update to the system and service manager used by most major Linux distributions. The final release was tagged on September 22, 2026, following three release candidates earlier in the month.

Systemd 262 introduces improvements across service management, containers, virtualization, encrypted storage, TPM security, networking, journal recovery, system updates, and unattended installations. Among the most interesting additions are the ability to build systemd as a single statically linked PID 1 binary, Intel TDX support in systemd-vmspawn, Live Update Orchestrator integration, improved TPM-backed encryption, and new fallback unit files embedded directly into the systemd manager.

The release also contains a rather unusual development safeguard: an AI/LLM canary intended to help identify code contributions generated by AI that haven’t been properly reviewed by a human before submission.

systemd 262 Is Officially Available

The final systemd 262 source was tagged by systemd developer Luca Boccassi on September 22.

The upstream tag identifies commit 8cc40e0c5e9234bf45084751ac53b1fbfe70b492 as systemd v262, following release candidates published throughout September.

The release has already begun reaching Linux distribution development repositories.

Debian accepted systemd 262-1 into Debian Unstable on September 22, while Fedora has prepared systemd 262 packages for Fedora 45.

As usual, the speed at which systemd 262 reaches ordinary users will depend on each distribution’s update policy.

systemd Can Now Become a Single Static PID 1 Binary

One of the most interesting changes in systemd 262 is support for building systemd as a single statically linked PID 1 and executor binary.

The feature is primarily intended for extremely small container environments.

Normally, systemd depends on a collection of dynamically linked libraries and supporting components. That architecture makes sense for a complete Linux distribution, but containers sometimes need a much smaller runtime environment.

The new static configuration makes it possible to create a more self-contained systemd executable suitable for minimal container images.

These builds avoid dynamically loading optional libraries and use simplified mechanisms for resolving users and groups rather than relying on the complete Name Service Switch infrastructure.

This doesn’t mean normal Linux distributions will suddenly replace their standard systemd packages with a giant static executable. The capability is specifically useful for specialized container and minimal-system deployments.

Continue Readingsystemd 262 Released with Static PID 1, Intel TDX, TPM Improvements, and New Container Features

Ubuntu 26.10 adds a Windows-style window snapping panel

Ubuntu 26.10 offers a new way to tile your apps, with a layout picker sliding in from the top of the screen when you move a window. This “dropzone” concept for quick tiling will be familiar to users of Windows 11 users or those who’ve tried the Tiling Shell extension for GNOME Shell – they do, broadly, the same thing. When you drag a window a layout picker with a small set of preset layouts drop zones moves in from the top of the display. You drag your window up over a layout zone (a ‘ghost’ preview of where the […]

You’re reading Ubuntu 26.10 adds a Windows-style window snapping panel, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

Continue ReadingUbuntu 26.10 adds a Windows-style window snapping panel