AHXproject

Raspberry Pi launch 10-inch Touch Display 2 for $80

Raspberry Pi has launched a 10-inch version of its Touch Display 2 with a 1200×1920 resolution and 10-point captive touchscreen for $80/£77. 5-inch and 7-inch variants of the Touch Display 2 have been available for a while, but Raspberry Pi's Gordon Hollingworth says the new version gives makers a larger, higher resolution screen to use in their projects. Like the smaller versions, the 10.1″ Touch Display 2 uses a portrait orientation by default, where the displays are often used for home automation dashboards, kiosks, digital signage, control panels, etc. It can be used in landscape by changing the orientation in [...]

You're reading Raspberry Pi launch 10-inch Touch Display 2 for $80 , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: Hardware, News, Raspberry Pi, touchscreen
Source: https://www.omgubuntu.co.uk/2026/07/raspberry-pi-10-inch-touch-display Jul 22, 2026, 05:41 PM

Ubuntu 26.10 adds Ubuntu Certified check to Settings

Wondering if your laptop or desktop PC is Ubuntu Certified? Ubuntu 26.10 is adding a new way to check from the Settings app. A new row in Settings > System > About reads "check if this computer is Ubuntu Certified". Clicking it opens a new page that will read the local/cached status from the com.ubuntu.hwctl service (the Canonical hardware API introduced in 2025). Ubuntu's has had a command-line way to check certification for a while, using hwlib. In 26.10 (Stonking Stingray), you'll be able to check it via Settings rather than through terminal command. The statuses which can be shown: There's also an [...]

You're reading Ubuntu 26.10 adds Ubuntu Certified check to Settings , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: News, Ubuntu 26.10, Ubuntu Certified
Source: https://www.omgubuntu.co.uk/2026/07/ubuntu-2610-certified-hardware-check Jul 22, 2026, 01:56 AM

Canonical announces the Enterprise Store as part of Ubuntu Pro

Canonical introduces a new way to manage software behind firewalls and in air-gapped environments with the Enterprise Store.

The Enterprise Store makes software distribution manageable and scalable behind firewalls or in air-gapped environments. Available with an Ubuntu Pro subscription, the Enterprise Store respects the security protocols of strict environments, in a way that is controllable, auditable, and predictable. 

What is the Enterprise Store?

The Enterprise Store  is an on-premise edge proxy. It sits between your devices and Canonical's software stores, so your systems can install and update software without needing direct outbound access from every machine. That makes it a strong fit for:

• Corporate networks with strict egress controls
• Air-gapped and offline environments
• Regulated industries that need change control and auditability 

In order to meet the needs of these strict environments, the Enterprise Store is designed around a few practical capabilities:

• Local caching to speed up repeat downloads and reduce bandwidth use.
• Air-gapped operation (offline mode) so updates can be manually transferred when there's no internet connectivity.
• High availability options to reduce the risk of service interruption.
• Granular revision control so you can pin versions and avoid surprises during critical operations.

High availability

The Enterprise Store supports high availability, giving teams a more resilient way to run software distribution in production. Instead of relying on a single machine to serve every client request, organizations can deploy multiple Enterprise Store instances behind a reverse proxy, allowing traffic to be routed to another live unit if one goes down. That reduces the risk of a single-node failure interrupting access to packages, updates, or operator software across connected systems.

This high-availability model is designed for real operational environments. Reverse proxies can balance traffic and run health checks across backend units, while shared services help keep states consistent across the deployment. The result is a more robust control point for software distribution: one that helps teams maintain continuity, consistency, and tighter operational control even in restricted or business-critical environments.

One proxy for snaps and charms

The Enterprise Store gives teams a single proxy to manage both snaps and charms, covering the full software lifecycle from delivery to operations. 

Snaps are self-contained Linux packages that are easy to install, update, and maintain across desktop, cloud, and IoT environments. Charms are operators: software that wraps an application and contains the logic needed to deploy, configure, scale, integrate, and manage it over time. Together, they cover both software delivery and software operations.

Many organizations use snaps to package and distribute software consistently, and charms to automate deployment and lifecycle management for applications across clouds and clusters. With a unified approach to network controls and governance, the Enterprise Store helps organizations manage their entire software estate consistently. 

Included with Ubuntu Pro

The Enterprise Store is included as part ofUbuntu Pro , which means anyone with an Ubuntu Pro subscription can try it. If you're experimenting at home or in a lab, you can get started today.

Ubuntu Pro  is free for personal use (for up to 5 machines), so you can get hands-on with the Enterprise Store before you roll it into a broader evaluation.

Get started

If you want to explore and set up the Enterprise Store:

• Read theEnterprise Store overview  to understand use cases and key features.
• Follow thedocumentation : the docs hub includes getting started guides and sections covering charm support.
• Reach out  to Canonical if you have commercial requirements, larger-scale rollouts, or want guidance for a regulated environment.

Talk to us about your use case

If you're looking at the Enterprise Store for production, especially across fleets, air-gapped environments, or compliance-bound ecosystems, Canonical can help you plan an evaluation, architecture, and rollout plan.

Contact us  and tell us about your requirements and use cases.

Further reading

• Enterprise Store overview
• Enterprise Store documentation
• Ubuntu Pro  (free for personal use)

Canonical introduces a new way to manage software behind firewalls and in air-gapped environments with the Enterprise Store. The Enterprise Store makes software distribution manageable and scalable behind firewalls or in air-gapped environments. Available with an Ubuntu Pro subscription, the Enterprise Store respects the security protocols of strict environments, in a way that is controllable, [...]


Categories: IoT app stores, Ubuntu Pro
Source: https://ubuntu.com//blog/canonical-announces-the-enterprise-store Jul 21, 2026, 05:25 PM

Firefox 153 released with buil-in containers, QR Code generator + more

Mozilla has released Firefox 153 with built-in containers, QR code generation and more quick actions in the address bar. This is the final "monthly" stable release before Mozilla shifts to a faster releases cadence, with new versions of Firefox coming out every two weeks. Like all updates, you can get this one for Windows, macOS and Linux, as well as for Android and iOS (mobile versions have different features and are not covered in this post). Firefox gets built-in Containers Containers are the biggest new feature in Firefox 153. These, Mozilla say, let you "separate cookies by container so you [...]

You're reading Firefox 153 released with buil-in containers, QR Code generator + more , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: News, Containers, Firefox, Mozilla
Source: https://www.omgubuntu.co.uk/2026/07/firefox-153-new-containers-feature Jul 21, 2026, 01:57 AM

Tracing a memory leak bug in PID 1 and contributing an upstream fix: a Linux support story

Some memory leaks are straightforward to detect. A process allocates memory, forgets to free it, and grows until something breaks. This was not that kind of leak.

This is the story of how Canonical Support helped a global retail organization trace the cause for an unusual memory leak originating in PID 1, the very first process started by the kernel during the system boot sequence. The memory footprint was 10 times higher than expected. By investigating the issue across three separate system layers – a misconfigured storage orchestrator, a kernel race condition, and glibc's allocator – our team was able to identify the source and fast-track a patch. 

The symptom that made no sense

The customer was the innovation and engineering arm of a global retail company. They were responsible for driving the company's retail transformation –  operating a fleet of servers running as part of a Ceph storage cluster. Across several of these cluster nodes, they began observing a pattern that made no immediate sense: /sbin/init (a symlink to systemd, which was running as PID 1) was consuming over 50% of available system memory. On servers with 125 GB of RAM, that meant PID 1 alone was holding approximately 70 GB, when only 8 GB were expected. The systems were experiencing out-of-memory kills, with the kernel forcibly terminating processes to free up available memory to survive.

Nothing in the obvious diagnostic places explained it. Memory consumption continued to grow, and was never released. The investigation didn't point to any obvious application-level cause. The customer had ruled out the workloads running on the servers as being the issue. The problem was somewhere deeper, below the application layer.

Starting the investigation: getting the right artifact

The support team at Canonical's first move was to request sos-reports from the affected nodes, the standard starting point for system-level investigation. But sos-report output, comprehensive as it is, didn't contain anything that explained a 70 GB footprint on PID 1. The next step was more direct: the engineer requested a core dump of PID 1 itself, generated with gcore 1.

This is not a routine ask. Generating a core dump of the init process (PID 1) on a running production system is the technical equivalent of performing open-heart surgery while the patient is running a marathon. PID 1 is not just any process; it is the root of the entire user-space ecosystem. If it stumbles, the whole system collapses. Because the resulting file is massive – In this case the core dump compressed from 70 GiB to less than 10 GiB, a major red flag that there was significant repetition in the memory of the process –, transferring, downloading, and analyzing it can significantly delay the start of troubleshooting, and the investigation itself can take an unpredictable amount of time. The customer uploaded it, and that artifact is what cracked the case open.

The diagnostic leap: from memory to mounts

Analyzing the core dump, the Canonical engineer could see directly what was occupying PID 1's memory. The footprint was tied to mount table entries. Specifically, entries from runs of a ceph-volume Docker container. The mount table, which systemd maintains and reparses every time changes are made, had grown to millions of entries.

The behavior of systemd here is by design: it watches /proc/self/mountinfo and reparses the full table on every change. Under normal conditions, reparsing is not an issue, but because the table was now very large, continuously regenerating it caused serious issues. Each time systemd parsed it, glibc's allocator retained the memory rather than returning it to the kernel. The memory accumulated but was never freed.

That explained the mechanism, but it didn't yet explain why the mount table had grown so large, or why ceph-volume containers were running so frequently.

The second leap: a silent failure nobody knew about

This is where the investigation crossed layers.

Tracing the frequency of ceph-volume container activity, the engineer identified the actual source: a cephadm process – part of the Ceph orchestration layer – was repeatedly attempting to "zap" (a destructive operation that wipes all data and metadata from a disk to reset it to a clean state) an OSD (Object Storage Daemon) that no longer existed. Because there was no Logical Volume associated with it, the operation failed every time. And every time it failed, it retried. The ceph-volume Docker container was spinning up and tearing down in a continuous loop.

Nobody had flagged this because the orchestration layer in Ceph was silently failing, and the only visible symptom, the one that brought the customer to Canonical Support, was 70 GB of memory consumed by PID 1 on nodes that had nothing obviously wrong with them.

Stopping the loop was the workaround. Once cephadm was corrected and the repeated zap attempts ceased, the mount/unmount thrashing stopped, the race condition stopped triggering, and memory usage stabilized. The customer confirmed that the correction resolved the immediate problem.

Once a workaround was implemented, the Canonical team was able to shift their attention to finding a permanent fix. 

From diagnosis to upstream

Canonical's support engineers traced the bug to the upstream code and regularly engaged with  the open source community to implement a fix that extended beyond the immediate customer. By providing Linux kernel maintainers with a fully characterized bug and a verified trigger, they secured a resolution that benefited the entire open source ecosystem.

By shrinking the problem to a minimal reproducer, mounting and unmounting a tmpfs in a tight loop, the team isolated the precise, reproducible mechanism: a kernel race condition. This churn caused mount table entries to intermittently spike to millions of lines, triggering continuous systemd reparsing and glibc memory retention, which resulted in the 70 GB footprint on PID 1. 

The patch was merged into the mainline kernel. After passing through the Stable Release Update (SRU)  process, the fix landed in several Ubuntu kernel releases.

Why this case stands out

What looked like a  memory leak wasn't quite the whole story. While the memory was being properly freed by systemd and tracked by glibc, it became unusable to the rest of the system, effectively starving the node. The real issue was that a silent misconfiguration in a storage orchestration layer, cephadm looping on a non-existent OSD, was the trigger for a kernel-level race condition that manifested as an inexplicably large footprint. No single layer told the full story: 

• The sos-report pointed toward the symptom. 
• The core dump identified the mechanism. 
• Tracing the container activity identified the trigger. Only then was there enough precision to take the problem upstream.

That chain, from production symptom to cross-layer diagnosis to mainline kernel patch, is what enterprise Linux support looks like when the problem isn't immediately obvious and doesn't fit a known category.

If you want to understand what support from Canonical can bring to complex infrastructure problems, visit our support page , or, get in touch .

How Canonical Support helped a global retail organization trace the cause for an unusual memory leak originating in PID 1. By investigating the issue across three separate system layers our team was able to identify the source and fast-track a patch.


Categories: Bug-fix support, Support, Ubuntu Pro
Source: https://ubuntu.com//blog/fixing-memory-bug Jul 17, 2026, 11:04 AM

Ubuntu's desktop icons extension completes its GTK4 port

The Desktop Icons NG (aka DING) GNOME Shell extension Ubuntu uses to put icons on your literal desktop, has been busy – it finished its port to GTK4, patched memory leaks and improved a few of its lesser-known features. The GTK4 port landed in v51.0.0, released this month, alongside early support for GNOME 51 (since that's the GNOME version Ubuntu 26.10 will ship with in October). Prior to that, there were other, smaller in June with fixes for memory leaks and buffs to usability. DING's GTK4 port – not to be confused with a separate GTK4 fork I covered back in [...]

You're reading Ubuntu's desktop icons extension completes its GTK4 port , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: News, desktop icons, GNOME Extensions, Ubuntu 26.10
Source: https://www.omgubuntu.co.uk/2026/07/ubuntu-desktop-icons-extension-gtk4-port Jul 20, 2026, 01:04 AM

This theme makes Discord look more at home on Ubuntu

The official Discord desktop app supports Linux but it doesn't make much effort to fit in, which is why alternative clients are popular – not least because they can be themed. Discord GNOME Theme by developer ~ricewind012, is so named because, basically, that's what it is: a custom theme that restyles Discord to look more like Adwaita and follow the GNOME HIG (well, as close as Discord's CSS allows). A reminder: Ubuntu's Yaru theme is based (heavily) on upstream Adwaita, so while this theme won't give an exact match on Ubuntu, it's closer than stock. As it's all CSS, it [...]

You're reading This theme makes Discord look more at home on Ubuntu , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: News, adwaita, discord, Eye Candy
Source: https://www.omgubuntu.co.uk/2026/07/discord-gnome-theme-adwaita-vesktop Jul 19, 2026, 12:19 AM

Flathub's AI slop ban looks like it was the right call

When Flathub banned AI-coded app submissions last month, some critics warned the platform was denying the future by dismissing a new wave of "vibe-coded" software as out-and-out "slop". Well, new data suggests otherwise, as nearly three-quarters of the rejected apps are already dead, existing only a few months. Linux developer Evangelos Paterakis, developer of Tuba, Turntable and others, did the digging, looking at 120 code repositories whose pull requests for inclusion on Flathub were rejected because of their heavy AI usage and given an "AI Slop" tag. Of those rejected, 88 are no longer under active development, many having deleted their [...]

You're reading Flathub's AI slop ban looks like it was the right call , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: News, AI/ML, flathub
Source: https://www.omgubuntu.co.uk/2026/07/flathub-ai-slop-ban-data Jul 17, 2026, 10:53 PM

Ubuntu 26.04 fixes trash dialog bug that defaulted to cancel

Ubuntu 26.04 LTS is getting a fix for Nautilus that restores 'Delete' as the focused button in the trash confirmation dialog, undoing an accidental swap that made 'Cancel' the focused button instead. That 'unintentional' focus flip meant you could no longer hit enter to action file deletion for Trash since it instead cancelled it. I've lost count of the times I've assumed I emptied the trash since upgrading to Ubuntu 26.04 LTS, only to find I hadn't. My muscle memory has struggled to adapt to needing to explicitly click (or tab to) the delete button. Annoying, but thankfully not intentional. [...]

You're reading Ubuntu 26.04 fixes trash dialog bug that defaulted to cancel , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: News, Bug Fixes, Nautilus, Ubuntu 26.04 LTS
Source: https://www.omgubuntu.co.uk/2026/07/ubuntu-26-04-trash-dialog-cancel-button-fix Jul 16, 2026, 06:06 PM

Firefox is getting updates twice as fast from September

Mozilla is changing Firefox's release schedule from September, with new stable versions planned every two weeks instead of once a month. The faster release cadence will, Mozilla says, make its schedule more predictable and give "work that is ready to ship more frequent opportunities to reach users". In a message to developers, Mozilla describes the change as an experiment it will "closely monitor" to ensure that the impact is positive and "adjust if needed". Firefox 154, due for release on 18 August, will be the final stable version released under the current schedule. Firefox 155 is then planned for 1 [...]

You're reading Firefox is getting updates twice as fast from September , a blog post from OMG! Ubuntu . Do not reproduce elsewhere without permission.


Categories: News, Firefox
Source: https://www.omgubuntu.co.uk/2026/07/firefox-two-week-release-cycle Jul 15, 2026, 10:36 PM