Dear Tumbleweed users and hackers,

This week looks like OBS was faster in building than I was in reviewing the QA results – at least two snapshots would have been releasable, but were replaced before the full tests were done. As a consequence, we have ‘only’ released four snapshots (0220, 0223, 0224, and 0226)

The most relevant changes shipped are:

• upower 1.91.1
• Linux kernel 6.19.3
• libupnp 1.18.0
• libzio 1.12
• pipewire 1.6.0
• poppler 26.02.0
• mdadm 4.5+43
• Mesa 26.0.1
• Mozilla Firefox 148.0
• qemu 10.2.1
• dnf 5.4.0

Things being worked on at the moment and being delivered as soon as QA passes:

• systemd 259.5
• KDE Plasma 6.6.1
• gettext 1.0
• Switch default bootloader on uefi systems to systemd-boot (aligning tumbleweed to microos)
• glibc 2.43: metabug: https://bugzilla.opensuse.org/show_bug.cgi?id=1257250

The data sheet of my new AI focused mini workstation from HP mentions Ubuntu 24.04 as the supported Linux distribution. I have tried that, but I could not get the installer to run. However, 25.10 installed without any problems, even from an openSUSE branded USB stick :-)

I must admit that I’m not an Ubuntu fan, but installed it anyway, as Ubuntu is the “official” Linux distro for this machine. GNOME is heavily modified compared to other distros. For GUI apps the focus seems to be shifted to snaps from distro packages.

For now I did not test the in hardware AI support, just tried to collect some first impressions. I ended up installing a few 3D games and playing :-) Having AMD graphics has the advantage that everything works out of box. There is no need for binary only drivers, extra repositories, praying to the binary gods, etc. It just works. Fully open source.

This blog is part of a longer series about my adventures with my new machine and AI. You can reach me to discuss this blog on one of the contacts listed in the upper right corner. You can read the rest of the blogs under the toy tag.

This is a roundup of articles from the openSUSE community listed on planet.opensuse.org.

The community blog feed aggregator lists the featured highlights below from Feb. 20 to 26.

Blogs this week highlight music and Saloons to NVIDIA GPUs and a Git workshop. Blogs also highlight Ubuntu and openSUSE installs on the HP Z2 Mini, KDE Plasma and Krita releases, syslog-ng 4.11’s new features, and openSUSE Tumbleweed’s latest snapshot updates.

Here is a summary and links for each post:

New Toy: Installing Ubuntu on the HP Z2 Mini

Peter Czánik’s Blog revisits and expands on a prior blog covered below about installing Ubuntu 24.04 as an officially supported Linux distribution for the Ryzen AI Max+ PRO 395-powered HP Z2 Mini workstation. The 24.04 installer failed to run—while Ubuntu 25.10 installed successfully even from an openSUSE-branded USB stick.

How to Configure KDE Plasma’s “Only Icons” Taskbar Behavior

The KDE Blog explains how to switch the Plasma task manager to “Icons Only” mode for a minimalist desktop layout that displays application icons without window titles or progress indicators. The tutorial walks users through right-clicking the task manager panel, accessing Task Manager Settings, and selecting the “Icons Only” option under the Display Style dropdown.

Version 4.11.0 of syslog-ng Is Now Available

Peter Czánik’s Blog announces the release of syslog-ng 4.11.0 that now enables bidirectional integration with Kafka pipelines. The update introduces Elasticsearch/OpenSearch data stream support, OAuth2 authentication for cloud destinations including gRPC-based modules, load-balancer failover functionality, and more. Fedora 44/Rawhide and openSUSE Tumbleweed updates are expected shortly as the project maintains its commitment to broad platform accessibility.

Krita 5.3 and Krita 6.0 Betas Released

The KDE Blog announces the second beta releases of both Krita 5.3.0 and Krita 6.0.0, which features a completely rewritten text tool with direct canvas editing and OpenType support plus a new knife tool for splitting vector objects in the 5.3 branch. The 6.0 beta introduces foundational Qt6 migration with native Wayland support including color management, fractional scaling, and HDR on Linux.

First Update for Plasma 6.6 Released

The KDE Blog reports that the KDE Community delivered the first bugfix update for Plasma 6.6 one week after its release. The update builds upon Plasma 6.6’s flagship features including OCR text extraction in Spectacle, the redesigned Plasma Keyboard for touch devices, Plasma Setup assistant for post-install configuration and more.

New toy: Installing openSUSE Tumbleweed on the HP Z2 Mini

Peter Czánik’s Blog details his successful installation of openSUSE Tumbleweed on the compact HP Z2 Mini AI workstation after Ubuntu 24.04’s installer crashed and the machine’s finicky USB boot support rejected older flash drives, which requires a USB-C stick and BIOS adjustments including Secure Boot disablement before Linux would install. The Tumbleweed installer with its classic YaST interface worked flawlessly on the AMD Ryzen AI Max+ PRO 395 hardware, though an unexpected snag emerged post-installation when GRUB2-BLS.

Git Workshop: The Premier Libre Collaboration Tool at LliureJam 2026 Valencia

The KDE Blog covers a Git workshop held at the LliureJAM 2026 event in Valencia, where participants learned about Git as a key free and collaborative version-control tool. The session taught fundamentals for software development, game creation, and documentation management. It was preceded by an install party offering GNU/Linux installation assistance, ad-blocking setup for mobile devices, and guidance on libre social networks.

Free Software Could Change the World of AI Music Overnight

The Assunto Nerd Blog discusses how open-source software is rapidly reshaping the landscape of AI-driven music generation. It highlights how combining open-source models like ACE-Step-1.5 with intuitive frontends such as ACE-Step UI, which allows users to generate full songs in seconds on consumer GPUs.

3 Native FPS Games for Linux

The KDE Blog highlights three free, open-source first-person shooters games available natively on Linux via Flathub. Total Chaos, Wolfenstein: Blade of Agony and The AMC Squad. All three titles offer substantial single-player campaigns with character progression systems while adhering to libre software principles.

Linux Saloon 188 | MX Linux 25.1 Distribution Exploration

The CubicleNate Blog highlights episode 188 of Linux Saloon. The discussion covered MX Linux’s unique positioning between traditional Debian stability and modern usability features, which includes MX Tools for system maintenance, snapshot capabilities via Timeshift, and seamless migration paths for former Windows users seeking a gentle Linux introduction. Participants also debated the distribution’s community-driven governance model and its pragmatic approach to balancing legacy hardware support with contemporary desktop expectations.

Installation of NVIDIA drivers on openSUSE and SLE (G07)

Stefan’s Blog explains how to install the G07 NVIDIA drivers on openSUSE and SUSE Linux Enterprise, which covers both the Open and CUDA repository methods. Users on Tumbleweed, Leap 15.6/16.0, and all current SLE versions must continue using G06 drivers until G07 packages complete QA and become available through official update channels.

Plasma 6.6 Is Here – This Week in Plasma

The KDE Blog covers the official release of Plasma 6.6. The update delivers practical workflow enhancements including per-application volume control via task manager hover, emoji skin tone selection, QR code Wi‑Fi scanning, customizable global themes with automatic day/night switching, and four colorblind accessibility filters including a new grayscale mode. It also introduces smoother high-refresh-rate animations, expanded Wayland accessibility support, flexible virtual desktop options, and gaming improvements.

Librsvg Got Its First AI Slop Pull Request

The Federico’s Blog reports that the librsvg project received two so-called “AI slop” pull request on GitHub despite its code being developed in gitlab.gnome.org with the README warning not to send PRs to GitHub. Both PRs were closed by the submitter within minutes of creation. The author reported the submissions as spam.

openSUSE Tumbleweed Weekly Review – Week 8 of 2026

Victorhck and dimstar report on the six snapshots there were delivered. The review highlights updates including KDE Plasma 6.6’s official arrival in the repository, Mesa 26.0.0 final release, and glibc 2.43 integration—marking major milestones for graphics performance, desktop experience, and core system libraries.

What Windows Doesn’t Let You Do But Linux Does

introduces a video and discussion about capabilities that Linux offers which Windows typically restricts or complicates, aimed at users reconsidering Windows as support ends. The article highlights practical examples like replacing display servers, customizing window management behaviors down to the pixel level, packaging applications in multiple formats without vendor lock-in, and maintaining full control over when and how system updates are applied.

Version 4.11.0 of syslog-ng is now available. The main attraction is the brand new Kafka source, but there are many other smaller features and improvements, as well.

Before you begin

If you happen to use Debian, Ubuntu or the RHEL family of operating systems (RHEL, CentOS, Rocky Linux, Alma Linux, Oracle Linux, etc.) then ready-to-use packages are already available as part of the release process. For details, check the README in the syslog-ng source code repository on GitHub: https://github.com/syslog-ng/syslog-ng/?tab=readme-ov-file#installation-from-binaries The syslog-ng container is also updated to this release: https://github.com/syslog-ng/syslog-ng/?tab=readme-ov-file#installation-from-binaries

I plan to update Fedora 44 and Rawhide soon, just like openSUSE Tumbleweed. For other distributions, you often need to wait a bit more or use third-party repositories. Our 3rd-party repo page has some pointers: https://www.syslog-ng.com/products/open-source-log-management/3rd-party-binaries.aspx

What is new?

The largest new feature is the Kafka source, which allows you to collect log messages from Kafka streams. For many years, syslog-ng had a Kafka destination, allowing you to send log messages to a Kafka-based data pipeline. The Kafka source enables syslog-ng to collect log messages from Kafka, parse and filter log messages, and route them to various destinations. You can learn more about the Kafka source from the syslog-ng documentation at https://syslog-ng.github.io/admin-guide/060_Sources/038_Kafka/README .

Support for Elasticsearch / OpenSearch data streams was also added: https://www.syslog-ng.com/community/b/blog/posts/changes-in-the-syslog-ng-elasticsearch-destination

4.11 also includes many other interesting new features and bug fixes, including:

• OAuth2 support in the cloud-auth module, including gRPC-based destinations
• Failover support in the load-balancer
• Improved performance and lowered resource usage on macOS
• cmake support feature parity with autotools

For a complete list of changes, check the release notes on GitHub: https://github.com/syslog-ng/syslog-ng/releases/tag/syslog-ng-4.11.0

As usual, while we make every effort to make all features work everywhere, it is not always technically possible. For example, compilers and / or dependencies are too old to support gRPC-based modules in older RHEL, SUSE and Debian releases.

What is next?

As usual: feedback is very welcome. If you have any problems with the syslog-ng 4.11.0 release, open an issue on GitHub at https://github.com/syslog-ng/syslog-ng/issues Your report helps us to make syslog-ng better. Of course, we are also very happy about any positive feedback :-)

Originally published at https://www.syslog-ng.com/community/b/blog/posts/version-4-11-0-of-syslog-ng-is-now-available

Last week I introduced you to my new toy at home: an AI focused mini workstation from HP. It arrived with Windows pre-installed, but of course I also wanted to have Linux on the box.

Documentation mentions that I have to disable secure boot and make a few more changes before installing Linux. I did all the suggested BIOS changes before installing Linux.

The data sheet mentions Ubuntu 24.04 as the supported Linux distribution. I have tried that, but I could not get the installer to run. Along the way I realized that the USB boot support is very picky on this box. Using my old USB sticks, which work perfectly in my laptop and old desktop, does not work at all. Also, changing the USB stick requires you to turn the machine off and on, a simple reboot is not enough. Finally I found a USB-C stick, and that almost worked with Ubuntu 24.04. It booted, but the installer crashed.

As I have been a S.u.S.E. / openSUSE user for the past 30 years, I did not mind this failure much. I downloaded the openSUSE Tumbleweed installer, and it worked like a charm. Best of all, unlike openSUSE Leap 16.0, Tumbleweed still has the good old YaST installer I used for decades. Installation was quick, easy and rock solid.

Surprise arrived when I rebooted the machine. Windows was not available in the boot menu. As it turned out, Tumbleweed used a new flavor of GRUB2 by default: grub2-bls, but that does not seem to boot other operating systems. There is no supported way to switch back to grub2-efi, so I reistalled openSUSE. Luckily it’s an easy job, and I did not have any data yet on the machine. So, it was just a few mouse clicks.

openSUSE is my daily driver, so I did not spend much time exploring the system. It seems to work just fine. Installing a few games and checking the in hardware AI support comes once I finished installing all operating systems on the machine. Next to Windows I plan to install openSUSE, Fedora and Ubuntu on the Linux side, and FreeBSD as well.

This blog is part of a longer series about my adventures with my new machine and AI. You can reach me to discuss this blog on one of the contacts listed in the upper right corner. You can read the rest of the blogs under the toy tag.

Important

This blogpost explains how to install new G07 NVIDIA drivers. It is temporarily available as long as the content of the current blogpost for installation of G06 NVIDIA drivers is still needed.

The availability of G07 NVIDIA driver packages will happen soon.

Currently this blogpost can be used for the following openSUSE and SLE products:

• (empty list)

For the following openSUSE and SLE products you still need to use the current blogpost for installation of G06 NVIDIA drivers:

• openSUSE Tumbleweed
• Leap 15.6 / SLE 15 SP6
• SLE 15 SP7
• Leap 16.0 / SLE 16

Both lists above are updated when G07 NVIDIA driver packages are becoming available for the appropriate products.

Let’s begin

This blogpost covers only installation of G07 drivers, i.e. drivers for GPUs >= Turing, i.e.

• Turing and higher (Open Kernel driver)

Check with inxi -aG on openSUSE Leap/Tumbleweed if you have such a GPU. Use hwinfo --gfxcard on SLE. Use G04/G05/G06 legacy drivers (Proprietary drivers) for older NVIDIA GPUs.

There are two different ways to install NVIDIA drivers. Either use GFX Repository or use CUDA Repository.

GFX Repository

First add the repository if it has not been added yet. On openSUSE Leap/Tumbleweed and SLE 15 Desktop and SLE 15 Workstation Extension it is being added by default. So check first, if it has already been added.

# openSUSE Leap/Tumbleweed
zypper repos -u | grep https://download.nvidia.com/opensuse/
# SLE
zypper repos -u | grep https://download.nvidia.com/suse

Verify that the repository is enabled. If the output was empty add the repository now:

# Leap 15.6
zypper addrepo https://download.nvidia.com/opensuse/leap/15.6/  nvidia
# Leap 16.0
zypper addrepo https://download.nvidia.com/opensuse/leap/16.0/  nvidia
# Leap 16.1 (Beta)
zypper addrepo https://download.nvidia.com/opensuse/leap/16.1/  nvidia
# Tumbleweed
zypper addrepo https://download.nvidia.com/opensuse/tumbleweed/  nvidia
# SLE15-SP6
zypper addrepo https://download.nvidia.com/suse/sle15sp6/  nvidia
# SLE15-SP7
zypper addrepo https://download.nvidia.com/suse/sle15sp7/  nvidia
# SLE16
zypper addrepo https://download.nvidia.com/suse/sle16/  nvidia
# SLE16.1 (Beta)
zypper addrepo https://download.nvidia.com/suse/sle16.1/  nvidia

With the following command the Open Kernel driver will be installed. In addition the CUDA and Desktop drivers are installed according to the software packages which are currently installed (Desktop driver trigger: libglvnd package). 

zypper in nvidia-open-driver-G07-signed-kmp-meta

Understanding package dependancies

The following graphics explains the installation and package dependancies. Zoom in for better reading.

Once in-sync becomes latest driver version, i.e the nvidia-open-driver-G07-kmp-<flavor> of latest driver has been released for your product and nvidia-open-driver-G07-kmp-meta has been updated accordingly all remaining userspace driver packages (nvidia-video-G07, nvidia-compute-utils-G07 and dependancies) get updated to latest driver version.

CUDA Repository

Add the repository if it hasn’t been added yet. On SLE15 it might have already been added as aModule. So check first:

# openSUSE Leap/Tumbleweed
zypper repos -u | grep https://developer.download.nvidia.com/compute/cuda/repos/opensuse15
# SLE
zypper repos -u | grep https://developer.download.nvidia.com/compute/cuda/repos/sles15

Verify that the repository is enabled. If the output is empty add the repository now:

# Leap 15.6/16.0/16.1(Beta)/Tumbleweed
zypper addrepo https://developer.download.nvidia.com/compute/cuda/repos/opensuse15/x86_64/  cuda
# SLE15-SPx/SLE16/SLE16.1(Beta) (x86_64)
zypper addrepo https://developer.download.nvidia.com/compute/cuda/repos/sles15/x86_64/  cuda
# SLE15-SPx/SLE16/SLE16.1(Beta) (aarch64)
zypper addrepo https://developer.download.nvidia.com/compute/cuda/repos/sles15/sbsa/  cuda

Use Open prebuilt/secureboot-signed Kernel driver

It is strongly recommended to use our prebuilt and secureboot-signed Kernel driver. Unfortunately this is often not the latest driver, which is availabe, since this driver needs to go through our official QA and Maintenance process before it can be released through our product update channels, but things are much easier to handle for the user.

# Install open prebuilt/secureboot-signed Kernel driver
zypper in nvidia-open-driver-G07-signed-cuda-kmp-default

# Make sure userspace CUDA/Desktop drivers will be in sync with just installed open prebuilt/secureboot-signed Kernel driver
version=$(rpm -qa --queryformat '%{VERSION}\n' nvidia-open-driver-G07-signed-cuda-kmp-default | cut -d "_" -f1 | sort -u | tail -n 1)

# Install CUDA drivers
zypper in nvidia-compute-utils-G07 == ${version} nvidia-persistenced == ${version}
# Install Desktop drivers
zypper in nvidia-video-G07 == ${version}

Use Open DKMS Kernel driver (latest driver available)

If you really need the latest Open driver, use NVIDIA’s Open DKMS Kernel driver. This will build this driver on demand for the appropriate Kernel during the boot process.

# Install latest Open DKMS Kernel driver 
zypper in nvidia-open-driver-G07

# Install CUDA drivers
zypper in nvidia-compute-utils-G07

# Install Desktop drivers
zypper in nvidia-video-G07

On Secure Boot systems you still need to import the certificate, so you can later enroll it right after reboot in the MOK-Manager by using your root password.

mokutil --import /var/lib/dkms/mok.pub --root-pw

Otherwise your freshly built kernel modules can’t be loaded by your kernel later.

Installation of CUDA

In case you used GFX Repository for installing NVIDIA drivers before, first add the CUDA Repository as outlined above in CUDA Repository chapter.

The following commands will install CUDA packages themselves. It describes a regular and minimal installation. In addition it makes it easy to do first tests with CUDA. Depending on which Kernel driver is being used it may be needed to install different CUDA versions.

# Kernel driver being installed via GFX Repo
cuda_version=13-1
# Kernel driver being installed via CUDA Repo
cuda_version=13-1

# Regular installation
zypper in cuda-toolkit-${cuda_version}
# Minimal installation
zypper in cuda-libraries-${cuda_version}

# Unfortunately the following package is not available for aarch64,
# but there are CUDA samples available on GitHub, which can be
# compiled from source: https://github.com/nvidia/cuda-samples
zypper in cuda-demo-suite-12-9

Let’s have a first test for using libcuda (only available on x86_64).

/usr/local/cuda-12/extras/demo_suite/deviceQuery

Which one to choose for NVIDIA driver installation: GFX or CUDA Repository?

Good question! Not so easy to answer. If you rely on support from NVIDIA (especially when using SLE), for Compute usage we strongly recommend to use the CUDA Repository for NVIDIA driver installation. Even if you use NVIDIA Desktop drivers as well.

For others - usually running openSUSE Leap/Tumbleweed - it’s fine to use GFX Repository for NVIDIA driver installation and adding CUDA Repository for installing CUDA packages.

Migration from G06 to G07 Open drivers

Migration from G06 Open drivers to G07 is a manual step. Uninstall all NVIDIA driver packages first:

rpm -e $(rpm -qa | grep -e ^nvidia -e ^libnvidia | grep -v container)

Then install G07 Open drivers as described in the sections above.

Known issues

CUDA Repository

Once you have added the CUDA Repository it may happen that some old or not recommended driver packages get mistakenly auto-selected for installation or even have already been mistakenly installed. These are:

• nvidia-gfxG05-kmp-default 535.x
• nvidia-open-gfxG05-kmp-default 535.x
• nvidia-open-driver-G06-kmp-default 570.x
• nvidia-driver-G06-kmp-default 570.x
• nvidia-open-driver-G06

In order to avoid mistakenly installing them add package locks for them with zypper.

zypper addlock nvidia-gfxG05-kmp-default
zypper addlock nvidia-open-gfxG05-kmp-default
zypper addlock nvidia-open-driver-G06-kmp-default
zypper addlock nvidia-driver-G06-kmp-default
zypper addlock nvidia-open-driver-G06

In case you see any of these packages already installed on your system, better read the Troubleshooting section below how to get rid of these and all other nvidia driver packages related to them. Afterwards add locks to them as described right above.

Tumbleweed

On Tumbleweed it may happen that some legacy driver packages get mistakenly auto-selected for installation or even have already been mistakenly installed. These are:

• nvidia-gfxG04-kmp-default
• nvidia-gfxG05-kmp-default

In order to avoid mistakenly installing them add package locks for them with zypper.

zypper addlock nvidia-gfxG04-kmp-default
zypper addlock nvidia-gfxG05-kmp-default

In case you see any of these packages already installed on your system, better read the Troubleshooting section below how to get rid of these and all other nvidia driver packages related to them. Afterwards add locks to them as described right above.

Leap 15.6

On Leap 15.6 when doing a zypper dup this may result in a proposal to dowgrade the driver packages to some older 570 version and switching to -azure kernel flavor at the same time. The culprit for this issue is currently unknown, but you can prevent it from happening by adding a package lock with zypper.

zypper addlock nvidia-open-driver-G06-signed-kmp-azure

Troubleshooting

In case you got lost in a mess of nvidia driver packages for different driver versions the best way to figure out what the current state the system is in is to run:

rpm -qa | grep -e ^nvidia -e ^libnvidia | grep -v container | sort

Often then the best approach is to begin from scratch, i.e remove all the nvidia driver packages by running:

rpm -e $(rpm -qa | grep -e ^nvidia -e ^libnvidia | grep -v container)

Then follow (again) the instructions above for installing the driver using the GFX or CUDA Repository.

You all know that librsvg is developed in gitlab.gnome.org, not in GitHub. The README prominently says, "PLEASE DO NOT SEND PULL REQUESTS TO GITHUB".

So, of course, today librsvg got its first AI slop pull request and later a second one, both in GitHub. Fortunately (?) they were closed by the same account that opened them, four minutes and one minute after opening them, respectively.

I looked.

There is compiled Python code (nope, that's how you get another xz attack).

There are uncomfortably large Python scripts with jewels like subprocess.run("a single formatted string") (nope, learn to call commands correctly).

There are two vast JSON files with "suggestions" for branches to make changes to the code, with jewels like:

• Suggestions to call standard library functions that do not even exist. The proposed code does not even use the nonexistent standard library function.

• Adding enum variants to SVG-specific constructs for things that are not in the SVG spec.

• Adding incorrect "safety checks". assert!(!c_string.is_null()) to be replaced by if c_string.is_null() { return ""; }.

• Fix a "floating-point overflow"... which is already handled correctly, and with a suggestion to use a function that does not exist.

• Adding a cache for something that does not need caching (without an eviction policy (so it is a memory leak)).

• Parallelizing the entire rendering process through a 4-line function. Of course this does not work.

• Adding two "missing" filters from the SVG spec (they are already implemented), and the implementation is todo!().

It's all like that. I stopped looking, and reported both PRs for spam.