The Wellbeing controls available in Ubuntu 25.04 make it easy to get periodic prompts to move your butt or look away from your screen - you might not want them enabled all the time, though. Wellbeing controls were one of the flagship features of GNOME 48. As well as screen time monitoring (with controls to set a screen time limit, and turn the display greyscale when it's reached), you can enable reminders to take a break and move. Alerts telling you to get up and move may be helpful during the day, but at nighttime when you're, say, engrossed in […]

You're reading Easily Toggle Ubuntu's New Wellbeing Reminders On/Off, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

08 May 2025 10:26pm GMT

We are pleased to announce that the Plasma 6.3.5 bugfix update is now available for Kubuntu 25.04 Plucky Puffin in our backports PPA.

As usual with our PPAs, there is the caveat that the PPA may receive additional updates and new releases of KDE Plasma, Gear (Apps), and Frameworks, plus other apps and required libraries. Users should always review proposed updates to decide whether they wish to receive them.

To upgrade:

Add the following repository to your software sources list:

ppa:kubuntu-ppa/backports

or if it is already added, the updates should become available via your preferred update method.

The PPA can be added manually in the Konsole terminal with the command:

sudo add-apt-repository ppa:kubuntu-ppa/backports

and packages then updated with

sudo apt full-upgrade

We hope you enjoy using Plasma 6.3.5!

Issues with Plasma itself can be reported on the KDE bugtracker [1]. In the case of packaging or other issues, please provide feedback on our mailing list [2], and/or file a bug against our PPA packages [3].

1. KDE bugtracker::https://bugs.kde.org
2. Kubuntu-devel mailing list: https://lists.u
3. Kubuntu ppa bugs: https://bugs.launchpad.net/kubuntu-ppa

08 May 2025 6:28pm GMT

More details on the makeup of the upcoming Linux Mint 22.2 release have been revealed, including its new codename (for those who track those). Linux Mint 22.2 (due to be released in late July or early August) has been officially named 'Zara', so continuing distro lead Clem's codename convention of choosing female names in (somewhat) alphabetical order for each new version. I only say somewhat since Linux Mint 22.1 release was dubbed 'Xia', while Linux Mint 22.2 jumps straight to 'Zara'. Even with my lackadaisical attention to letter ordering, I know a 'Y' comes between 'X' and 'Z'. Perhaps Clem […]

You're reading Linux Mint 22.2 Modernises its Default Theme, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

08 May 2025 2:29pm GMT

A Canonical levou o Miguel a redescobrir o conforto da gama de sofás-cama do IKEA e entretanto, o Diogo trouxe um saco cheio de prendas, que incluem reflexões sobre direitos digitais e privacidade em tempo de eleições, uma obsessão acumuladora com arquivos, papéis, facturas, revistas velhas e jornais cheios de pó digital e ainda uma catrefada de extensões de Firefox para todos os usos e gostos - ou não fosse isto o Podcast Firefox Portugal, o podcast sobre Firefox, a Mozilla e outras cenas.

Já sabem: oiçam, subscrevam e partilhem!

• Perfis Compartimentados no Firefox: https://support.mozilla.org/pt-PT/kb/profile-management
• Podcast Voz dos Direitos Digitais - Programas eleitorais:
  • https://direitosdigitais.libsyn.com/
  • https://direitosdigitais.libsyn.com/ep-05-eleies-legislativas-2024
  • https://direitosdigitais.libsyn.com/ep-09-legislativas-2025-programa-do-volt
  • https://direitosdigitais.libsyn.com/ep-10-legislativas-2025-programa-do-pcp
  • https://direitosdigitais.libsyn.com/ep-11-legislativas-2025-programa-da-ad
  • https://direitosdigitais.libsyn.com/ep-12-legislativas-2025-programa-do-be
  • https://direitosdigitais.libsyn.com/ep-12-legislativas-2025-programa-do-ps
• Debate Soberania Digital na Festa do Software Livre: https://viste.pt/w/5zNPsAp4EqtEVXNWopoJ35
• Monolith: https://snapcraft.io/monolith
• Waybackpy
  • https://github.com/akamhy/waybackpy?tab=readme-ov-file
  • https://github.com/akamhy/waybackpy/wiki/CLI-docs#save
  • https://snapcraft.io/waybackpy
• Arquivar PDF
  • https://docs.paperless-ngx.com/
  • https://apps.nextcloud.com/apps/integration_paperless
  • https://nerdyarticles.com/a-clutter-free-life-with-paperless-ngx/
  • https://www.youtube.com/watch?v=NcpOnOcMoA0 Extensões para Firefox:
  • https://addons.mozilla.org/pt-PT/firefox/addon/view-page-archive/
  • https://web.archive.org/web/2/https://addons.mozilla.org/pt-PT/firefox/addon/view-page-archive/
  • https://github.com/dessant/web-archives
• Internet Archive: https://addons.mozilla.org/pt-PT/firefox/user/12373129/
• Firefox Multi-Account Containers: https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/
• Temporary Containers: https://addons.mozilla.org/en-US/firefox/addon/temporary-containers/
• Search by image
  • https://addons.mozilla.org/pt-PT/firefox/addon/search_by_image/
  • https://web.archive.org/web/20250507131719/https://addons.mozilla.org/pt-PT/firefox/addon/search_by_image/
• Ping blocker
  • https://addons.mozilla.org/pt-PT/firefox/addon/ping-blocker/
  • https://apps.armin.dev/ping-spotter/
  • https://github.com/dessant/ping-blocker
• Captcha buster
  • https://addons.mozilla.org/pt-PT/firefox/addon/buster-captcha-solver/
  • https://github.com/dessant/buster
  • https://github.com/dessant/buster/wiki/Inaccessible-reCAPTCHA-audio-challenge
• ClearURLs
  • Removes tracking elements from URLs
  • https://addons.mozilla.org/pt-PT/firefox/addon/clearurls/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search
• Firefox Color
  • https://addons.mozilla.org/pt-PT/firefox/addon/firefox-color/
• Ubuntu Touch Q&A 163: https://www.youtube.com/watch?v=4ksTW_ypmwM
• LoCo PT: https://loco.ubuntu.com/teams/ubuntu-pt/
• Mastodon: https://masto.pt/@pup
• Youtube: https://youtube.com/PodcastUbuntuPortugal

Atribuição e licenças

Este episódio foi produzido por Diogo Constantino, Miguel e Tiago Carrondo e editado pelo Senhor Podcast. O website é produzido por Tiago Carrondo e o código aberto está licenciado nos termos da Licença MIT. (https://creativecommons.org/licenses/by/4.0/). A música do genérico é: "Won't see it comin' (Feat Aequality & N'sorte d'autruche)", por Alpha Hydrae e está licenciada nos termos da CC0 1.0 Universal License. Este episódio e a imagem utilizada estão licenciados nos termos da licença: Attribution-NonCommercial-NoDerivatives 4.0 International (CC BY-NC-ND 4.0), cujo texto integral pode ser lido aqui. Estamos abertos a licenciar para permitir outros tipos de utilização, contactem-nos para validação e autorização. A arte de episódio foi criada por encomenda pela Shizamura - artista, ilustradora e autora de BD. Podem ficar a conhecer melhor a Shizamura na Ciberlândia e no seu sítio web.

08 May 2025 12:00am GMT

I've written about the EU Cyber Resilience Act (CRA) on our Canonical blog a few times now, and I think now's the perfect time to talk about the implications of this new regulation and what it means for IoT and device manufacturers on the practical level of how they design and build Products with Digital Elements (PDEs).

In this blog, I'll give you a thorough overview of common IoT manufacturer and PDE developer practices that need immediate attention, and how to change or improve these practices so that your work and PDEs can keep their place on the EU market with full CRA compliance.

What you can't do under the CRA (and what to do instead)

In general, the things you can and cannot do under that CRA depend on how you and your PDEs are classified or categorized under this new piece of legislation. If you're not familiar with the CRA's wording, classifications, and requirements, you can catch up on the specifics by reading the previous articles I wrote here:

• A CISO's comprehensive breakdown of the CRA: Catch up on what the EU Cyber Resilience Act is, what the CRA requirements are, and how it will broadly affect cybersecurity design, documentation, and long-term support and vulnerability management for devices.
• What the CRA means for IoT manufacturers: Explore how the CRA will affect all IoT manufacturers looking to market their devices and products in the EU.
• How the CRA will affect open source software: Get an overarching insight into how the CRA came about, the community reaction to this regulation, and what it means for open source going forward.

However, outside of the category- and classification-specific requirements of the CRA, this regulation introduces an extremely broad set of changes to IoT and PDE cybersecurity and vulnerability management that will affect everyone, regardless of where they fall under the CRA's specific wording.

Let's take a closer look:

No more passing the buck

No more passing security responsibility to your downstream users or expecting that your upstream providers will take care of vulnerabilities. In fact, building and shipping things often means you will be categorized as a manufacturer, which means that you will be burdened with an increased level of compliance assessment and higher demands for PDE compliance.

If you don't want to bear the brunt of Manufacturer compliance, you should find a supplier willing to assume that responsibility.

You can no longer hide behind documentation - or treat it as optional

You can no longer hide behind documentation. If there are vulnerabilities, limitations, or flaws in the PDE, or specific outlines for its use, you cannot simply expect users to have fully read your documentation and follow these hard-to-find instructions to use your product safely.

On a practical level, this means that instead of simply documenting vulnerabilities and communication - for example, telling users not to use the device on unsecured networks, to change the password before use, or to manually disable certain ports or features before use. It's no longer enough to document vulnerabilities and then warn users about them: you need to patch them yourself.

And when it comes to documentation, the CRA outlines stricter requirements for how to approach your docs and make them accessible. In general, the CRA means you will have new documentation requirements, with more communication around where this documentation can be accessed, and you'll need to produce a software supply chain and formal software bill of materials (SBOM) that is accessible and machine readable.

As a minimum, you need to have the following documented and available for the public and EU authorities:

• A description of the design, development, and vulnerability handling process
• An assessment of cybersecurity risks
• A list of harmonised EU cybersecurity standards the product meets
• A signed EU Declaration of Conformity that the above essential requirements have been met
• A Software Bill of Materials (SBOM) documenting vulnerabilities and components in the product

You can no longer hide behind intention

It's not just documentation that you can't use as a crutch or shield - intention is out too.

This means that you can't defend flaws, design issues, or vulnerabilities as intentional design choices. For example, if your device has ports, features, or functionality that could reasonably be used to access the device or connect to networks, you need to take steps to mitigate the risks and attack vectors that these elements pose.

In the next section, we'll go through some of the practical steps you can take to address device cybersecurity.

The security basics are no longer optional

Many of the requirements of the CRA simply formalize cybersecurity practices and security features that should be considered as minimum standards. By this I'm referring to things like shipping with known vulnerabilities, expecting users and consumers to secure your devices after purchase, ignoring cybersecurity fundamentals like no default admin-password credentials, or hiding behind obscure or inadequate documentation.

Some of these cybersecurity essentials include:

• Ensuring that whatever you're building is as secure as it can be. It must have minimal attack surfaces.
• Hardening your device or product. Its data must be encrypted or protected and it must prevent unauthorized access.
• Preventing downtime. Your device must keep working, even under DDoS attack, and it mustn't interrupt other devices, even when attacked with exploits.
• Keeping track of activity. Your device needs to be able to provide security data by monitoring or logging changes in the device.
• Proactive patching. Your product needs to be able to receive security updates or rollbacks. This includes direct or remote updates, user notifications about updates, and the ability to roll back updates or reset the product to a factory/default state.

Even without the CRA compelling you to meet higher cybersecurity standards, you should be meeting these basic standards in PDE security design. Here are some steps you could take to ensure your PDEs are as robust and secure as possible before they reach the market:

• Implement a Zero Trust Architecture wherever possible
• Ensure that your authentication, authorization, and access control are fully secure (and that you have control over your credentials)
• Use Secure by Default configurations
• Minimize your attack surface - if your device, system, or organization isn't actively using something (whether it's a port, component, or package), then disable it by default until it's needed
• Ensure proper use of cryptography to ensure data is protected at rest and in transfer, that traffic is encrypted, and that you avoid plaintext or cleartext data
• Validate all input and handle all exceptions
• Secure all individual components and their dependencies, not just the stack
• Minimize the access permissions of apps and systems, and design your baseline to stop server-side request forgery from Day Zero
• Use automated security patching software to ensure that validated and authenticated security updates, CVE fixes, and other patches are downloaded timeously and automatically

In short, the goldrush of taking unsafe IoT devices to market is over: consumers have higher expectations for the security and privacy of the devices they use, and if your products don't meet them, it will lead only to disaster down the line. We understand the serious impacts that CVEs have on users and businesses alike, which is why we take such a strong commitment to patching critical CVEs within 24 hours through Ubuntu Pro.

Ubuntu Pro gives organizations a hands-free, automated way of receiving vital software packages and security updates for up to 12 years, ensuring that they're covered no matter what new vulnerabilities or regulatory compliance comes up.

You can no longer ignore products after launch

Another priority you should focus on is patching and vulnerability management for your devices and software. One of the CRA's primary requirements is to ensure that your devices can be securely updated against new vulnerabilities. Your updates must be free and sent out as soon as vulnerabilities are discovered, along with information to users about what actions they should take.

When this happens, you need to provide:

• A description of the vulnerabilities and their severity
• Information allowing users to identify the product with digital elements affected
• The impacts of the vulnerabilities
• Information helping users to remediate the vulnerabilities

What's more, these patching and security update efforts must be long term, and cover the PDE's entire lifecycle. You must regularly test the product, and fix vulnerabilities immediately - and once a fix has been applied, you need to publicly disclose what the fixed vulnerability was (in line with the new coordinated public disclosure policy you need to have, under the CRA).

And for a period of a maximum of 5 years (or the product lifespan, whichever is shorter) you'll be required to recall or withdraw products that don't meet conformity standards of the CRA.

Get vital CRA compliance insights in our CRA compliance guide video

No more hidden or gray dependencies

Whether you're classified as a manufacturer or not, you still need to think about your software supply chain like a manufacturer does. This is because the CRA introduces new requirements for documentation, transparent software supply chains, and a software bill of materials to show your software is securely sourced. As a minimum, you should be consuming trusted open source only, or only sourcing packages from trusted suppliers.

If you're unsure about your software supply chain and its ability to meet the CRA's regulatory standards, documentation requirements, vulnerability disclosure demands and transparency expectations, you should evaluate your service and software providers to choose those who make it effortless to meet your CRA obligations.

Generally, this means picking a vendor who meets one of the following criteria:

• Has a CE marking
• Can provide supply chain certification
• Has decided to take on the category of 'Manufacturer'

Our recommendation is to consume packages or software updates from large and trusted suppliers who have taken on responsibility for CRA compliance. This means that you should be sourcing versions of your open source software, (or security patches for that software) directly from a vendor who has decided to take on the category of 'Manufacturer' in the software supply chain.

At Canonical we understand how important this is, which is why we've committed to meeting the manufacturer responsibilities for many of our products. The many, many tools and products we develop and maintain at Canonical - Ubuntu; our distributions of Kubernetes, MicroCloud, and OpenStack; and more - are designed with security in mind, supported through security maintenance and vulnerability patching, and aligned with the regulatory oversight in the CRA. On top of this, services like Ubuntu Pro for Devices ensure your devices will receive security maintenance for up to 12 years.

No more "market-first" approach

The days of "move fast and break things" are over. Under the CRA, you cannot hyperfocus on market timing or a launch date and ship an MVP that skimps on security design and long-term support. Instead, you need to build on a strong foundation for security and support for your packages and software that extends for many years past your launch date.

You should be reassessing your choices - of OS, development environment, and software vendors - to meet this new change. And the systems you do choose should give both the robust baseline of security and the long-term security support the CRA requires - as well as the minimized attack surface that reduces the number of attack vectors and vulnerabilities as much as possible.

Luckily, this has benefits that go beyond security: a minimized attack surface, device-optimized OS, or containerized build keeps everything to the smallest footprint possible - which means faster performance, lower device specification requirements, and cheaper manufacturing costs. In fact, Ubuntu Core (the embedded Linux OS for devices) takes these requirements and benefits to heart: it acts as a pared-down, strictly confined flavor of Ubuntu for embedded devices. Ubuntu Core has an optimized profile that's perfect for devices that have limited specifications or hardware but which still demand robust security, long-term maintenance, and high levels of on-device performance.

Summary of what you need to change to meet CRA compliance

In conclusion, the CRA means that a lot of things have changed. Gone are the days of hiding behind obscure documentation, passing the buck to manufacturers or users, or launching market-first, "fire-and-forget" devices with unknown dependencies and no support. However, by intensifying the security of your PDEs with cybersecurity basic practices, consuming trusted packages and security updates from a manufacturer-category supplier with a long-term support program, and building a clear list of your software supply chain and dependencies, you can easily meet these new requirements head-on, and access the EU market for years to come.

To sum everything up, if you want to meet the new challenges and requirements of the CRA head-on, you need to follow these simple 6 steps:

• Adopt best practices for PDE hardening and device security
• Implement cybersecurity hardening to the greatest extent possible
• Conduct your compliance assessment and testing as soon as you can
• Document everything and make it publicly available, along with SBOMs that show your software composition and dependencies
• Take a customer-first approach, and beware of rushing an MVP to market
• Pick vendors who take on manufacturer responsibility for packages/software

To find out more about how Canonical can help you to meet the EU Cyber Resilience Act requirements for your devices, visit or comprehensive CRA webpage at https://canonical.com/solutions/open-source-security/cyber-resilience-act or fill out this form to contact our team of compliance experts.

Learn more

Find out how you can design and support CRA-ready PDEs by bringing up to 12 years of automated security patching to your device by visiting www.ubuntu.com/pro

Learn how Ubuntu Core is ideal for your PDEs, IoT devices, and all embedded systems by visiting www.ubuntu.com/core

More reading

• Understand IoT security and IoT compliance across global markets [Free white paper]
• Read our CISO's full breakdown of the CRA
• Explore the impacts of the CRA on open source
• Cyber Resilience Act: Yocto or Ubuntu Core for embedded devices?
• What is SBOM? Software bill of materials explained
• What the CRA means for IoT manufacturers

07 May 2025 2:36pm GMT

In this blog, I'll give you a thorough overview of common IoT manufacturer and PDE developer practices that need immediate attention, and how to change or improve these practices so that you can pass CRA compliance.

07 May 2025 2:36pm GMT

Get early access to Ubuntu 25.10 'Questing Quokka' through official daily builds. Download, test and contribute to Ubuntu's development before its October release.

You're reading Ubuntu 25.10 Daily Builds Now Available to Download, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

07 May 2025 1:34pm GMT

Raspberry Pi has reduced the price on all 4GB and 8GB Compute Module 4 boards by $5-10, making embedded projects more affordable to try out.

You're reading Raspberry Pi Compute Module 4 Gets a Price Cut, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

06 May 2025 10:59pm GMT

Huawei has unwrapped its latest Linux notebook, the MateBook X Pro 2024 Linux Edition - alas, it's only available in China. The Windows-free MateBook X Pro 2024 uses the same hardware as the Windows version, but clocks in at CN¥300 cheaper thank to a lack of Windows license fee and a government subsidy discounting tech that, from what I can gather, use a domestic OS. Chinese consumers can reportedly claim an extra discount of CN¥2000 on the purchase price as part of a national subsidy to promote usage of homegrown tech in general. With US sanctions in play, Microsoft is reportedly not […]

You're reading Huawei MateBook X Pro 2024 (Linux Edition) Goes on Sale, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

06 May 2025 2:52pm GMT

Today, IBM announced the launch of their latest server: the new IBM LinuxONE Emperor 5. This fifth generation redefines IBM's LinuxONE system as their most secure and high-performing Linux computing platform for data, applications and trusted AI.

Canonical supports LinuxONE Emperor 5 with Ubuntu Server. Ubuntu is cost-efficient and easy to install and manage on the servers - all whilst enabling the most up-to-date LinuxONE hardware features. Ubuntu Server for IBM Z and LinuxONE is ready for deployment from day one.

This blog provides an overview of the IBM LinuxONE Emperor 5's key features, and will demonstrate why Ubuntu Server is the right choice of software to install.

The new system was developed towards three main aspects and goals:

1. Industry-leading cyber security and privacy

IBM LinuxONE Emperor 5 lets users deploy confidential containers, and use quantum-safe encryption which can be scaled and unified across an enterprise.

Ubuntu Server for IBM Z and LinuxONE is also designed with security in mind, making the perfect fit for the security features of the IBM LinuxONE 5 generation hardware.

Canonical uses high security cryptography algorithms and disables weak cryptography algorithms by default. Ubuntu Server for IBM Z and LinuxONE is one of the very first Linux distributions that introduced Secure Execution support (since 20.04), and provides support for pervasive encryption in all dimensions, be it data at-rest, in-flight, or in-use. Ubuntu Server for IBM Z and LinuxONE supports quantum-safe cryptography, requiring only two commands to do so, and making use of the IBM LinuxONE 5 generation's quantum-safe encryption becomes a transparent and easy process.

Canonical's Kernel Livepatch service (Pro) delivers kernel patches for high or critical vulnerabilities that can be applied to a running kernel, without needing immediate downtime, so the system can continue running.

Ubuntu is built for compliance, and has various security certifications including FIPS.

These are only the beginning - you can learn more about the wealth of inherent Ubuntu Security Features in our wiki.

2. Optimized IT for energy and cost savings

IBM's enterprise class of LinuxONE systems is renowned for its large-scale workload consolidation which can result in significant savings on energy, space, and operational costs.

These strengths improve with each new hardware generation, as overall resources and performance increase whilst maintaining the system's maximum energy consumption at a steady level. IBM LinuxONE Emperor 5 includes up to 208 customer cores, up to 64TB of memory, and introduces a simplified system IO architecture.

By choosing Ubuntu Pro to run on the IBM servers, you can get Expanded Security Maintenance for open source at a transparent rate with our unique drawer-based pricing. Learn more about the benefits of an Ubuntu Pro subscription here.

3. Built-in AI, engineered for better outcomes

On the IBM LinuxONE Emperor 5, you can develop AI models in a hybrid cloud and run inference alongside data and applications within a trusted execution environment (TEE), enhancing prediction accuracy using a multiple model AI approach with the integration AI accelerator in Telum II, and scale AI while maximizing energy efficiency. In addition, the previously announced Spyre is expected to become available in 2025, and will enable Generative AI applications to be developed and run.

Ubuntu is a popular choice for most AI and machine learning researchers. Ubuntu balances ease of use, compatibility with the larger AI stacks and popular frameworks, and support from the open-source community or commercial support through Ubuntu Pro.

Canonical is working hard to ensure Telum II (of LinuxONE 5) and the upcoming Spyre Accelerator card are supported on Ubuntu Server, allowing users to deploy a multiple AI model approach in the future and as well as hardware-assisted generative AI.

After 9 years of LinuxONE and IBM Z (s390x) platform support, Canonical is proud that Ubuntu Server plays a central role in open source workloads, helping to make LinuxONE 5 generation easier to use, more secure, more reliable, and available to all at scale.

Download Ubuntu Server for IBM Z and LinuxONE

For more information about IBM LinuxONE Emperor 5, visit www.ibm.com/products/linuxone-5

Or if you have any questions, you can contact us directly:

Valerie Noto, Alliance Business Director - valerie.noto@canonical.com

Frank Heimes, Staff Engineer - frank.heimes@canonical.com

06 May 2025 3:59am GMT

Today, IBM announced the launch of their latest server: the new IBM LinuxONE Emperor 5. This fifth generation redefines IBM's LinuxONE system as their most secure and high-performing Linux computing platform for data, applications and trusted AI. Canonical supports LinuxONE Emperor 5 with Ubuntu Server. Ubuntu is cost-efficient and easy to install and manage on […]

06 May 2025 3:59am GMT

Open source system cleaning app BleachBit has put out its first major update in more than a year, adding improved cleaning capabilities, security fixes, and stability buffs. For the benefit of those with dusty memories, BleachBit is a free, open source system cleaner for Windows and Linux, written in Python and GTK 3. Similar to other apps of its type, BleachBit helps free up disk space by cleaning out caches, cookies, and other transient cruft. It can also delete files securely, wipe unallocated disk space, and squeeze Firefox and Chrome's SQLite databases to improve performance. BleachBit 5.0, released this week, expands its […]

You're reading System Cleaner BleachBit Gets First 'Major Update' Since 2023, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

05 May 2025 10:59pm GMT

Welcome to the Ubuntu Weekly Newsletter, Issue 890 for the week of April 27 - May 3, 2025. The full version of this issue is available here.

In this issue we cover:

• Ubuntu Stats
• Hot in Support
• LXD: Weekly News #393
• Other Meeting Reports
• Upcoming Meetings and Events
• UbuCon Korea 2025 참가등록 안내 [Registration Guide]
• LoCo Events
• Patch Pilot Hand-off 25.10
• Ubuntu Server Gazette - Issue 3 - Document with a little help from my friends
• Other Community News
• Canonical News
• In the Blogosphere
• Featured Audio and Video
• Updates and Security for Ubuntu 20.04, 22.04, 24.04, 24.10, and 25.04
• And much more!

The Ubuntu Weekly Newsletter is brought to you by:

• Krytarik Raido
• Bashing-om
• Chris Guiver
• Wild Man
• Din Mušić - LXD
• And many others

If you have a story idea for the Weekly Newsletter, join the Ubuntu News Team mailing list and submit it. Ideas can also be added to the wiki!

.

05 May 2025 10:14pm GMT

Google's search deal with Mozilla is such a sizeable portion of its overall income that without it, Firefox would struggle to compete - or even survive, say Mozilla. It's no secret that Google has paid Mozilla handsomely for its search engine to be set default in the Firefox web browser for decades. Mozilla's financial report for 2023 revealed that the amount of money accrued from its "search deals" that year made up roughly three quarters of its entire income (specific amounts and from whom is confidential; it's lumped together). While that figure is a bit less than it used to be, […]

You're reading Why Google Search Deal is Critical for Firefox's Future, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

05 May 2025 2:54pm GMT

Singapore | May 27, 2025 | Full-day event How do you build robust, performant edge AI infrastructure? This is the question organizations are asking themselves when looking to capitalize on the opportunity of edge AI. Ubuntu IoT Day is your opportunity to find out - and it's coming to Singapore! Join us on May 27 […]

05 May 2025 11:42am GMT

About 90% of my Debian contributions this month were sponsored by Freexian.

You can also support my work directly via Liberapay.

Request for OpenSSH debugging help

Following the OpenSSH work described below, I have an open report about the sshd server sometimes crashing when clients try to connect to it. I can't reproduce this myself, and arm's-length debugging is very difficult, but three different users have reported it. For the time being I can't pass it upstream, as it's entirely possible it's due to a Debian patch.

Is there anyone reading this who can reproduce this bug and is capable of doing some independent debugging work, most likely involving bisecting changes to OpenSSH? I'd suggest first seeing whether a build of the unmodified upstream 10.0p2 release exhibits the same bug. If it does, then bisect between 9.9p2 and 10.0p2; if not, then bisect the list of Debian patches. This would be extremely helpful, since at the moment it's a bit like trying to look for a needle in a haystack from the next field over by sending instructions to somebody with a magnifying glass.

OpenSSH

I upgraded the Debian packaging to OpenSSH 10.0p1 (now designated 10.0p2 by upstream due to a mistake in the release process, but they're the same thing), fixing CVE-2025-32728. This also involved a diffoscope bug report due to the version number change.

I enabled the new --with-linux-memlock-onfault configure option to protect sshd against being swapped out, but this turned out to cause test failures on riscv64, so I disabled it again there. Debugging this took some time since I needed to do it under emulation, and in the process of setting up a testbed I added riscv64 support to vmdb2.

In coordination with the wtmpdb maintainer, I enabled the new Y2038-safe native wtmpdb support in OpenSSH, so wtmpdb last now reports the correct tty.

I fixed a couple of packaging bugs:

• Please stop writing /var/log/btmp
• Restore sshd_config(5) documentation about rdomain

I reviewed and merged several packaging contributions from others:

• ssh-agent: Improve systemd user service socket activation (Daniel Kahn Gillmor)
• Switch from adduser to sysusers.d (Luca Boccassi)
• Add sshd-keygen service (Luca Boccassi)

dput-ng

Since we added dput-ng integration to Debusine recently, I wanted to make sure that it was in good condition in trixie, so I fixed dput-ng: will FTBFS during trixie support period. Previously a similar bug had been fixed by just using different Ubuntu release names in tests; this time I made the tests independent of the current supported release data returned by distro_info, so this shouldn't come up again.

We also ran into dput-ng: -override doesn't override profile parameters, which needed somewhat more extensive changes since it turned out that that option had never worked. I fixed this after some discussion with Paul Tagliamonte to make sure I understood the background properly.

man-db

I released man-db 2.13.1. This just included various small fixes and a number of translation updates, but I wanted to get it into trixie in order to include a contribution to increase the MAX_NAME constant, since that was now causing problems for some pathological cases of manual pages in the wild that documented a very large number of terms.

debmirror

I fixed one security bug: debmirror prints credentials with -progress.

Python team

I upgraded these packages to new upstream versions:

• celery
• django-modeltranslation (maintained by Freexian)
• django-phonenumber-field
• djangorestframework
• kombu
• orderly-set
• pox
• pydantic-extra-types
• python-cmarkgfm (fixing CVE-2022-39209, CVE-2023-22483, CVE-2023-22484, CVE-2023-22485, CVE-2023-22486, CVE-2023-24824, CVE-2023-26485, and CVE-2023-37463)
• python-django-crispy-forms
• python-django-extensions (fixing incompatibilities with Python 3.12: #1040091, #1040119)
• python-django-pgtrigger
• python-django-test-migrations
• python-holidays
• python-legacy-cgi
• python-pydash
• python-redis (4.3.4 to 5.2.1; needed some autopkgtest adjustments)
• python-tblib
• python-typing-extensions
• trove-classifiers
• xonsh

In bookworm-backports, I updated these packages:

• python-django to 3:4.2.20-1 (issuing BSA-123)
• python-django-pgtrigger to 4.13.3

I dropped a stale build-dependency from python-aiohttp-security that kept it out of testing (though unfortunately too late for the trixie freeze).

I fixed or helped to fix various other build/test failures:

• billiard (contributed upstream)
• bleak-retry-connector
• cairosvg
• errbot (contributed upstream)
• haversine
• json-tricks
• jsonpickle (contributed upstream)
• lazygal
• mypy
• pydantic
• pydantic-core
• pydantic-settings
• pympress (contributed upstream)
• pysequoia
• pysodium (contributed upstream)
• python-decorator
• python-djvulibre (contributed upstream)
• python-momepy (contributed upstream)
• python-msgspec
• python-tz
• storm
• supysonic
• uvloop (contributed upstream)

I packaged python-typing-inspection, needed for a new upstream version of pydantic.

I documented the architecture field in debian/tests/autopkgtest-pkg-pybuild.conf files.

I fixed other odds and ends of bugs:

• python-pydash: please make the build reproducible
• thunarx-python: fails to allow plugins to run / thunarx-python: fails to discover SONAME of libpython, tries to load /usr/lib/MULTIARCH/lib.so.1.0
• ttconv: package installs superfluous files under /usr/lib/python3/dist-packages

Science team

I fixed various build/test failures:

• python-vispy (also fixing unhandled failures to build documentation can occur while I was there)
• skimage

04 May 2025 3:38pm GMT

Linux system monitoring app Mission Center has put out its first update in 6 months - and it's a big one! Mission Center 1.0 adds new hardware tracking, UI tweaks, and refactors its backend to provide palapble performance improvements, boost the app's responsiveness and minimise 'time deviations between refresh cycles'. The latter may sound a tad dry on the 'excitement' scale but, arguably, it's a big thing: a real-time monitoring app is used for, well, real-time monitoring and those tweaks ensure hardware and system process info shown is more precise. For a closer lookout the "visible" changes in this release, […]

You're reading Mission Center 1.0: New Features, Better Performance, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

04 May 2025 2:45pm GMT

Before container technologies like Docker came into play, applications were typically run directly on the host operating system-either on bare metal hardware or inside virtual machines (VMs). While this method works, it often leads to frustrating issues, especially when trying to reproduce setups across different environments.

This becomes even more relevant in the amateur radio world, where we often experiment with digital tools, servers, logging software, APRS gateways, SDR applications, and more. Having a consistent and lightweight deployment method is key when tinkering with limited hardware like Raspberry Pi, small form factor PCs, or cloud VPS systems.

---

The Problem with Traditional Software Deployment

Let's say you've set up an APRS iGate, or maybe you're experimenting with WSJT-X for FT8, and everything runs flawlessly on your laptop. But the moment you try deploying the same setup on a Raspberry Pi or a remote server-suddenly things break.

Why?

Common culprits include:

• Different versions of the operating system
• Mismatched library versions
• Varying configurations
• Conflicting dependencies

These issues can be particularly painful in amateur radio projects, where specific software dependencies are critical, and stability matters for long-term operation.

You could solve this by running each setup inside a virtual machine, but VMs are often overkill-especially for ham radio gear with limited resources.

---

Enter Docker: The Ham's Best Friend for Lightweight Deployment

Docker is an open-source platform that allows you to package applications along with everything they need-libraries, configurations, runtimes-into one neat, portable unit called a container.

Think of it like packaging up your entire ham radio setup (SDR software, packet tools, logging apps, etc.) into a container, then being able to deploy that same exact setup on:

• A Raspberry Pi
• A cloud server
• A homelab NUC
• Another ham's machine

Why It's Great for Hams:

• Lightweight - great for Raspberry Pi or low-power servers
• Fast startup - ideal for services that need to restart quickly
• Reproducible environments - makes sharing setups with fellow hams easier
• Isolation - keeps different radio tools from interfering with each other

Many amateur radio tools like Direwolf, Xastir, Pat (Winlink), and even JS8Call can be containerized, making experimentation safer and more efficient.

---

Virtual Machines: Still Relevant in the Shack

Virtual Machines (VMs) have been around much longer and still play a crucial role. Each VM acts like a complete computer, with its own OS and kernel, running on a hypervisor like:

• VirtualBox
• VMware
• KVM
• Hyper-V

With VMs, you can spin up an entire Windows or Linux machine, perfect for:

• Running legacy ham radio software (e.g., old Windows-only apps)
• Simulating different operating systems for testing
• Isolating potentially unstable setups from your main system

However, VMs require more horsepower. They're heavy, boot slowly, and take up more disk space-often not ideal for small ham radio PCs or low-powered nodes deployed in the field.

---

Quick Comparison: Docker vs Virtual Machines for Hams

Feature	Docker	Virtual Machine
OS	Shares host kernel	Full OS per VM
Boot Time	Seconds	Minutes
Resource Use	Low	High
Size	Lightweight	Heavy (GBs)
Ideal For	Modern ham tools, APRS bots, SDR apps	Legacy systems, OS testing
Portability	High	Moderate

---

Ham Radio Use Cases for Docker

Here's how Docker fits into amateur radio workflows:

• Run an APRS iGate with Direwolf and YAAC in isolated containers.
• Deploy SDR receivers like rtl_433, OpenWebRX, or CubicSDR as containerized services.
• Set up a Winlink gateway using Pat + ax25 tools, all in one container.
• Automate and scale your APRS bot, or APRS gateway using Docker + cron + scripts.

Docker makes it easier to test and share these setups with other hams-just export your Docker Compose file or image.

---

When to Use Docker, When to Use a VM

Use Docker if:

• You're building or experimenting with modern ham radio apps
• You want to deploy quickly and repeatably
• You're using Raspberry Pi, VPS, or low-power hardware
• You're setting up CI/CD pipelines for your scripts or bots

Use VMs if:

• You need to run legacy apps (e.g., old Windows logging software)
• You want to simulate full system environments
• You're working on something that could crash your main system

---

Final Thoughts

Both Docker and VMs are powerful tools that have a place in the modern ham shack. Docker offers speed, portability, and resource-efficiency-making it ideal for deploying SDR setups, APRS bots, or automation scripts. VMs, on the other hand, still shine when you need full system emulation or deeper isolation.

At the end of the day, being a ham means being an experimenter. And tools like Docker just give us more ways to explore, automate, and share our radio projects with the world.

The post Docker vs Virtual Machines: What Every Ham Should Know appeared first on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

03 May 2025 3:16am GMT

If you use the Papirus icon theme on Ubuntu, you'll be pleased to hear a new version is available to download. Frequent updates are a major reason why the Papirus icon set is so popular with Linux users. After all, it's annoying to switch to a stylish icon set that doesn't have icons for most of your apps, ruining the vibe. Not so with Papirus. It's perpetually expanding its coverage through regular updates. Papirus's second update this year adds 69 new icons-nice-and 18 updated ones. It also includes packaging and DE changes, and deprecates its ePapirus variants since elementaryOS 8 […]

You're reading Papirus Icon Set Update Adds New Icons, Plasma 6 Support, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

02 May 2025 2:30pm GMT

Canonical has announced the first official Ubuntu desktop image for the Qualcomm DragonWing platform. A beta image of Ubuntu 24.04 desktop compatible with Qualcomm Dragonwing QCS6490 and QCS5430 processors, and specifically tailored for the Qualcomm RB3 (Gen 2) Vision Kit and RB3 (Gen 2 Lite) Vision Kit is available for testing. Ubuntu 24.04 server images were previously available for the same model vision kits, so it's the addition of desktop builds that is an interesting development. Canonical say marrying a full Ubuntu desktop experience married with "powerful AI acceleration with high-performance graphics" in the Dragonwing devices provides "a powerful development environment […]

You're reading Canonical Brings Ubuntu 24.04 to Qualcomm Dragonwing Vision Kit, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

02 May 2025 2:14am GMT

Incus is a manager for virtual machines and system containers.

A virtual machine (VM) is an instance of an operating system that runs on a computer, along with the main operating system. A virtual machine uses hardware virtualization features for the separation from the main operating system. With virtual machines, the full operating system boots up in them. While in most cases you would run Linux on a VM without a desktop environment, you can also run Linux with a desktop environment (like in VirtualBox and VMWare).

In How to run a Windows virtual machine on Incus on Linux we saw how to run a run a Windows VM on Incus. In this post we see how to run a Linux Desktop virtual machine on Incus.

Table of Contents

• Updates
• Prerequisites
• Cheat sheet
• Availability of images
• Booting a desktop Linux VM on Incus
  • Booting the Ubuntu desktop image on Incus
  • Booting the ArchLinux desktop image on Incus
  • Booting the OpenSUSE desktop image on Incus
• Troubleshooting
  • I closed the desktop window but the VM is running. How do I get it back up?
  • Error: This console is already connected. Force is required to take it over.
  • Error: Instance is not running
  • I get no audio from the desktop VM! How do I get sound in the desktop VM?
  • How do I shutdown the desktop VM?
  • Error: Failed instance creation: The image used by this instance is incompatible with secureboot. Please set security.secureboot=false on the instance
  • Error: Failed instance creation: Failed creating instance record: Add instance info to the database: Failed to create "instances" entry: UNIQUE constraint failed: instances.project_id, instances.name

Updates

No updates yet.

Prerequisites

1. You should have a system that runs Incus.
2. A system with support for hardware virtualization so that it can run virtual machines.
3. A virtual machine image of your preferred Linux desktop distribution.

Cheat sheet

Availability of images

Currently, Incus provides you with the following VM images of Linux desktop distributions. The architecture is x86_64.

Run the following command to list all available Linux desktop images. incus image is the section of Incus that deals with the management of images. The list command lists the available images of a remote/repository, the default being images: (run incus remote list for the full list of remotes). After the colon (:), you type filter keywords, and in this case we typed desktop to show images that have the word desktop in them (to show only Desktop images). We are interested in a few columns only, therefore -c ldt only shows the columns for the Alias, the Description and the Type.

$ incus image list images:desktop -c ldt
+------------------------------------------+---------------------------+-----------------+
|                  ALIAS                   |      DESCRIPTION          |      TYPE       |
+------------------------------------------+---------------------------+-----------------+
| archlinux/desktop-gnome (3 more)         | Archlinux current amd64   | VIRTUAL-MACHINE |
+------------------------------------------+---------------------------+-----------------+
| opensuse/15.5/desktop-kde (1 more)       | Opensuse 15.5 amd64       | VIRTUAL-MACHINE |
+------------------------------------------+---------------------------+-----------------+
| opensuse/15.6/desktop-kde (1 more)       | Opensuse 15.6 amd64       | VIRTUAL-MACHINE |
+------------------------------------------+---------------------------+-----------------+
| opensuse/tumbleweed/desktop-kde (1 more) | Opensuse tumbleweed amd64 | VIRTUAL-MACHINE |
+------------------------------------------+---------------------------+-----------------+
| ubuntu/24.10/desktop (3 more)            | Ubuntu oracular amd64     | VIRTUAL-MACHINE |
+------------------------------------------+---------------------------+-----------------+
| ubuntu/focal/desktop (3 more)            | Ubuntu focal amd64        | VIRTUAL-MACHINE |
+------------------------------------------+---------------------------+-----------------+
| ubuntu/jammy/desktop (3 more)            | Ubuntu jammy amd64        | VIRTUAL-MACHINE |
+------------------------------------------+---------------------------+-----------------+
| ubuntu/noble/desktop (3 more)            | Ubuntu noble amd64        | VIRTUAL-MACHINE |
+------------------------------------------+---------------------------+-----------------+
| ubuntu/plucky/desktop (1 more)           | Ubuntu plucky amd64       | VIRTUAL-MACHINE |
+------------------------------------------+---------------------------+-----------------+
$ 

These images have been generated with the utility distrobuilder, https://github.com/lxc/distrobuilder The purpose of the utility is to prepare the images so that when we launch them, we get immediately the desktop environment and do not perform any manual configuration. The configuration files for distrobuilder to create these images can be found at https://github.com/lxc/lxc-ci/tree/main/images For example, the archlinux.yaml configuration file has a section to create the desktop image, along with the container and other virtual machine images.

The full list of Incus images are also available on the Web, through the website https://images.linuxcontainers.org/ It is possible to generate more such desktop images by following the steps of the existing configuration files. Perhaps a Kali Linux desktop image would be very useful. In the https://images.linuxcontainers.org/ website you can also view the build logs that were generated while building the images, and figure out what parameters are needed for distrobuilder to build them (along with the actual configuration file). For example, here are the logs for the ArchLinux desktop image, https://images.linuxcontainers.org/images/archlinux/current/amd64/desktop-gnome/

Up to this point we got a list of the available virtual machine images that are provided by Incus. We are ready to boot them.

Booting a desktop Linux VM on Incus

When launching a VM, Incus provides by default 1GiB RAM and 10GiB of disk space. The disk space is generally OK, but the RAM is too little for a desktop image (it's OK for non-desktop images). For example, for an Ubuntu desktop image, the instance requires about 1.2GB of memory to start up and obviously more to run other programs. Therefore, if we do not specify more RAM, then the VM would struggle to make do of the mere 1GiB of RAM.

Booting the Ubuntu desktop image on Incus

Here is the command to launch a desktop image. We use incus launch to launch the image. It's a VM, hence --vm. We are using the image from the images: remote, the one called ubuntu/plucky/desktop (it's the last from the list of the previous section). We configure a new limit for the memory usage, -c limits.memory=3GiB, so that the instance will be able to run successfully. Finally, the console is not textual but graphical. We specify that with --console=vga which means that Incus will launch the remote desktop utility for us.

$ incus launch --vm images:ubuntu/plucky/desktop mydesktop -c limits.memory=3GiB --console=vga
Launching mydesktop

Here is a screenshot of the new window with the running desktop virtual machine.

Screenshot of images:ubuntu/plucky/desktop

Now we closed the wizard.

Screenshot of images:ubuntu/plucky/desktop after we close the wizard.

Booting the ArchLinux desktop image on Incus

I cannot get this image to show the desktop. If someone can make this work, please post in a comment.

$ incus launch --vm images:archlinux/desktop-gnome mydesktop -c limits.memory=3GiB --console=vga -c security.secureboot=false
Launching mydesktop

Booting the OpenSUSE desktop image on Incus

$ incus launch --vm images:opensuse/15.5/desktop-kde mydesktop -c limits.memory=3GiB --console=vga
Launching mydesktop

Troubleshooting

I closed the desktop window but the VM is running. How do I get it back up?

If you closed the Remote Viewer window, you can get Incus to start it again with the following command. By doing so, you are actually reconnecting back to the VM and continue working from where you left off.

We are using the incus console action to connect to the running mydesktop instance and request access through the Remote Viewer (rather than a text console).

$ incus console mydesktop --type=vga

Error: This console is already connected. Force is required to take it over.

You are already connected to the desktop VM with the Remote Viewer and you are trying to connect again. Either go to the existing Remote Viewer window, or add the parameter --force to close the existing Remote Viewer window and open a new one.

Error: Instance is not running

You are trying to connect to a desktop VM with the Remote Viewer but the instance (which already exists) is not running. Use the action incus start to start the virtual machine, along with the --type=vga parameter to get Incus to launch the Remote Viewer for you.

$ incus start mydesktop --console=vga

I get no audio from the desktop VM! How do I get sound in the desktop VM?

This requires extra steps which I do not show yet. There are three options. The first is to use the QEMU device emulation to emulate a sound device in the VM. The second is to somehow push an audio device into the VM so that this audio device is used exclusively in the VM (have not tried this but I think it's possible). The third and perhaps best option is to use network audio with PulseAudio/Pipewire. You enable network audio on your desktop and then configure the VM instance to connect to that network audio server. I have tried that and it worked well for me. The downside is that the Firefox snap package in the VM could not figure out that there is network audio there and I could not get audio in that application.

How do I shutdown the desktop VM?

Use the desktop UI to perform the shutdown. The VM will shut down cleanly.

Error: Failed instance creation: The image used by this instance is incompatible with secureboot. Please set security.secureboot=false on the instance

You tried to launch a virtual machine with SecureBoot enabled but the image does not support SecureBoot. You need to disable SecureBoot when you launch this image. The instance has been created but is unable to run unless you disable SecureBoot. You can either disable SecureBoot through an Incus configuration for this image, or just delete the instance, and try again with the parameter -c security.secureboot=false.

Here is how to disable SecureBoot, then try to incus start that instance.

$ incus config set mydesktop security.secureboot=true

Here is how you would enable that flag when you launch such a VM.

incus launch --vm images:archlinux/desktop-gnome mydesktop -c limits.memory=3GiB --console=vga -c security.secureboot=false

Note that official Ubuntu images can work with SecureBoot enabled, most others don't. It has to do with the Linux kernel being digitally signed by some certification authority.

Error: Failed instance creation: Failed creating instance record: Add instance info to the database: Failed to create "instances" entry: UNIQUE constraint failed: instances.project_id, instances.name

This error message is a bit cryptic. It just means that you are trying to create or launch an instance while the instance already exists. Read as Error: The instance name already exists.

01 May 2025 10:51pm GMT

Development today opened on Ubuntu 25.10 "Questing Quokka", the next short-term release of Ubuntu, due for release in October. Canonical engineer Utkarsh Gupta fired the figurative starting pistol for developers in a post to the Ubuntu mailing list, announcing the opening, and the enabling of auto-sync. "As usual, we expect a large influx of builds and autopkgtests in this initial period, which will cause delays. Please help fixing any breakage that occurs," Gupta adds. It's only been a couple of weeks since the Ubuntu 25.04 release, but the dedicated devs who spent 6 months diligently shaping that release don't get much time […]

You're reading We're Off - Ubuntu 25.10 Opens for Development, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

01 May 2025 4:19pm GMT

O Miguel abriu um terminal e escreveu sudo do-release-upgrade às 11h30 do dia 29 de Abril. E o país ficou às escuras. Coincidência? Revelamos todos os detalhes de uma investigação bombástica que revelará os segredos chocantes de uma sociedade secreta de GNU-Linux que governa o mundo e que envolve pessoas tão famosas como o Diogo, a Soficious, HatRat e o PewDiePie - uma sociedade que opera nas trevas (literalmente) e que é tão poderosa que obrigou o governo Federal Alemão a usar formatos abertos! Para além disso, ainda falámos sobre as últimas novidades compartimentadas de Firefox 138 e os próximos eventos da agenda: Raspberry Pi Jam, Open Lab no LCD Porto, Encontros Ubuntu, Encontros nacionais do Community Day de Home Assistant e datas para a Wikicon Portugal.

Já sabem: oiçam, subscrevam e partilhem!

• Apagão de 2025: https://pt.wikipedia.org/wiki/Apag%C3%A3o_europeu_de_2025
• Lançamento de Plucky Puffin: https://canonical.com/blog/canonical-releases-ubuntu-25-04-plucky-puffin
• O que é novo no 25.04: https://9to5linux.com/ubuntu-25-04-plucky-puffin-is-now-available-for-download-this-is-whats-new
• Novas Funcionalidades de 25.04: https://www.omgubuntu.co.uk/2025/03/ubuntu-25-04-new-features
• Perfis Compartimentados no Firefox: https://support.mozilla.org/pt-PT/kb/profile-management
• https://9to5linux.com/mozilla-firefox-138-is-now-available-for-download-heres-whats-new
• https://www.omgubuntu.co.uk/2025/04/firefox-138-new-features
• https://www.mozilla.org/en-US/firefox/138.0/releasenotes/
• Tias Que Malham em Jogos: https://www.twitch.tv/tias_malham
• Podcast Voz dos Direitos Digitais: https://direitosdigitais.libsyn.com/
• Raspberry Pi Jam: https://mill.pt/events/raspberry-jam-lisboa-3/
• Videovigilância com Raspberry Pi Zero: https://youtu.be/ll5d342QaCY
• LCD Porto - Laboratório de Criação Digital: https://lcdporto.org
• Home Assistant Community Day: Aveiro https://lu.ma/p9eo4v3t Porto https://lu.ma/uozbfr6n Lisboa https://lu.ma/bxbs0kdp Mundo: https://www.home-assistant.io/blog/2025/04/24/community-day/
• JNation: https://jnation.pt/
• Wikicon Portugal: https://wikimedia.pt/eventos/wikicon-portugal-2025/
• Libertação de Schleswig-Holstein: https://arstechnica.com/information-technology/2024/04/german-state-gov-ditching-windows-for-linux-30k-workers-migrating/
• https://blog.documentfoundation.org/blog/2025/03/13/updates-on-schleswig-holstein-moving-to-libreoffice/
• Alemanha adopta Formatos Abertos: https://blog.documentfoundation.org/blog/2024/04/04/german-state-moving-30000-pcs-to-libreoffice/
• https://blog.documentfoundation.org/blog/2025/04/29/germany-committing-to-odf-and-open-document-standards/
• https://www.it-planungsrat.de/beschluss/beschluss-2025-06
• Soficious: https://www.twitch.tv/soficious
• https://linktr.ee/soficious
• HatRat: https://www.youtube.com/@hatrat
• PewDiePie adopta Linux: https://www.youtube.com/watch?v=pVI_smLgTY0
• 8-10 Maio: SushiTech Tokyo - Sustainable High City Tech https://sushitech-startup.metro.tokyo.lg.jp/en/
• Ubuntu Touch Q&A 163: https://www.youtube.com/watch?v=4ksTW_ypmwM
• LoCo PT: https://loco.ubuntu.com/teams/ubuntu-pt/
• Mastodon: https://masto.pt/@pup
• Youtube: https://youtube.com/PodcastUbuntuPortugal

Atribuição e licenças

Este episódio foi produzido por Diogo Constantino, Miguel e Tiago Carrondo e editado pelo Senhor Podcast. O website é produzido por Tiago Carrondo e o código aberto está licenciado nos termos da Licença MIT. (https://creativecommons.org/licenses/by/4.0/). A música do genérico é: "Won't see it comin' (Feat Aequality & N'sorte d'autruche)", por Alpha Hydrae e está licenciada nos termos da CC0 1.0 Universal License. Este episódio e a imagem utilizada estão licenciados nos termos da licença: Attribution-NonCommercial-NoDerivatives 4.0 International (CC BY-NC-ND 4.0), cujo texto integral pode ser lido aqui. Estamos abertos a licenciar para permitir outros tipos de utilização, contactem-nos para validação e autorização. A arte de episódio foi criada por encomenda pela Shizamura - artista, ilustradora e autora de BD. Podem ficar a conhecer melhor a Shizamura na Ciberlândia e no seu sítio web.

01 May 2025 12:00am GMT

April saw a solid set of software updates land for an slew of popular Linux apps. In this post, I run through a number of recent releases that didn't get the "full article" treatment on this blog. Sometimes it's a challenge to cover everything I want to (especially in an Ubuntu release month, as April was), and some updates are rather minor and hard to say too much about. Also, covering updates relies on me knowing they're out in a timely fashion. I track as much as I can, as best as I can. But it's easy for things to […]

You're reading Linux App Release Roundup (April 2025), a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

30 Apr 2025 8:10pm GMT

This public beta enables the full Ubuntu Desktop experience on the Qualcomm Dragonwing™ QCS6490 and QCS5430 processors and complements existing Ubuntu Server support with significant enhancements. Together, these updates provide a powerful development environment for building next-generation AI-driven edge applications. April 30, 2025 - Canonical, the publisher of Ubuntu and provider of open source security, […]

30 Apr 2025 7:58pm GMT

Luna brings moon phases to your Ubuntu desktop with a simple GNOME Shell extension. Track current phase, illumination percentage, and upcoming changes right from your panel.

You're reading Track Moon Phases From Your Ubuntu Desktop With Luna, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

30 Apr 2025 2:42pm GMT

The EU Cyber Resilience Act is here, and in 2027 it will require manufacturers to meet a long list of security and support standards. Here's our advice to all developers.

30 Apr 2025 1:16pm GMT

Launchpad and the Open Documentation Academy Live in Málaga

Launchpad is a web-based platform to support collaborative software development for open source projects. It offers a comprehensive suite of tools including bug tracking, code hosting , translation management, and package building

Launchpad is tightly integrated with the Ubuntu ecosystem, serving as a central hub for Ubuntu development and community contributions. Its features are designed to streamline the process of managing, developing, and distributing software in a collaborative environment.

Launchpad aims to foster strong community engagement by providing features that support collaboration, community management, and user participation, positioning itself as a central hub for open source communities.

Canonical's Open Documentation Academy is a collaboration between Canonical's documentation team and open source newcomers, experts, and those in-between, to help us all improve documentation, become better writers, and better open source contributors.

A key aim of the project is to set the standard for inclusive and welcoming collaboration while providing real value for both the contributors and the projects involved in the programme.

Join us at OpenSouthCode in Málaga

Launchpad and the Open Documentation Academy will join forces at OpenSouthCode 2025 in the wonderful city of Málaga, Spain, on June 20 - 21 2025.

The Open Documentation Academy will have a hands-on documentation workshop at the conference, where the participants will learn how to do meaningful open source contributions with the help of the Diátaxis documentation framework.

Launchpad's Jürgen Gmach will be on-site and help you to land your first open source contribution.

Please register at https://www.opensouthcode.org/conferences/opensouthcode2025 - the conference and the workshop are free of charge. If you have any questions, please do not hesitate to reach out to us at feedback@launchpad.net.

Tenemos muchas ganas de conoceros. ¡Nos vemos en Málaga!

29 Apr 2025 3:00pm GMT

In this article, I'll explore an original and robust method for using third-party IdPs that allows you to maintain a zero trust security posture, thanks to Extra Factor Authentication. Find it on our Charm hub!

29 Apr 2025 2:33pm GMT

At long last, Mozilla Firefox has GUI profile management features - obvious, easy to use and don't require poking around the browser's backend and creating custom shortcuts. The feature, which begins rolling out in today's Firefox 138 update, is the latest "big ticket" feature the browser has belatedly sought to add, following recent long-requested supported for vertical tabs and tab grouping capabilities. Last month's Firefox 137 release added the aforementioned tab grouping features, give its address bar a chip-laden overhaul, and flipped the switch on HEVC video playback on Linux. Firefox 138 has a number of notable changes to match those […]

You're reading Firefox 138 Released with Long-Awaited Profile Manager, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

29 Apr 2025 11:04am GMT

Welcome to the Ubuntu Weekly Newsletter, Issue 889 for the week of April 20 - 26, 2025. The full version of this issue is available here.

In this issue we cover:

• Status of Oracular to Plucky upgrades
• [update] Migration to rust-coreutils in 25.10
• Welcome New Members and Developers
• Ubuntu Stats
• Hot in Support
• LXD: Weekly news #392
• Other Meeting Reports
• Upcoming Meetings and Events
• Ubuntu Nepal's Meetup For UbuCon Asia 2025
• Korean LoCo Tea Party (May 17)
• UbuCon Africa @ DjangoCon Africa 2025
• LoCo Events
• Agenda Topics for Communications Council - April 30th 2025
• Behind the Curtain: Releasing Ubuntu 25.04 "Plucky Puffin"
• Visualizing and Exploring Ubuntu Excuses
• Celebrating community contributions
• Canonical News
• In the Blogosphere
• Other Articles of Interest
• Featured Audio and Video
• Updates and Security for Ubuntu 20.04, 22.04, 24.04, 24.10, and 25.04
• And much more!

The Ubuntu Weekly Newsletter is brought to you by:

• Krytarik Raido
• Bashing-om
• Chris Guiver
• Wild Man
• Din Mušić - LXD
• Cristovao Cordeiro (cjdc) - Rocks
• And many others

If you have a story idea for the Weekly Newsletter, join the Ubuntu News Team mailing list and submit it. Ideas can also be added to the wiki!

.

28 Apr 2025 10:14pm GMT

If you're looking for an easy way to "scrobble" music on Linux, no matter which music player you use, check out a new app called Turntable - and even if you don't scrobble you should! Before I go any further I should bring those unfamiliar with what a "scrobble" is, up to speed. "Scrobbling" is-no, not one of those old fashioned British words I'm fond of using-the term given to logging the music you listen to, as you listen to it, on services like Last.fm and Libre.fm. When you play a track in a media player connected to a compatible […]

You're reading Turntable is a Universal Scrobbler App for Linux, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

28 Apr 2025 7:47pm GMT

I was just released from the hospital after a 3 day stay for my ( hopefully ) last surgery. There was concern with massive blood loss and low heart rate. I have stabilized and have come home. Unfortunately, they had to prescribe many medications this round and they are extremely expensive and used up all my funds. I need gas money to get to my post-op doctors appointments, and food would be cool. I would appreciate any help, even just a dollar!

• GoFundMe
• Patreon
• Github
• Donorbox

I am already back to work, and continued work on the crashy KDE snaps in a non KDE env. ( Also affects anyone using kde-neon extensions such as FreeCAD) I hope to have a fix in the next day or so.

Fixed kate bug https://bugs.kde.org/show_bug.cgi?id=503285

Thanks for stopping by.

28 Apr 2025 1:04pm GMT

Of note, Ubuntu 24.04 developer images are now available for the new OrangePi RV2 RISC-V single-board computer (SBC). The news underscores Canonical's on-going interest in the fledgling, open-source architecture. Last year, DeepComputing released Ubuntu-powered RISC-V tablet and laptop, and Ubuntu Server 25.04 was released last month with support for a myriad of RISC-V SBCs. "At Canonical, we believe that it's important to do our part to help RISC-V succeed and gain acceptance as an open standard. Ubuntu's availability on the OrangePi RV2 is a testament to the continued collaboration between [us] and the broader RISC-V community," the company says. Adding […]

You're reading Ubuntu 24.04 Now Available for OrangePi's New RISC-V SBC, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

25 Apr 2025 3:58pm GMT

The Launchpad project is almost 21 years old! Many people have contributed to the project over this lifetime, and we are thankful for all of them. We understand the value of a strong community and we are taking steps to reinvigorate Launchpad's once-thriving community.

There are two common suggestions for getting started in open source: fixing bugs and contributing to documentation. Early in 2024, Canonical launched the Canonical Open Documentation Academy; an initiative that aims to break down barriers to open source contribution, and work with the community to raise the bar for documentation practice. The Open Documentation Academy has been helping people get involved in open source and has also been helping projects achieve ever higher standards in documentation. Launchpad is one such project.

Today, we recognize and celebrate our community contributors. We hope they enjoyed contributing to Launchpad as much as we enjoyed working with them!

- gerryRcom

- Jared Nielsen

- Adriaan Van Niekerk

- Nathan Barbarick

Thank you for helping to make Launchpad great!

commit f980cfb3c78b72b464a054116eea9658ef906782
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Mon Oct 14 15:39:27 2024 -0400

    Add debugging doc; fix broken links (#108)
    
    * Add debugging doc; fix broken links
    
    * fix broken links in debugging.rst
    
    * fix spelling errors
    
    * fix spelling errors
    
    * fix spelling errors
    
    * fix debugging link
    
    * fix lots of formatting on recovered debugging.rst page
    
    * add debugging.rst page into Launchpad development tips
    
    ---------
    
    Co-authored-by: Alvaro Crespo <alvarocrespo.se@gmail.com>

commit c690ef5c7ed2d63d989c1f91b2883ed947904228
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Wed Oct 9 14:32:59 2024 -0400

    Add database table page; fix broken link (#107)
    
    * Add database table page; fix broken link
    
    * add spell check errors to custom_wordlist
    
    * add rename-database-table to how-to/index.rst
    
    * fix reference link to rename-database-table page in live-patching.rst explanation doc
    
    * format rename-database-table to show as sql code
    
    ---------
    Co-authored-by: Jared Nielsen <nielsen.jared@gmail.com>
    Co-authored-by: Alvaro Crespo <alvaro.crespo@canonical.com>

commit 5b319ab2899a326b7e96a5c001965e486a445448
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Wed Oct 9 12:20:24 2024 -0400

    Add missing codehosting doc; fix broken link (#106)
    
    * Add missing codehosting doc; fix broken link
    
    * add codehosting-locally to index.rst
    
    * add spell check errors to custom_wordlist
    
    * fix reference link for codehosting-locally in code.rstexplanation section
    
    ---------
    
    Co-authored-by: Jared Nielsen <nielsen.jared@gmail.com>
    Co-authored-by: Alvaro Crespo <alvaro.crespo@canonical.com>

commit 1fcb3a9588bcb62132ce0004bb98f54e28c6561c
Author: Nathan Barbarick <nathanclaybarbarick@gmail.com>
Date:   Mon Sep 30 11:08:39 2024 -0700

    Group articles of the Explanation section into proper subsections (#97)
    
    * Remove How to go about writing a web application, per jugmac00.
    
    * Group articles in the Explanation section into subsections, add introductory text.
    
    * Add new sections for remaining ToC headings.
    
    * Add codehosting.png, fix broken link (#104)
    
    * add codehosting.png, fix broken link
    
    * delete linkcheck_ignore item
    
    * remove accessibility, upstream, and schema links (#102)
    
    * add concepts.rst, fix broken link in code.rst (#105)
    
    * add concepts.rst, fix broken link in code.rst
    
    * add spellcheck errors to custom_wordlist
    
    * add concepts to index.rst
    
    * Add descriptions in the explanation index and move new concepts page.
    
    ---------
    
    Co-authored-by: Jared Nielsen <nielsen.jared@gmail.com>

commit ce5408a8ba919d22c5f5f01ff0396e1eb982d359
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Thu Sep 12 08:11:00 2024 -0400

    add concepts.rst, fix broken link in code.rst (#105)
    
    * add concepts.rst, fix broken link in code.rst
    
    * add spellcheck errors to custom_wordlist
    
    * add concepts to index.rst

commit eb5a0b185af6122720d44791aa8c98d52daf93e5
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Fri Sep 6 04:00:51 2024 -0400

    remove accessibility, upstream, and schema links (#102)

commit 766dc568b06e49afbb831c25a6163be31ab5064a
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Thu Sep 5 03:09:19 2024 -0400

    Add codehosting.png, fix broken link (#104)
    
    * add codehosting.png, fix broken link
    
    * delete linkcheck_ignore item

commit 317437262dd6d21bbb832e9603e4f84dbd4095b6
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Fri Aug 16 15:02:25 2024 -0400

    add 'Soyuz' link (#103)

commit f238c1f4e2322d5ad31c9d86615108856c9f8dfc
Author: gerryRcom <gerryr@gerryr.com>
Date:   Wed Jul 24 06:01:27 2024 +0100

    oda spelling check on code doc (#90)
    
    * oda spelling check on code doc
    
    * oda spelling check on code doc
    
    * Update .custom_wordlist.txt
    
    ---------
    
    Co-authored-by: Jürgen Gmach <juergen.gmach@canonical.com>

commit ff237feec8ee9fd6530ccd0aa1f940939ddedee0
Author: Adriaan Van Niekerk <144734475+sfadriaan@users.noreply.github.com>
Date:   Tue Jul 23 14:44:29 2024 +0200

    Check Spelling errors (Storm migration guide) (#92)
    
    * Remove Storm Migration Guide from exclusion list
    
    * Update code inline formatting and correct spelling errors
    
    * Add accepted words

commit 8500de5b96e4949b23d6c646c65272b9c8180424
Author: Adriaan Van Niekerk <144734475+sfadriaan@users.noreply.github.com>
Date:   Tue Jul 23 11:05:04 2024 +0200

    Check Spelling (Database Performance page) (#91)
    
    * Remove database performance page from exclusion
    
    * Add accepted words
    
    * Correct spelling errors

commit 06401ea4f554bd8eff483a03c5dea2508f942bdd
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Wed Jul 17 11:13:05 2024 +0200

    Correct spelling errors

commit 9eb17247c1100dc7c23dcb2a0275064ed1dc7a19
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Wed Jul 17 11:11:13 2024 +0200

    Add accepted words

commit a539b047d012d5078b097041d9072937d2247704
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Wed Jul 17 11:10:59 2024 +0200

    Remove "Security Policy" from exclusion list

commit 7708a5fa7b6ed6c0856fa2722f917228c9127eb0
Author: Adriaan Van Niekerk <144734475+sfadriaan@users.noreply.github.com>
Date:   Wed Jul 17 08:13:34 2024 +0200

    Spell check (URL traversal + Navigation Menus) (#87)
    
    * Remove Navigation Menu page from exclusion
    
    * Add words to be excluded from spell check
    
    * Correct spelling errors
    
    * Remove "url-traversal" from exclusion list
    
    * Update list of accepted words
    
    * Update formatting and correct errors
    
    ---------
    
    Co-authored-by: Jürgen Gmach <juergen.gmach@canonical.com>

commit e952eb0aa98fe33a20517b82640d88c2c6a8fc5f
Author: gerryRcom <gerryr@gerryr.com>
Date:   Mon Jul 15 20:17:36 2024 +0100

    oda spelling check on branches doc

commit 46170ead6fe34fde518fe8848e3d321b57506875
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Mon Jul 15 11:02:57 2024 +0200

    Update formatting of URLs

commit 124245b2b4b5699596e7039f09f6d1f3211b409f
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Mon Jul 15 11:00:22 2024 +0200

    Remove Launchpad Mail page from exclusion list

commit 141aa07f62d47e7b25581c113fe222679ca9135d
Author: gerryRcom <gerryr@gerryr.com>
Date:   Wed Jul 10 20:12:47 2024 +0100

    oda spelling check on ppa doc

commit bdea1e1d11e88255eed19e335d840a278cefb134
Author: gerryRcom <gerryr@gerryr.com>
Date:   Wed Jul 10 20:08:37 2024 +0100

    oda spelling check on ppa doc

commit 7a960016415d32bae99bccac8e7ee634d7034ce7
Merge: 1c6506b 3e12837
Author: gerryRcom <gerryr@gerryr.com>
Date:   Tue Jul 9 17:47:06 2024 +0100

    Merge branch 'main' into spelling-feature-flags-doc

commit 1c6506b7e971fed802b3dfc85abc29bc0a075450
Author: gerryRcom <gerryr@gerryr.com>
Date:   Fri Jul 5 20:06:05 2024 +0100

    oda spelling check on feature-flags doc

commit 27b2aa62c48dde374d4e27fae671b061eb97a46f
Merge: acb3847 d32c826
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Fri Jul 5 16:03:01 2024 +0200

    Merge branch 'main' of https://github.com/canonical/launchpad-manual into javascript-buildsystem-page

commit 3dc90949b0bd2136347916be1b4b05e0041b2d54
Merge: 053a960 f193109
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Fri Jul 5 14:07:59 2024 +0200

    Merge branch 'main' of https://github.com/canonical/launchpad-manual into fix-spelling-issues

commit 053a96086a8e649f0b135aa6eeb942b858f7ba5b
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Fri Jul 5 13:59:34 2024 +0200

    Add word to resolve conflict in pull request

commit f19310999278be18a3d92443a7b22cf1b0e7e441
Author: gerryRcom <gerryr@gerryr.com>
Date:   Thu Jul 4 21:18:04 2024 +0100

    oda spelling check on testing doc

commit 93e5fb8d8356b70b52401c69e7884a1dea2e8b46
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Thu Jul 4 18:44:24 2024 +0200

    Remove exclusion added via rebase

commit d75ca31d26bd1731db6fad08c94c7d99bebc02c3
Merge: 54b74c2 5a2f090
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Thu Jul 4 18:09:04 2024 +0200

    Merge branch 'fix-spelling-issues' of https://github.com/sfadriaan/launchpad-manual into fix-spelling-issues

commit 54b74c252952c5de24c0e232bbbe560f9c4c416e
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Thu Jul 4 10:50:08 2024 +0200

    Correct spelling errors, verified by external documentation, converted to en-gb and corrected formatting

commit f1c66b1ce59f6af9a678f86f6b4fa637df91bcb3
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Thu Jul 4 10:48:48 2024 +0200

    Add correctly spelled words picked up by spell checker

commit 73f12ca01f9cce4414702674cd24dc3d38e49304
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Thu Jul 4 10:47:42 2024 +0200

    Remove javascript-integration-testing page from the exclusion list

commit acb384767214e3d432eafe062a2fb646f3c31938
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Thu Jul 4 16:07:25 2024 +0200

    Update mailing list URL, spelling error correction

commit da06505e8a3431d50a815d16ca4f89a5d66c7a41
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Thu Jul 4 16:06:52 2024 +0200

    Remove javascript-buildsystem from exclusion list

commit 2318addb0ea19de7813b5f6b16efc43d21584659
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Thu Jul 4 16:06:24 2024 +0200

    Add words to exclusion list

commit 5a2f090a2da9083b3c3b658592ec43595e78eb0e
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Thu Jul 4 10:50:08 2024 +0200

    Correct spelling errors, verified by external documentation, converted to en-gb and corrected formatting

commit ce333446e7c7501629d3ceab239183aed64af319
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Thu Jul 4 10:48:48 2024 +0200

    Add correctly spelled words picked up by spell checker

commit 7649b104c9439dda5f938b2e0153e4d1c45f21b4
Author: Adriaan van Niekerk <adriaan.vanniekerk@canonical.com>
Date:   Thu Jul 4 10:47:42 2024 +0200

    Remove javascript-integration-testing page from the exclusion list

commit 017d19761d96d9c04a1ea61ac0e77bcf6a7b7cab
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Wed Jul 3 11:42:33 2024 -0400

    Fix 'Loggerhead' link

commit fda0691919cd849ff4c6ee24e4dc1e3d5e6b1682
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Wed Jul 3 11:32:15 2024 -0400

    Fix 'UI/CssSprites' link

commit f26faaef61e5ef48140bd2f84630c5d624041dad
Author: gerryRcom <gerryr@gerryr.com>
Date:   Wed Jul 3 09:18:02 2024 +0100

    oda spelling check on translations doc

commit 13cb12c45e1a5826d27eaf497b7e6a2605d7ec6d
Author: gerryRcom <gerryr@gerryr.com>
Date:   Tue Jul 2 19:41:38 2024 +0100

    oda spelling check on unittesting doc

commit cdab34e61a7c1009852a642e978b9027c2aad3d2
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Tue Jul 2 12:07:06 2024 -0400

    Fix 'Running' link

commit dbe279acfef9eb736735b04ba474801d3f58a3f0
Author: Nathan Barbarick <nathanclaybarbarick@gmail.com>
Date:   Fri Jun 28 19:55:08 2024 -0700

    Restructure navigation menu using subsections in how-to.

commit 8592ed544881d50877f036073a6eec9de2e6356d
Author: gerryRcom <gerryr@gerryr.com>
Date:   Sat Jun 29 09:49:34 2024 +0100

    oda spelling check on css doc

commit 90608989d15cf2dbdf9a538a03517c03d87a3658
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Sat Jun 29 03:54:27 2024 -0400

    Fix 'JavascriptUnitTesting' link (#72)
    
    Co-authored-by: Jürgen Gmach <juergen.gmach@canonical.com>

commit 61ab3a36a51cb6ee40d6132cc1028779115b8efd
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Sat Jun 29 03:43:47 2024 -0400

    Fix 'Help' link (#70)
    
    Co-authored-by: Jürgen Gmach <juergen.gmach@canonical.com>

commit 89f08619f4c1cbb6e82bc95fd3cdc30b802e9c37
Author: gerryRcom <gerryr@gerryr.com>
Date:   Fri Jun 28 19:52:32 2024 +0100

    oda spelling check on live-patching doc

commit 96924bd1cf580875d76ed28afa3db83d0d642247
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Fri Jun 28 08:44:30 2024 -0400

    Fix 'Getting'

commit be6124ff67fc89a604ebad566805e7e535a01377
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Fri Jun 28 09:00:41 2024 -0400

    Fix 'JavaScriptIntegrationTesting' link

commit da7f6bfa597f2ea1e8df57dbbec7217fd746268f
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Fri Jun 28 07:46:05 2024 -0400

    Fix 'FixBugs'

commit 2ca5b808797ccd2c24cfb65a06d98e1db844b1b1
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Thu Jun 27 11:02:31 2024 -0400

    remove underscores

commit 7577f7674066d4e1d974e956ab2506e0d6f5a89b
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Tue Jun 25 13:22:07 2024 -0400

    Fix '../Trunk'

commit deb42beb594b860356dfe11297516d26609d1018
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Thu Jun 27 11:52:33 2024 -0400

    Fix 'Database/LivePatching'

commit ded351427d3f694d16855f3b4c44e085eb4e551c
Author: gerryRcom <gerryr@gerryr.com>
Date:   Thu Jun 27 19:47:05 2024 +0100

    oda spelling check on merge-reviews doc

commit c07847f039bc9414410ebf134d263174004a0a67
Author: gerryRcom <gerryr@gerryr.com>
Date:   Thu Jun 27 08:22:23 2024 +0100

    oda spelling check on db-devel doc

commit 6a54f46fedfcfdb3385dd8ff5c2f1d4a9ce45f15
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Tue Jun 25 12:32:41 2024 -0400

    remove updated link from linkcheck_ignore

commit 6eedaa9f3d5eaee21242280b1ead71c376698c4e
Author: Jared Nielsen <nielsen.jared@gmail.com>
Date:   Sat Jun 22 12:59:24 2024 -0400

    Fix 'PolicyAndProcess/DatabaseSchemaChangesProcess'

commit 92d1b15eafc2a90a88e24afd5a6938f277314d8a
Author: gerryRcom <gerryr@gerryr.com>
Date:   Wed Jun 26 19:30:14 2024 +0100

    oda spelling check on css-sprites doc

commit aeb7e5c2d4186ba45cb3279e24c3716e7752b32c
Author: gerryRcom <gerryr@gerryr.com>
Date:   Tue Jun 25 20:06:46 2024 +0100

    oda spelling check on registry doc

commit 13eb716d534b41ee60ac6adbf8b9d8fb96ca96cd
Author: gerryRcom <gerryr@gerryr.com>
Date:   Mon Jun 24 20:00:43 2024 +0100

    oda spelling check on triage-bugs doc

commit b7ad120ca563e3a1ac82f5ec7c7742874b53d88b
Author: gerryRcom <gerryr@gerryr.com>
Date:   Mon Jun 24 19:51:08 2024 +0100

    oda spelling check on triage-bugs doc

commit a83419e47f21071ae53a7036210a7c650195e8ef
Author: gerryRcom <gerryr@gerryr.com>
Date:   Fri Jun 21 21:54:21 2024 +0100

    oda spelling check on schema-changes doc

commit 486b54241a46ec42f48a05a0081b238699c0557b
Author: gerryRcom <gerryr@gerryr.com>
Date:   Thu Jun 20 20:36:01 2024 +0100

    oda spelling check on submitting-a-patch doc

commit a890a576681258d647d20b8fdc5c80b14f490d94
Author: gerryRcom <gerryr@gerryr.com>
Date:   Tue Jun 18 20:09:14 2024 +0100

    oda spelling check on database-setup doc

commit b52d850a0d2456f7925a91cb3e2ff4a8c44711a5
Author: gerryRcom <gerryr@gerryr.com>
Date:   Mon Jun 17 12:18:09 2024 +0100

    oda spelling check on contribute-to doc

commit 074e13a662821ba17d1c99e2814ef38fe2206a01
Author: gerryRcom <gerryr@gerryr.com>
Date:   Fri Jun 14 13:17:53 2024 +0100

    oda spelling check on getting-help-hacking

commit 81b6f8025aecf35c48b6660510447e07910d4b8e
Author: gerryRcom <gerryr@gerryr.com>
Date:   Thu Jun 13 20:58:20 2024 +0100

    oda spelling check on explanation-hacking

25 Apr 2025 2:35pm GMT

The Incus team is pleased to announce the release of Incus 6.12!

This release comes with some very long awaited improvements such as online growth of virtual machine memory, network address sets for easier network ACLs, revamped logging support and more!

On top of the new features, this release also features quite a few welcome performance improvements, especially for systems with a lot of snapshots and with extra performance enhancements for those using ZFS.

The highlights for this release are:

• Network address sets
• Memory hotplug support in VMs
• Reworked logging handling & remote syslog
• SNAT support on complex network forwards
• Authentication through access_token parameter
• Improved server-side filtering in the CLI
• More generated documentation

The full announcement and changelog can be found here.
And for those who prefer videos, here's the release overview video:

You can take the latest release of Incus up for a spin through our online demo service at: https://linuxcontainers.org/incus/try-it/

And as always, my company is offering commercial support on Incus, ranging from by-the-hour support contracts to one-off services on things like initial migration from LXD, review of your deployment to squeeze the most out of Incus or even feature sponsorship. You'll find all details of that here: https://zabbly.com/incus

Donations towards my work on this and other open source projects is also always appreciated, you can find me on Github Sponsors, Patreon and Ko-fi.

Enjoy!

25 Apr 2025 4:05am GMT

One of my favourite authors, Douglas Adams, once said that "we are stuck with technology when what we really want is just stuff that works." Whilst Adams is right about a lot of things, he got this one wrong - at least when it comes to infrastructure. As our Infra Masters 2025 event demonstrated, infrastructure […]

24 Apr 2025 12:36pm GMT

Ampere and Canonical are pleased to celebrate new milestones in their ongoing partnership including the completion of Canonical's System-on-Chip (SoC) certification on AmpereOne®, and the extension of the partnership into the AI Platform Alliance, a strategic group of full stack ecosystem partners that provide enterprise-grade curated solutions specifically developed for AI inference use cases. The […]

23 Apr 2025 10:06am GMT

The dipole program is part of the Yagi-Uda project, a collection of tools designed for the analysis and optimization of Yagi-Uda antennas. This particular tool calculates the impedance of a single dipole, making it a useful utility for antenna engineers and amateur radio enthusiasts.

Installation on Ubuntu/Debian

To install the Yagi-Uda software suite, including dipole, run the following command:

sudo apt install yagiuda

This package includes several tools for Yagi-Uda antenna analysis and design, making it a valuable addition for those working with antennas.

Usage

To compute the impedance of a dipole, use the following command:

dipole <frequency> <length> <diameter>

For example, to calculate the impedance of a dipole at 7.1 MHz with a length of 20 meters and a diameter of 1.5 mm, run:

dipole 7.100mhz 20m 1.5mm

Example Output:

Self impedance of a dipole:
7.100000 MHz,  length 20.000000 m, diameter 1.500000 mm, is 
Z = 62.418686  -48.363233 jX Ohms

This output indicates:

• Frequency: 7.1 MHz
• Length: 20 meters
• Diameter: 1.5 mm
• Impedance (Z): 62.42 - j48.36 Ω

The negative reactance (-48.36 Ω) suggests the dipole is capacitive, meaning it is too long at this frequency. To achieve resonance (purely resistive impedance), the dipole length should be slightly reduced.

Related Tools

The Yagi-Uda project includes additional tools that help with various aspects of antenna design and optimization:

• first - Initial calculations for antenna design
• input - Processes input parameters for analysis
• output - Displays calculated results
• optimise - Helps refine antenna parameters for better performance

Each of these tools contributes to designing and analyzing Yagi-Uda antennas effectively.

Supported Platforms

The Yagi-Uda project was primarily developed for UNIX-based systems, including Linux distributions such as Ubuntu and Debian. While efforts were made to port it to other operating systems, its primary focus remains on UNIX environments.

Reporting Bugs

If you encounter any issues while using dipole or other Yagi-Uda tools, you can report them to Dr. David Kirkby (G8WRB) at david.kirkby@onetel.net. Providing clear, reproducible steps will help ensure that reported bugs are addressed efficiently.

Conclusion

For amateur radio operators and engineers working with Yagi-Uda antennas, the dipole program is a valuable tool for analyzing a single dipole's impedance. With an easy installation process on Debian-based systems, it is an accessible and practical choice for antenna analysis.

The post Understanding Yagi-Uda's dipole Program for Antenna Analysis appeared first on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

19 Apr 2025 12:06pm GMT

Ubuntu MATE 25.04 is ready to soar! 🪽 Celebrating our 10th anniversary as an official Ubuntu flavour with the reliable MATE Desktop experience you love, built on the latest Ubuntu foundations. Read on to learn more 👓️

A Decade of MATE

This release marks the 10th anniversary of Ubuntu MATE becoming an official Ubuntu flavour. From our humble beginnings, we've developed a loyal following of users who value a traditional desktop experience with modern capabilities. Thanks to our amazing community, contributors, and users who have been with us throughout this journey. Here's to many more years of Ubuntu MATE! 🥂

What changed in Ubuntu MATE 25.04?

Here are the highlights of what's new in the Plucky Puffin release:

• Celebrating 10 years as an official Ubuntu flavour! 🎂
• Optional full disk encryption in the installer 🔐
  • Enhanced advanced partitioning options
  • Better interaction with existing BitLocker-enabled Windows installations
  • Improved experience when installing alongside other operating systems

Major Applications

Accompanying MATE Desktop 🧉 and Linux 6.14 🐧 are Firefox 137 🔥🦊, Evolution 3.56 📧, LibreOffice 25.2.2 📚

See the Ubuntu 25.04 Release Notes for details of all the changes and improvements that Ubuntu MATE benefits from.

Upgrading to Ubuntu MATE 25.04

The upgrade process to Ubuntu MATE 25.04 is the same as Ubuntu.

• Ubuntu 25.04 Upgrade Process

There are no offline upgrade options for Ubuntu MATE. Please ensure you have network connectivity to one of the official mirrors or to a locally accessible mirror and follow the instructions above.

19 Apr 2025 4:48am GMT

The latest interim release of Ubuntu introduces "devpacks" for popular frameworks like Spring, along with performance enhancements across a broad range of hardware. 17 April 2025 Today Canonical announced the release of Ubuntu 25.04, codenamed "Plucky Puffin," available to download and install from ubuntu.com/download. Ubuntu 25.04 delivers the latest GNOME 48 with support for triple […]

17 Apr 2025 3:23pm GMT

Focal Fossa will reach the End of Standard Support in May 2025, also known as End Of Life (EOL). Ubuntu 20.04 LTS has become a critical component for millions of IoT and embedded devices worldwide, including kiosks, digital signage solutions, industrial appliances, and robotic systems. The release has been foundational for companies innovating in various […]

16 Apr 2025 3:16am GMT

Part 1 of how we ran a design sprint to refresh our website. Sharing what worked, what didn't, and lessons from designing for open source in mind.

14 Apr 2025 10:08am GMT

Explore how Anbox Cloud meets the challenges of development in connected cars and automotive infotainment systems

10 Apr 2025 9:23am GMT