AHXproject

Amarok 3.3.2 Brings Improvements to User Interface, Audio Backend, and More



Amarok 3.3.2 open-source music player is now available for download with improvements to user interface, audio backend, playlist, and more.

The post Amarok 3.3.2 Brings Improvements to User Interface, Audio Backend, and More  appeared first on 9to5Linux  - do not reproduce this article without permission. This RSS feed is intended for readers, not scrapers.


Categories: Apps, News, Amarok, audio player, music player
Source: https://9to5linux.com/amarok-3-3-2-released-with-improvements-to-user-interface-audio-backend-and-more Jan 18, 2026, 12:38 PM

Fedora Games Lab Spin to Switch from Xfce to KDE Plasma with Fedora Linux 44



Fedora Games Lab ditches the Xfce desktop environment for KDE Plasma starting with the upcoming Fedora Linux 44 release in April 2026.

The post Fedora Games Lab Spin to Switch from Xfce to KDE Plasma with Fedora Linux 44  appeared first on 9to5Linux  - do not reproduce this article without permission. This RSS feed is intended for readers, not scrapers.


Categories: Distros, News, Fedora Games Lab, Fedora Linux 44, KDE Plasma, Linux distribution
Source: https://9to5linux.com/fedora-games-lab-spin-to-switch-from-xfce-to-kde-plasma-with-fedora-linux-44 Jan 16, 2026, 03:03 PM

PipeWire 1.4.10 Backports Filter-Graph Channel Support and Fixes More Bugs



PipeWire 1.4.10 open-source server for handling audio/video streams and hardware on Linux is now available for download with various fixes and improvements.

The post PipeWire 1.4.10 Backports Filter-Graph Channel Support and Fixes More Bugs  appeared first on 9to5Linux  - do not reproduce this article without permission. This RSS feed is intended for readers, not scrapers.


Categories: Apps, News, PipeWire, PipeWire 1.4
Source: https://9to5linux.com/pipewire-1-4-10-backports-filter-graph-channel-support-and-fixes-more-bugs Jan 16, 2026, 01:42 PM

Raspberry Pi Imager 2.0.4 Improves Handling for Files Larger Than 4GB



Raspberry Pi Imager 2.0.4 SD card flashing utility is now available for download with improved handling of files larger than 4GB and other changes. Here's what's new!

The post Raspberry Pi Imager 2.0.4 Improves Handling for Files Larger Than 4GB  appeared first on 9to5Linux  - do not reproduce this article without permission. This RSS feed is intended for readers, not scrapers.


Categories: Apps, News, Raspberry Pi, Raspberry Pi Imager
Source: https://9to5linux.com/raspberry-pi-imager-2-0-4-improves-handling-for-files-larger-than-4gb Jan 16, 2026, 12:31 PM

First .NET 10 Servicing Update Now Available in Ubuntu 24.04 LTS

Looking to run .NET 10 on Noble Numbat? The .NET 10.0.1 update is now available for Ubuntu 24.04 LTS. Latest SDK and runtime improvements – an apt command away.

You're reading First .NET 10 Servicing Update Now Available in Ubuntu 24.04 LTS , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: News, App Updates, dotnet, Microsoft, Ubuntu 24.04 LTS
Source: https://www.omgubuntu.co.uk/2026/01/dotnet-10-0-1-update-ubuntu-24-04-lts Jan 16, 2026, 07:05 PM

Canonical Ubuntu and Ubuntu Pro now available on AWS European Sovereign Cloud

January 15, 2026 – Canonical, the publisher of Ubuntu and provider of open source security, support, and services, announced today that it is a launch partner for the AWS European Sovereign Cloud, a new independent cloud for Europe, with Ubuntu and Ubuntu Pro now available.

Canonical's Ubuntu Pro delivers a securely designed, stable, and enterprise-ready foundation for open source innovation while providing customers with the same security, availability, and performance they expect from AWS. This enables customers to meet stringent operational autonomy and data residency requirements within the European Union (EU).

The AWS European Sovereign Cloud is a fully featured, independently operated sovereign cloud backed by strong technical controls, sovereign assurances, and legal protections designed to meet the needs of European governments and enterprises. The AWS European Sovereign Cloud infrastructure is entirely located within the EU and operates independently from existing regions. Customers using the AWS European Sovereign Cloud will benefit from the full power of AWS including the same services portfolio, security, availability, performance, familiar architecture, APIs, and innovations such as the AWS Nitro System.

"The AWS European Sovereign Cloud represents a significant step forward for organizations operating under EU regulatory frameworks," said Cindy Goldberg, VP Cloud and Silicon Partnerships at Canonical.  By combining the performance and the expanded security coverage of Ubuntu Pro with AWS's sovereignty controls and technical assurances, we're delivering the compliance support and innovation our customers need to accelerate their digital transformation while meeting stringent EU regulatory requirements."

Discover Ubuntu and Ubuntu Pro on the AWS European Sovereign Cloud today on the AWS EC2 console. Launch now on the European Sovereign Cloud EC2 console .

About Canonical 

Canonical, the publisher of Ubuntu, provides open source security, support, and services. Our portfolio covers critical systems, from the smallest devices to the largest clouds, from the kernel to containers, from databases to AI. With customers that include top tech brands, emerging startups, governments and home users, Canonical delivers trusted open source for everyone.

Learn more at https://canonical.com/

Canonical announced it is a launch partner for the AWS European Sovereign Cloud, with Ubuntu and Ubuntu Pro now available. This new independent cloud for Europe enables organizations to run secure, enterprise workloads with full operational autonomy and EU data residency. By combining the performance and expanded security coverage of Ubuntu Pro with AWS sovereignty controls, customers can meet stringent EU regulatory requirements while continuing to innovate at scale.


Categories: AWS, Sovereign cloud, Ubuntu, Ubuntu Pro
Source: https://ubuntu.com//blog/ubuntu-aws-european-sovereign-cloud Jan 16, 2026, 12:06 AM

How to build DORA-ready infrastructure with verifiable provenance and reliable support

The Digital Operational Resilience Act (DORA) came into force across the EU on January 17, 2025, fundamentally changing how financial institutions must approach infrastructure and technology assets resilience. Its requirements around ICT risk management, operational resilience, and third-party oversight signal a broader shift that will ripple across regulated industries worldwide.

At its core, DORA demands something deceptively simple: organizations must know exactly what they're running, where it came from, and how to fix it when something breaks. For technical teams managing complex stacks spanning bare metal, the OS, kernel, and applications, this translates into a hard requirement for provenance: transparent, verifiable lineage from source code all the way up.

The provenance problem: you can't verify what you can't see

Traditional vendor stacks create a fundamental compliance problem: they're opaque by design. When you deploy a proprietary solution, you're accepting someone else's assurances about what's inside. You can't inspect the source code. You can't verify the build process. You can't independently validate that a security patch actually addresses the vulnerability it claims to fix.

While Software Bills of Materials (SBOMs) have emerged as an important transparency tool and represent progress, they fail to solve this fundamental inspection problem. An SBOM tells you what components are present in proprietary software, but you still can't examine the source code itself or verify the build process yourself. For regulated organizations facing requirements like DORA, this creates a compliance gap, where you can document dependencies but cannot truly verify their integrity.

DORA explicitly requires financial entities to maintain oversight of their ICT infrastructure, including third-party dependencies. So, how do you maintain oversight of something you can't inspect?

Open source becomes essential here. With open source software:

• You get reproducible inspectability all the way down the supply chain
• You can trace every component back to the developer who wrote it
• You can verify builds
• You can audit changes
• You can understand exactly what's running in your environment

The single developer problem (and why Ubuntu Pro matters)

Here's the uncomfortable truth about modern infrastructure: critical components in your stack likely trace back to a single developer somewhere on the internet, maintaining a library in their spare time. An estimate, based on analysis of ecosyste.ms  data, shows that a relatively small group, on the order of ten thousand people, supports the majority of the world's open source software users. In the Tidelift 2024 State of the Open Source Maintainer survey, 61% of unpaid maintainers reported working alone on their projects. When the Heartbleed vulnerability was discovered in 2014, OpenSSL—used by 66% of web servers at the time—was maintained by just a handful of volunteers, only one working full time, with the project receiving about $2,000 in annual donations.

These individual maintainers are doing heroic work. But from a resilience perspective, it's a risk. What happens when that developer moves on? Gets burned out? Simply stops maintaining the package?

The problem is worsening: in 2024, almost 60% of maintainers reported having quit or considered quitting their maintenance work, with many citing burnout, insufficient compensation, and overwhelming demands on their time.

Investing in open source is a form of infrastructure security: it reduces your dependence on unpaid, solo maintainers and builds sustainable maintenance pipelines with professional support, timely security patching, and long-term viability. When enterprises pay for Ubuntu Pro, part of that funding flows back into the open source ecosystem through Canonical's upstream engineering work and direct financial support for the projects Ubuntu depends on.​

Canonical does not just repackage open source; our engineers contribute features and fixes upstream across the projects shipped in Ubuntu, and we commit security maintenance for components long after their upstream end of life, such as continuing to backport OpenSSL 1.1.1 fixes for supported Ubuntu releases. Ubuntu Pro packages this ecosystem investment into a single subscription: up to 15 years of security maintenance for thousands of open source packages, plus the assurance that Canonical is actively collaborating with and funding the communities behind them. Instead of betting your resilience on a single unpaid maintainer, you get a vendor whose business model is aligned with keeping that open source infrastructure secure and sustainable over the long term.

From responsibility to assurance: system-level, not vendor-level

There's a fundamental difference between a vendor taking responsibility for their products and a platform providing assurance for your entire system.

When an Ubuntu Pro customer from the financial industry asked, "How do we get all machines FIPS-enabled and CIS-compliant?", that's not a question about a single application. It's a question about system-level security compliance across thousands of machines, down to the operating system and the metal beneath it.

Ubuntu Pro answers this by providing a single, verifiable stack with end-to-end provenance. The focus shifts from trusting individual vendors to establishing a unified security posture where every layer is supported, patched, and verifiable.

For finance organizations, this changes the conversation from "Do we trust this vendor?" to "Can we verify and validate our entire infrastructure up to the application layer?" The answer needs to be yes, and you need documentation to prove it.

The DORA advantage: knowing what you don't know

Discovering what you don't know proves more challenging than fixing known compliance issues. What packages are actually running in production? Which versions? What's their patch status? What potential exposures might an auditor find during their next review?

With Ubuntu Pro, you get continuous visibility, security maintenance and support:

• Complete inventory: Enumerate exactly what's running across your infrastructure
• Provenance tracking: Every package has verifiable lineage back to source
• Continuous patching: Both main and universe repository packages receive security updates
• Compliance tooling: Built-in capabilities for CIS hardening, FIPS certification, and compliance reporting

Beyond compliance: building for what comes next

Think of compliance as the baseline, not the goal. While DORA is a regulatory requirement for financial services in the EU, smart organizations across industries are using it as a model for their own resilience programs. The principles it codifies, operational resilience, supply chain transparency, systematic risk management, are universal concerns.

The trajectory is clear: more regulation, more scrutiny, more demands for transparency and provenance. When your industry's equivalent of DORA arrives (and it will), you need infrastructure that can already demonstrate:

• Verifiable provenance for every component in your stack
• Long-term support commitments backed by professional teams
• System-level security compliance down to the OS and infrastructure layer
• Complete source code transparency and documented patching processes

Ubuntu Pro applies these principles to open source infrastructure, combining transparent components with long-term security maintenance and support so your stack is ready for whatever comes next.

Learn more about other security standards we support: ubuntu.com/security/security-standards .

Get in touch  or start a 30-day Ubuntu Pro free trial .

References

• Digital Operational Resilience Act (DORA) – EIOPA
• Regulation (EU) 2022/2554 – EUR-Lex
• Tidelift 2024 State of the Open Source Maintainer Report
• The Unpaid Backbone of Open Source – Socket
• Critical infrastructure for the Web – Forbes
• Canonical + thanks.dev

DORA requires organizations to know what they run, where it came from, and how it's maintained. Learn how to build infrastructure with verifiable provenance.


Categories: Compliance, DORA, Security
Source: https://ubuntu.com//blog/build-dora-ready-infrastructure-with-verifiable-provenance Jan 14, 2026, 11:53 AM

Deploy your Spring Boot application to production

In a previous article, we covered how easy it is to create Spring Boot containers  with Rockcraft. So the next logical step is to deploy and operate your application in a production environment. The Juju ecosystem is the key to making this process straightforward.

In this article we walk through the steps required to deploy a Spring Boot application to production using Juju and Kubernetes. The goal is to showcase the integration of the application with essential services like PostgreSQL for database management and Traefik for ingress control.



Ordinarily, deploying and operating Spring Boot containers is easier said than done. Any non-trivial application will require integrations with other software components like databases, message brokers, and authentication services. Some of these components are complex to operate. What's more, your application will need to be exposed to the outside world. And for Day 2 operations, you'll also need to perform routine maintenance and properly monitor your application.

Fortunately, Juju provides a strong ecosystem composed of a multitude of high quality software operators that enables deployment, integration and lifecycle management at any scale, on any infrastructure.

With the release of the Spring Boot framework extensions for Rockcraft  and Charmcraft , if your application follows the 12-factor methodology best practices, you can benefit from the Juju ecosystem out of the box.

If you are developing a Spring Boot application we recommend you to try out the devpack support for Spring  and then follow this tutorial to write your Spring Boot charm . 

But without further ado, let's see how it all works by charming spring-petclinic . 

Set up a developer machine with Canonical Kubernetes and Juju

We will start with a virtual machine created from scratch using Multipass  and prepare our development machine with the help of the Concierge  tool.

Launch the new virtual machine and shell into it:

multipass launch --cpus 4 --disk 30G --memory 4G --name blogpost 24.04

multipass shell blogpost

We will provision the testing machine with Concierge, which will install and configure Rockcraft, Charmcraft, Canonical Kubernetes and Juju. Besides that, we will update the load balancer to serve under the machine's main IP and install an OCI image registry:

sudo snap install --classic concierge
sudo concierge prepare -p k8s --charmcraft-channel latest/edge
PREFSRC=$(ip -4 -j route get 2.2.2.2 | jq -r '.[] | .prefsrc')
sudo k8s set load-balancer.cidrs=$PREFSRC/32
curl https://raw.githubusercontent.com/canonical/spring-petclinic/refs/heads/resources/registry.yaml | kubectl apply -f - 

Get spring-petclinic application

spring-petclinic  is the app we'll be charming. It's a sample application created by the Spring team to demonstrate a real-world web app using the Spring Framework. 

Clone the spring-petclinic repository. 

git clone https://github.com/canonical/spring-petclinic.git

cd spring-petclinic

Following the spring-petclinic repository instructions , you can build a jar and run it with the command line. It is quite easy, but clearly not production ready, even the database in-memory.

Create the rock

Let's prepare a rock – a compliant OCI image – for the application. We could use either Maven or Gradle to build the application, but for this example we will use Maven. From the spring-petclinic directory, remove the Gradle artifacts and initialize the rockcraft project:

rm -rf build.gradle gradlew gradle
rockcraft init --profile spring-boot-framework

Pack the rock and upload it to the OCI registry :

ROCKCRAFT_ENABLE_EXPERIMENTAL_EXTENSIONS=True rockcraft pack
rockcraft.skopeo copy --insecure-policy --dest-tls-verify=false oci-archive:spring-petclinic_0.1_amd64.rock docker://localhost:32000/spring-petclinic:0.1

At this point we have a fully compliant OCI image. But to fully integrate with the Juju ecosystem we need a charm, a software operator. 

Create the charm

Let's build it:

mkdir charm
cd charm
charmcraft init --profile spring-boot-framework --name spring-petclinic

As we want to use PostgreSQL instead of an in-memory database, add the following lines to the file charmcraft.yaml:

requires:
postgresql:
interface: postgresql_client
optional: false
limit: 1

And we are ready to create a charm. Pack it:

CHARMCRAFT_ENABLE_EXPERIMENTAL_EXTENSIONS=True charmcraft pack

Let's test it

At this point we have a charm for spring-petclinic that will integrate seamlessly with PostgreSQL. 

Let's test it with a new Juju model in a Kubernetes cloud:

juju add-model spring-petclinic
juju deploy ./spring-petclinic_amd64.charm spring-petclinic --resource app-image=localhost:32000/spring-petclinic:0.1 --config app-profiles=postgres

Deploy PostgreSQL and Traefik and integrate with spring-petclinic:

juju deploy postgresql-k8s --trust
juju integrate spring-petclinic postgresql-k8s

juju deploy traefik-k8s --trust
juju integrate spring-petclinic traefik-k8s

After a while, your production ready application will be ready for use! You can check it with the command juju status:



You can get the URL of the application with:

juju run traefik-k8s/0 show-proxied-endpoints

And just like that, you can use it!



The application is running in a Kubernetes cluster, with Trafik acting as an ingress. Your spring-petclinic application is now using PostgreSQL to store its data. The Charmed PostgreSQL K8s has provided credentials for the database to the spring-petclinic application, and is ready to be operated in a production-grade environment. 

Not bad for a start.

Get in touch

Do you have a project or setup where you want to employ this solution? If you have any questions about the 12-factor tooling for Rockcraft and Charmcraft, reach out in our Matrix Channel .

What's next?

• Follow the Spring Boot tutorial
• Publish your charm in CharmHub

In this article we walk through the steps required to deploy a Spring Boot application to production using Juju and Kubernetes. The goal is to showcase the integration of the application with essential services like PostgreSQL for database management and Traefik for ingress control.


Categories: charm, Charms, cloud, Juju, juju charms, kubernetes
Source: https://ubuntu.com//blog/deploy-spring-application-to-production Jan 13, 2026, 02:00 PM

Opera GX Gaming Browser is Coming to Linux

Opera confirms it's working on a Linux version of Opera GX, its gaming-focused browser. No release date yet, but after years of users asking it's happening.

You're reading Opera GX Gaming Browser is Coming to Linux , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: News, Opera, Web Browsers
Source: https://www.omgubuntu.co.uk/2026/01/opera-gx-linux-version-being-worked-on Jan 16, 2026, 02:21 AM

Raspberry Pi AI HAT+ 2 Lets You Run LLMs Locally

The Raspberry Pi AI HAT+ 2 costs $130 but with 40 TOPS and 8GB of onboard RAM it can run LLMs like Qwen 2 and DeepSeek R1 locally, opening up new use cases.

You're reading Raspberry Pi AI HAT+ 2 Lets You Run LLMs Locally , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: Hardware, News, AI/ML, raspberry pi
Source: https://www.omgubuntu.co.uk/2026/01/raspberry-pi-ai-hat-2-runs-llms Jan 15, 2026, 08:31 PM