How does the TUXEDO OS release model work? - TUXEDO Computers

Frequently, we receive questions regarding the release model of our in-house distribution TUXEDO OS. Common inquiries include which base we use for TUXEDO OS or why certain packages are not offered in their latest version. In this article, we explain our release model and answer these and similar questions.

Semi-Rolling Release

Our release model falls under the category of semi-rolling release. This means that some components are kept up to date, while others follow the base of the distribution.

The Base

Since we’re talking about the base: TUXEDO OS uses the latest long-term support version of Ubuntu (LTS) as its base. We are currently transitioning from Ubuntu 22.04 LTS to 24.04 LTS. We are often asked why we use Ubuntu and not Debian or another distribution. This is partly due to the foundation of our KDE Plasma integration, which originates from the user edition of KDE neon. KDE neon is also based on Ubuntu, making our work in this context significantly easier.

The Plasma Desktop

Based on the latest Ubuntu LTS, which is shipped with GNOME as the default desktop, we use the current KDE Plasma desktop instead. This consists of the Plasma Desktop, KDE Frameworks, and KDE Gear. For this, we source around 270 packages from the KDE neon repositories.

Packages We Package Ourselves

Then there are the packages that we package and keep up to date ourselves for various reasons. The reason we don’t do this with all or more packages is that packaging, testing and maintaining them involves considerable time and effort.

The following packages are kept up to date or made available in our repository for other reasons, so they are automatically updated during system updates:

• bluez
• calamares
• chromium
• egl-wayland
• firefox
• libdrm2
• maliit-keyboard
• mc
• mesa
• nextcloud-desktop
• openrgb
• pipewire
• sddm
• thunderbird
• wireplumber
• virtualbox
• xwayland

Why Do We Package Ourselves?

We mainly keep packages like Firefox, Thunderbird, and Chromium up to date for security reasons. Other packages like mesa, egl-wayland, libdrm2, pipewire, and wireplumber ensure a constantly up-to-date graphics stack in connection with current graphics drivers. VirtualBox is kept up to date to ensure support for our kernels.

For Different Reasons

However, keeping packages up to date is not always the reason we package them ourselves. For instance, the virtual keyboard maliit-keyboard is in in our repository in an older version because the current package from KDE neon does not work on our InfinityFlex Convertible. Other packages like the file manager mc are prevented from using the regular version due to long-standing, unresolved bugs in Ubuntu.

As you can see, we invest quite some time and thought into curating the package list for TUXEDO OS. If you have any suggestions about why we should package a certain application ourselves and if it would provide value for all users, feel free to let us know on GitLab. We will then evaluate whether the effort is worth the gain.