Note: Swipe left on the briefing content to view the event timeline, historical background, technical details, and quick Q&A information.
Fwupd 2.0.15 Adds Support for ConnectX Network Cards
Fwupd 2.0.15 has been released, adding support for NVIDIA ConnectX-6, ConnectX-7, and ConnectX-8 network cards, as well as Foxconn SDX61 modems and Jabra Evolve2 devices.
This open-source updater, built around the Linux Vendor Firmware Service (LVFS), also includes new features and bug fixes.
Historical Background
Fwupd is an open-source Linux firmware update tool that works with the Linux Vendor Firmware Service (LVFS) to deliver updates from hardware manufacturers to users and distributions. Version 2.0.15 is the fifteenth maintenance update in the 2.0 series, continuing the project’s stable improvement of features and expanded device support. Over time, fwupd has regularly added compatibility for more peripherals and system components to simplify firmware maintenance on Linux.
Did you know?
The release of fwupd is coordinated by Richard Hughes, a long-time maintainer of LVFS and the Linux firmware update stack, and a Red Hat engineer.
Technical Details
LVFS (Linux Vendor Firmware Service):LVFS is the service around which fwupd is built, allowing hardware vendors to publish signed firmware updates that Linux users can install through a consistent, distribution-friendly workflow.
Device Support:The addition of support for specific devices (e.g., ConnectX-6/7/8 network cards, Foxconn SDX61 modems, Jabra Evolve2) enables fwupd to identify, verify, and apply vendor-provided firmware updates on these peripherals.
Quick Q&A
What new devices does fwupd 2.0.15 support?NVIDIA ConnectX-6/7/8 network cards, Foxconn SDX61 modems, and Jabra Evolve2 headsets are the newly supported devices.
Who announced the release of fwupd 2.0.15?Richard Hughes from Red Hat announced the availability of fwupd 2.0.15.
What is the foundational service for delivering firmware updates via fwupd?Fwupd is built around the Linux Vendor Firmware Service (LVFS).
Hyprland 0.51 Introduces Configurable Touchpad Gestures
Hyprland, a dynamic tiling Wayland compositor, has released version 0.51, featuring a redesigned gesture system, fully configurable touchpad gestures, and new animations.
This update also brings new configuration options, smoother animations, and numerous fixes aimed at optimizing the Linux desktop experience.
Historical Background
The Wayland compositor implements the modern Wayland display protocol and handles window management and input on the Linux desktop, a role historically filled by X11 window managers. Hyprland is described as an independent, highly customizable dynamic tiling Wayland compositor, reflecting the broader community push for flexible, scriptable desktops on Wayland. This context helps explain the emphasis on gesture and animation configurability in recent releases.
Did you know?
Hyprland is described as an independent, highly customizable dynamic tiling Wayland compositor suitable for GNU/Linux distributions.
Technical Details
Wayland Compositor:A Wayland compositor is a core component that draws windows and manages input according to the Wayland protocol; Hyprland provides this functionality for the Linux desktop.
Configurable Touchpad Gestures:Hyprland 0.51 supports fully configurable touchpad gestures, allowing users to adjust gesture behavior according to their workflows, built on a redesigned gesture system.
Animation Pipeline:This update adds new animations and makes existing transitions smoother, aimed at providing more refined visual feedback during window management.
Quick Q&A
What are the main changes in Hyprland 0.51?It introduces a redesigned gesture system, fully configurable touchpad gestures, new animations, smoother animations, new configuration options, and numerous fixes.
Is 0.51 primarily a bug-fix release?No — Phoronix describes it as a feature release with an improved gesture system and new animations, along with new options and fixes.
Ubuntu 25.10 Sets Dracut as Default Initramfs
After a feature freeze exception, the daily build of Ubuntu 25.10 now uses Dracut as the default initramfs generator, replacing initramfs-tools.
Initramfs-tools has been the default tool for Ubuntu for nearly two decades, and this switch aims to provide a more modular and maintainable boot process, better supporting modern hardware and systemd integration.
Existing installations can continue using initramfs-tools, aiding Ubuntu in preparing for the 26.04 LTS cycle.
Historical Background
For nearly 20 years, Ubuntu has relied on initramfs-tools, a shell script-based generator for building early boot environments. In contrast, Dracut’s modular approach has long been the standard for Fedora and Red Hat Enterprise Linux, and Ubuntu is now adopting this model. As part of a broader modernization effort, Ubuntu 25.10 will also include Linux kernel 6.17 and remove X11 in favor of Wayland, simplifying the components around the boot and display stack.
Did you know?
Ubuntu 25.10 will include Linux kernel 6.17.
Technical Details
Initramfs:The initial RAM filesystem is a small temporary root filesystem loaded into memory at boot to provide the drivers and tools needed to mount the real root filesystem.
Dracut Modular Design:Dracut builds initramfs from modules, including only the necessary drivers and utilities, simplifying updates and improving maintainability.
Systemd Integration:Dracut is tightly integrated with systemd to provide a more consistent boot sequence across different hardware and configurations.
Quick Q&A
Will existing Ubuntu systems be forced to switch to Dracut?No; existing users can continue using initramfs-tools, while new installations in 25.10 will default to Dracut.
Why did Ubuntu choose Dracut over initramfs-tools?Because of its modular design, active upstream support, and systemd integration, aimed at reducing boot complexity and improving maintainability.
How does this change relate to Ubuntu 26.04 LTS?Ubuntu is making this switch in 25.10 to gather real-world feedback and refine the approach before the next LTS release.
KDE Releases Alpha Version of KDE Linux for Testing
The KDE project released the alpha version of its internal “KDE Linux” distribution during the 2025 Akademy conference, making it publicly available for testing and download.
This distribution showcases the latest development of the KDE Plasma desktop and applications, with the project noting that as an alpha version, it has rough edges and missing features.
Linux Magazine emphasizes that it is not yet ready for production use.
KDE’s long-term goal is to develop an operating system suitable for home, enterprise, and OEM installations.
Event Timeline
❶ Akademy 2025 KDE released the KDE Linux alpha version during the 2025 Akademy conference.
❷ September 6, 2025 The alpha version was released for public testing and download.
❸ September 10, 2025 Reviews indicate that KDE Linux and FreeBSD have reached the alpha stage; Pop!_OS is reportedly close to beta.
Did you know?
KDE states that it ultimately hopes KDE Linux will be suitable for OEM installations — although it is still in the alpha stage.
Technical Details
Alpha Version:An early build intended for testing and feedback; features are incomplete, and stability issues are expected.
Internal Distribution:A Linux distribution built by the KDE project itself, aimed at showcasing cutting-edge Plasma and applications, and demonstrating the team’s preferred system integration.
Quick Q&A
What is KDE Linux intended to showcase?It aims to showcase the latest development of the KDE Plasma desktop and KDE applications.
Is the alpha version recommended for daily use?No — reports indicate rough edges and missing features, and Linux Magazine warns that it is not yet ready for production use.
Where can testers obtain the alpha version?The alpha version is now available for public testing and download via the project announcement link.
PipeWire 1.4.8 Improves FireWire Latency and HomePod Mini Support
PipeWire 1.4.8 was released on September 11, 2025, bringing low-latency support for FireWire audio devices using ALSA drivers, improved compatibility with Apple HomePod Mini speakers, enhanced JACK-related features, and fixing multiple bugs as part of the maintenance work for the 1.4 series of Linux audio/video processing.
Historical Background
PipeWire was introduced to unify Linux multimedia, bridging desktop audio (traditionally PulseAudio) and professional audio needs (JACK), while also handling video graphics processing. ALSA is the primary sound subsystem of the Linux kernel, and many traditional but still popular professional interfaces connect via FireWire (IEEE 1394). Improving latency for FireWire devices supported by ALSA helps musicians and audio engineers achieve responsive monitoring and recording on Linux.
Did you know?
Phoronix describes PipeWire as an “increasingly critical” component of the Linux desktop for managing audio and video streams.
Technical Details
Low-Latency FireWire via ALSA:PipeWire 1.4.8 adds low-latency processing for FireWire audio devices using ALSA drivers, reducing round-trip latency critical for real-time audio work.
HomePod Mini Compatibility:This update improves interoperability with Apple HomePod Mini speakers, making it easier for Linux systems to route audio to these devices.
JACK Improvements:Enhancements to JACK in this version benefit users relying on JACK-aware applications and routing, aiding PipeWire’s low-latency audio workflow.
Quick Q&A
Which devices gained new low-latency support in 1.4.8?FireWire audio devices using ALSA drivers gained low-latency operation in this version.
Which smart speaker has improved compatibility?Apple’s HomePod Mini has improved compatibility under PipeWire 1.4.8.
Is 1.4.8 a feature release or a maintenance update?It is described as a maintenance update in the 1.4 series, containing various fixes and incremental improvements.
System76 Completes COSMIC Initial Setup Milestone
LinuxToday reports that System76’s COSMIC desktop has completed its initial setup phase, bringing it closer to a stable release.
Additionally, a commenter noted that they have switched their daily-use Linux desktop to the COSMIC alpha version and have “no regrets.”
Technical Details
Initial Setup:The initial setup typically refers to the first-run experience for configuring accounts, appearance, and default settings; COSMIC’s initial setup is now complete, marking it ready for broader testing.
Alpha Version:An alpha version is an early pre-release version intended for testing and feedback, which may contain bugs; commenters specifically noted using the COSMIC alpha version for daily use.
Quick Q&A
What specific milestone has COSMIC reached?It has completed the initial setup phase, a key step toward a stable release.
Is COSMIC ready for production use?It is still in the alpha stage; however, one commenter reported successfully using the alpha version for daily use.
Ubuntu Details Dependency Risks; Linux Today Update List
Linux Today released its August 2025 recommended free and open-source software updates, noting a stable number of reviews while focusing more on hardware evaluations.
Canonical’s Ubuntu blog explains what software dependencies are, distinguishing between direct dependencies and transitive dependencies, and emphasizes that ensuring software supply chain security requires active management of these dependencies and associated risks.
The blog also cites research indicating that approximately 97% of codebases contain open-source components.
Technical Details
Direct Dependencies:Libraries explicitly declared by a project, typically critical to its functionality; managing these is the starting point for secure builds.
Transitive Dependencies:Dependencies introduced by your direct dependencies; these are not explicitly declared but may introduce hidden vulnerabilities, complicating vulnerability management.
Software Supply Chain Security:The practice of ensuring that software and its dependencies can be used safely by identifying, tracking, and addressing risks across all components.
Quick Q&A
What are transitive dependencies?They are dependencies required by your direct dependencies and are not explicitly declared in your project.
Why is dependency management associated with supply chain security?Because ensuring software supply chain security means ensuring that dependencies can be used safely and managing the security risks they introduce.
What are the highlights of Linux Today’s August updates?While this month focused more on hardware evaluations, it maintained a stable number of software reviews.
Static Workspace Background Extension Stops Wallpaper Movement
A GNOME Shell extension called “Static Workspace Background” keeps the wallpaper fixed during workspace switching, addressing a distracting wallpaper movement issue noticed by some users when switching workspaces.
Did you know?
The Static Workspace Background extension only targets the workspace switching animation, not your wallpaper settings themselves.
Technical Details
Workspace Transition Animation:GNOME workspaces allow you to organize applications and windows across different screens; by default, the wallpaper moves during transitions — this extension keeps it static for a more stable visual effect.
GNOME Shell Extensions:Extensions are add-ons that adjust GNOME Shell behavior without patching core code; Static Workspace Background is such an extension focused on wallpaper during workspace transitions.
Quick Q&A
What issue does the Static Workspace Background address?It prevents the wallpaper from moving when switching workspaces in GNOME Shell, reducing visual distraction during transitions.
Does this change the login screen background?No; it affects workspace transitions within the session, not the GDM login screen background.
Where can I learn more or get the extension?You can read an overview and find links to the Static Workspace Background through OMG! Ubuntu’s coverage.
Puppy Linux Releases BookwormPup64 10.0.12 Based on Debian 12.12 “Bookworm”
Puppy Linux has released BookwormPup64 10.0.12, a lightweight distribution based on the Debian 12.12 “Bookworm” repository.
It maintains the characteristics of being small, fast, and customizable, optimized to support both new and old computers.
The new version is now available for download.
Event Timeline
❶ September 10, 2025 Tuxmachines reported the release of BookwormPup64 10.0.12.
❷ September 2025 9to5Linux reported that BookwormPup64 10.0.12 is based on Debian 12.12 “Bookworm” and is available for download.
Historical Background
Puppy Linux is a long-running lightweight Linux distribution known for its low resource usage and efficient operation on older hardware (often running from RAM). Debian’s “Bookworm” (version 12) has been the stable version of Debian since 2023, and BookwormPup builds from these repositories to provide a Puppy-style Debian experience.
Did you know?
Debian’s release codenames are derived from characters in “Toy Story,” and “Bookworm” inspired the naming convention for this Puppy Linux version.
Technical Details
Debian Repository:BookwormPup64 10.0.12 pulls packages from the Debian 12.12 “Bookworm” repository, providing access to Debian’s stable software catalog while retaining Puppy’s lightweight tools.
Lightweight Distribution:Lightweight distributions aim for small size, fast performance, and moderate memory/storage requirements, helping older PCs run smoothly while keeping modern systems responsive.
Hardware Compatibility:This version is tuned to support both legacy and current hardware, expanding its availability across various PCs.
Quick Q&A
What base does BookwormPup64 10.0.12 use?It is based on the Debian 12.12 “Bookworm” repository.
Who is this version suitable for?It is optimized to support both new and old computers, appealing to users with aging PCs and modern hardware.
Can I download it now?Yes, the BookwormPup64 10.0.12 ISO is available for download.
OpenSUSE Disables bcachefs in Kernel 6.17+
openSUSE will disable the bcachefs filesystem in its Linux kernel builds starting from version 6.17, while the current 6.16.* series and Slowroll are temporarily unaffected.
Linus Torvalds recently marked bcachefs as “externally maintained,” pausing new upstream merges while retaining existing in-tree code.
LWN notes that openSUSE bcachefs users will “have to make other arrangements” after 6.16.
Event Timeline
❶ Recent (prior to openSUSE decision) Linus Torvalds marked bcachefs as “externally maintained” and paused new merges while retaining existing code in-tree.
❷ Kernel 6.17 and newer openSUSE disables the bcachefs filesystem in its kernel builds.
❸ Current releases openSUSE kernel 6.16.* and Slowroll are temporarily unaffected.
Historical Background
Bcachefs was introduced as an experimental copy-on-write (CoW) filesystem in the mainline kernel, indicating its ongoing maturation but also raising caution among distributions. Recently, Linus Torvalds marked the subsystem as “externally maintained,” pausing new merges while retaining existing bcachefs code. In light of this, openSUSE announced it would disable the driver starting from kernel 6.17, with LWN noting that users will need alternatives after upgrading from 6.16.
Did you know?
Despite the pause on new merges, upstream bcachefs code remains available in the kernel tree, allowing existing setup users to continue operating while decisions evolve.
Technical Details
Copy-on-Write (CoW) Filesystem:Bcachefs is described as an experimental CoW filesystem, meaning it writes new data to new locations before updating metadata, aiding snapshots and integrity but at the cost of increased complexity.
Externally Maintained Status:Torvalds’ “externally maintained” designation indicates that no new changes will be merged into the mainline for the time being, although existing bcachefs code remains in the kernel tree, affecting distribution enablement decisions.
Quick Q&A
Which openSUSE kernel versions have disabled bcachefs?openSUSE disables bcachefs in Linux 6.17+ builds; 6.16.* remains unaffected.
Has bcachefs been removed from the upstream Linux kernel?No; the code remains in the tree, but new bcachefs changes will not be merged after being marked as “externally maintained.”
What should openSUSE bcachefs users do next?They should temporarily stay on 6.16.* or Slowroll, or plan alternatives when migrating to 6.17+, as users will need to make other arrangements.