Skip to main content
  1. Blog
  2. Article

Jane Silber
on 22 January 2008

Why a Canonical blog?


Welcome to the Canonical Blog. The goal of the blog is to provide a vehicle for people who work for Canonical to respond to some of the questions we get asked, to explore the issues we care about, and to expand on some of the initiatives in which we are involved. It is a companion piece to the Fridge, Planet Ubuntu and to Mark’s blog but it is different as it is not the voice of the Ubuntu Community.

It is the Canonical (capital C) voice. It is (we hope) the considered opinion of people within Canonical with a valuable perspective on a specific topic. It is here to address that gap where a press release is over the top but we want to respond to an issue or we want to provide more colour on an announcement, where we want to provoke debate or bring attention to something that we feel is important.

We live in interesting times in computing and at Canonical we are fortunate to find ourselves at the centre of a lot of the more interesting developments. We hope this blog develops into a useful perspective on these issues.

– The Canonical Team

Related posts


Canonical
16 March 2026

Canonical announces it will distribute NVIDIA DOCA-OFED in Ubuntu

AI Article

Today Canonical, the publishers of Ubuntu, announced that it will integrate and distribute the NVIDIA DOCA-OFED networking driver with Ubuntu. ...


Canonical
16 March 2026

Meet Canonical at NVIDIA GTC 2026: NVIDIA CUDA and NVIDIA Vera Rubin NVL72 support in Ubuntu 26.04 LTS

Ubuntu Article

Previewing at NVIDIA GTC 2026: NVIDIA CUDA support in Ubuntu 26.04 LTS, NVIDIA Vera Rubin NVL72 architecture support in Ubuntu 26.04, Canonical’s official Ubuntu image for NVIDIA Jetson Thor, upcoming support for NVIDIA DGX Station and NVIDIA DOCA-OFED, and NVIDIA RTX PRO 4500 support. NVIDIA GTC 2026 is here, bringing together the techno ...


Luci Stanescu
12 March 2026

AppArmor vulnerability fixes available

Ubuntu Article

Qualys discovered several vulnerabilities in the AppArmor code of the Linux kernel. These are being referred to as CrackArmor, while CVE IDs have not been assigned yet. All of the vulnerabilities require unprivileged local user access. The impact of these vulnerabilities ranges from denial of service to kernel memory information leak, rem ...