Dear Tumbleweed users and hackers,

This week saw the release of 5 snapshots (0731, 0802, 0803, 0804, and 0805).

A couple of long-standing hurdles in our staging projects have finally been cleared. Highlighting these deliveries is the official arrival of Podman 6.0.0 in snapshot 0802, bringing a major stack update that defaults rootless networking to pasta and removes legacy components like cgroups v1, slirp4netns, and CNI support. Hand-in-hand with toolchain progress, python-Sphinx 9.1.0 also successfully landed in snapshot 0802, resolving the python311 and python312 documentation build issues that had previously held it back.

Additionally, shadow 4.20.0 has landed with significant changes. In this version, several deprecated features have been removed entirely, including the PASS_MIN_DAYS setting and the associated -m or --mindays flags in chage and passwd, which are considered security vulnerabilities. As a result, scripts relying on these flags will now intentionally fail, so users and administrators should review their automated user management workflows.

In desktop environment updates, Plasma 6 Workspace has transitioned to defaulting SDDM to the Plasma Wayland session, no longer recommending the X11 session. Additionally, both Breeze6 and Plasma 6 integration have split their legacy Qt 5 components into separate optional packages.

This week also addressed multiple security issues across core system libraries. Highlights include libssh2_org incorporating fixes for several CVEs (including heap overflows and double-frees) and libvirt 12.6.0 resolving multiple vulnerabilities along with a virsh crash fix.

These 5 snapshots delivered the following updates:

• apparmor 5.0.2
• aws-lc 5.4.0
• glib2 2.88.3
• hwdata 0.410
• ImageMagick 7.1.2.29
• libvirt 12.6.0
• Linux Kernel 7.1.6
• Mesa 26.1.6
• Mozilla Firefox 153.0.3
• nano 9.2
• nghttp2 1.70.0
• PHP 8.5.9
• Podman 6.0.0
• python-Sphinx 9.1.0
• qemu 11.0.3
• Samba 4.24.5
• SDL3 3.4.14
• shadow 4.20.0
• unbound 1.26.0
• Xen 4.22.0

As we look to the horizon, the staging areas are dominated by one particularly massive system transition, alongside several notable packages currently undergoing integration testing.

• glibc 2.44: The transition is progressing well in its staging area with only four build failures observed so far, which are tracked under boo#1273584.
• KDE Plasma 6.7.4
• LibreOffice 20.2.5.2
• Linux Kernel 7.1.7
• Swig 4.5.0
• libnettle 4.0.0: Currently breaking libzypp’s test suite.
• icewm 4.0: Undergoing testing, but currently experiencing redraw issues in combination with the YaST installer.

The votes are in! The openSUSE Asia Summit Committee is pleased to announce that **A. Thalida has been selected as the winner of the openSUSE.Asia Summit 2026 Logo Competition.

Congratulations, A. Thalida! 🎉

The winning logo will become the official visual identity of openSUSE.Asia Summit 2026, representing this year’s conference in Yogyakarta, Indonesia. As the winner, A. Thalida will receive a special appreciation gift from the organizing committee.

This year, we received nine logo submissions from contributors across several countries. The quality and creativity of all the entries made the selection process both exciting and challenging. The final decision was made through a voting process involving the openSUSE.Asia Committee and the local organizing team.

We would like to extend our sincere thanks to everyone who participated in this year’s competition:

• Haruo Yoshino - Japan
• Lubos Kocman - Czechia
• Subhasis Chakraborty - India
• Edmon Fuerte - Philippines
• Rhesa Prawedha - Indonesia
• Melchias Ari Setiadji - Indonesia
• Raden Neomy Lusie Ratna Deseina Budy Putri - Indonesia
• A. Thalida

Your creativity, passion, and support continue to strengthen the openSUSE community, and we truly appreciate every submission.

Finally, thank you to everyone who participated in the voting process. We look forward to welcoming you to openSUSE.Asia Summit 2026, taking place on 3–4 October 2026 in Yogyakarta, Indonesia. See you there!

The post discusses various topics in the tech and Linux community, including VPN usage, user accounts on computers, and recent news like Arch Linux disabling AUR package adoption to counter malware, upcoming features in Ubuntu 26.10, and Sony's response to backlash regarding PlayStation discs. It also mentions community activities and participant project links.

Dear Tumbleweed users and hackers,

This week saw the release of 5 snapshots (0723, 0724, 0726, 0728, and 0729).

A major milestone was reached as GCC 16 has officially landed as Tumbleweed’s new default system compiler in snapshot 0726. Because this transition required rebuilding the entire repository to benefit from the new compiler optimizations, snapshot 0726 was exceptionally large. Along with this compiler shift, the linux-glibc-devel 7.1 headers successfully made their way to users in snapshot 0728.

Additionally, we saw the return of multipath-tools 0.15~1 in snapshot 0726 after its brief “yo-yo” revert last week.

These 5 snapshots delivered the following updates:

• GCC 16 as the default system compiler
• linux-glibc-devel 7.1
• Mozilla Firefox 153.0
• systemd 261.2
• OpenSSH 10.4p1
• multipath-tools 0.15~1
• ntfs-3g_ntfsprogs 2026.7.7
• btrfsprogs 7.1
• python-numpy 2.4.6
• java-25-openjdk 25.0.4.0
• AppStream 1.1.5
• freerdp 3.30.0
• bind 9.20.26
• cryptsetup 2.8.7
• virtualbox 7.2.14
• wicked 0.6.80
• util-linux 2.42.2
• fwupd 2.1.7
• libostree 2026.2
• rpmlint: enforce whitelisting for capabilities in SUIDPermissionsCheck via bugreports

With these updates successfully rolled out, it is time to turn our gaze forward and see what the staging areas are cooking up for the near future.

• Podman 6.0.0: Undergoing integration and sync testing with buildah and skopeo.
• Linux Kernel 7.1.5
• Mozilla Firefox 153.0.1
• Samba 4.24.5
• PHP 8.5.9
• python-Sphinx 9.1.0: This update is currently breaking python311:doc and python312:doc.
• glibc 2.44

The author describes a journey of upgrading their home office setup, initially using a six-monitor rig with inadequate screens. They found improvements in an LG DualUP monitor and decided on a dual setup using INNOCN displays to enhance productivity. Despite some connection issues and pixel density discrepancies, the new layout significantly increased usability and desk efficiency.

🚢 Shipped this week Fixed issues, small features, security updates, minor releases, new external contributors… de-group when filter_search_text on top of filter_labels - #20097 Fix overlapping labels on image template radio buttons - #19931 make it visually clear that attributes are expandable - #19984 Fix backlog link for users in beta - #20092 Do not link hidden monitor workers to build logs - #20023 Reject release targets that point back to the same repository -...

For many years, I didn’t think that Tor could be useful for me. However, I’ve recently found a Gist on GitHub that describes how you can use it to harden your central syslog-ng server. And while I have yet to try it, at least now I have a reason to actually test Tor.

The Tor website describes the project as follows: “Protect yourself against tracking, surveillance, and censorship.” I live in a country where thankfully I do not need these, nor do I perform any activities for which Tor would be useful. However, sometimes I hear from syslog-ng users that they want to hide their logging infrastructure with something more than what mutual TLS authentication makes possible. This is where this short how-to might be useful for you:

https://gist.github.com/hashgh0st/19bcfa4bfc96fbf0bbd2897b66c77db7/

The Gist is about how to install / configure syslog-ng and Tor on a FreeBSD client and server. I have a couple of FreeBSD boxes lying around, so I will test the instructions there. However, with minimal changes, the procedure should work on any Linux distribution as well.

Originally published at https://www.syslog-ng.com/community/b/blog/posts/syslog-ng-hardening-using-tor

🚢 Shipped this week Fixed issues, small features, security updates, minor releases, new external contributors… Unify release API parameter naming and document it#20054 BSPublisher/Registry: support the cosign newbundle format#20026 PBuild: Fix auth for multiple remote registry assets#1162 Make obs-service-kiwi_metainfo_helper use BUILD_BUILDTIME#1367165 👩‍💻 Operations this week Statistics, deployments and incidents of https://build.opensuse.org/ In the last 7 days build.opensuse.org served 25.3 million HTTP requests resulting in 2.45 million package builds. With ~200.000 builds more than last week...

The content discusses various technology and Linux-related updates, including a live weekend discussion about user experiences with Fedora and job openings at Epic Games focused on Linux security. It also covers IBM's new chip architecture advancements and Dell surpassing HP in U.S. PC sales amid a shrinking market.

Back when I was working at Canonical on the Ubuntu phone project, test-driven development was the default and natural way to work. One thing I noticed and genuinely liked was how Ubuntu and Debian ship functional tests alongside many of their packages. Not only build-time unit tests hidden in the CI pipeline, but installable test binaries that you can run against the actual packages on an actual system. They are named *-tests or *-test, and they live in the archive next to the production packages.