News : Linus Torvalds fixes critical Linux kernel bug using AI-assisted debugging.

Linus Torvalds resolved a critical memory corruption bug in the Intel Xe driver for Battlemage G21 by combining traditional kernel debugging with AI-assisted instrumentation.

The issue caused black screen failures during boot on systems using the Battlemage G21 GPU, making the bug difficult to reproduce and trace manually.

Torvalds began by isolating the problematic code path inside the Xe driver, focusing on memory handling routines that interacted with the Battlemage G21 hardware.

To accelerate the debugging process, he used AI to automatically generate instrumentation code that logged internal driver states during each boot attempt.

The AI-generated instrumentation allowed Torvalds to capture detailed memory access patterns and identify the exact moment where corruption occurred.

He performed eighteen kernel boots with different instrumentation patches, gradually narrowing down the faulty memory operation.

After collecting enough diagnostic data, Torvalds confirmed that a specific memory write operation inside the Xe driver was overwriting GPU state buffers.

He created a series of twenty-four patches that corrected the memory handling logic, added safety checks, and improved buffer validation for Battlemage G21.

The final patch was reviewed, refined, and integrated into the Linux kernel, ensuring stable boot behavior for systems using Intel’s Battlemage GPUs.

This debugging session demonstrated how AI tools can assist kernel developers by generating targeted instrumentation and reducing the time required to diagnose complex hardware-related bugs.

The fix is now part of the Linux 7.2 kernel release, improving stability and compatibility for Intel’s next-generation Battlemage graphics hardware.

News : Fedora Releases Critical Fixes for Python 3.10, 3.11, 3.13 and 3.14.

Fedora has been highly active this week in the Python security ecosystem, releasing critical updates for Python 3.10, 3.11, 3.13, and 3.14 across multiple Fedora branches.

These updates address several high‑impact vulnerabilities, including Denial of Service issues in the HTML parser, XML parsing flaws, tarfile extraction bypasses, and multiple injection vectors affecting different Python modules.

The Python 3.10.21 update for Fedora 43 resolves code injection risks, HTTP header injection problems, XML stack overflow vulnerabilities, and a webbrowser.open security flaw that could be exploited in specific environments.

Fedora 44 received the Python 3.11.16 update, which patches critical Expat vulnerabilities, unicodedata issues, and HTML parser weaknesses that could lead to CPU exhaustion or unexpected crashes.

Python 3.13.15 was also updated in Fedora 43, fixing a tarfile directory traversal bypass and a CPU‑intensive HTML parsing bug that could degrade system performance under crafted input.

Fedora additionally pushed the Python 3.14.7 update, addressing similar HTML parser vulnerabilities and reinforcing security around tarfile extraction to prevent unauthorized file writes outside the intended directory.

These coordinated updates highlight Fedora’s commitment to rapid security response, especially in the Python ecosystem, which is widely used across system tools, automation scripts, cloud workloads, and developer environments.

By delivering synchronized patches for multiple Python branches, Fedora ensures that users running different versions of the distribution remain protected against known exploits and performance‑impacting vulnerabilities.

This week’s activity demonstrates Fedora’s strong focus on maintaining a secure and reliable Python environment, reinforcing its position as one of the most proactive Linux distributions in vulnerability management.

News : Fedora 45 beta.

Fedora 45 enters the Beta Freeze stage, marking the transition from active feature development to strict system stabilization in the Fedora release cycle.

This phase ensures that Fedora 45 maintains a consistent, predictable, and reproducible state while developers and testers focus on reliability and performance across all supported architectures.

The Fedora development workflow begins with Rawhide, the fast-moving branch where new packages land daily and experimental changes are introduced.

From Rawhide, the Fedora 45 branch is created, forming the foundation for the upcoming release and preparing the system for the Alpha milestone.

The Alpha stage integrates major components such as the Linux kernel, Mesa graphics stack, systemd, Python, GCC, and Clang, allowing early testing of core functionality.

After Alpha, Fedora 45 progresses into the Beta stage, where the distribution becomes feature-complete and ready for broad community testing on laptops, workstations, and servers.

During Beta, the focus shifts to hardware compatibility, upgrade validation, installer testing, and regression detection in critical subsystems like Wayland, PipeWire, SELinux, and DNF5.

With the start of Beta Freeze, all major updates are blocked from entering the stable repositories, preventing disruptive changes and ensuring a stable Beta image.

Every update must pass through Bodhi updates-testing, where automated gating tests and community karma feedback determine whether a package is safe to include.

This controlled process helps maintain system integrity and prevents regressions caused by rapid adoption of new compiler versions such as GCC 14 and Clang 18.

Nightly builds during Beta Freeze include only approved patches, including fixes in Anaconda, Pungi, and python-blivet that improve partition handling, image composition, and installer reliability.

Fedora 45 benefits from updated Mesa drivers, a newer Linux kernel, refreshed system libraries, and improvements across GNOME, KDE Plasma, and LXQt environments.

For users, the Beta stage is when Fedora 45 becomes stable enough for daily use and real-world testing, with reported issues directly influencing the final release quality.

For developers, Beta Freeze shifts the focus from adding features to refining package consistency, resolving dependencies, and eliminating incompatibilities across the ecosystem.

Fedora 45 continues the project’s tradition of delivering a modern, forward-looking Linux distribution, and the structured progression through Rawhide, Alpha, Beta, and Beta Freeze ensures a stable and high-quality final release.

News : Darktable 5.6.1: Stability, GPU fixes and AI improvements for Fedora and other Linux distributions.

Darktable 5.6.1 was released on August 27, 2026, with a technical focus on improving stability, memory handling, and GPU compatibility specifically on Fedora and other Linux distributions that adopt cutting‑edge toolchains and graphics stacks.

Fedora users benefit from native Wayland support in the official AppImage, allowing Darktable to run directly on GNOME’s Wayland session without relying on XWayland, while still providing automatic fallback to X11 for systems with incomplete OpenCL or Vulkan implementations.

The update addresses AMD GPU issues encountered frequently on Fedora due to Mesa Rusticl, eliminating pixel corruption and reducing OpenCL buffer allocation failures that previously caused crashes in modules such as denoise, sharpen, and tone equalizer.

Darktable 5.6.1 improves the RAW processing pipeline by enhancing ONNX model handling, adding automatic retry for interrupted downloads, and ensuring full metadata preservation for AI‑generated images, including EXIF, geotags, ratings, and color labels.

The AI RAW denoise module now rejects Fujifilm Super CCD sensors explicitly, preventing incorrect processing results caused by unsupported training data and ensuring predictable behavior across Fedora’s diverse camera workflows.

Multiple stability issues in wavelet decomposition, path masks, and raster masks are resolved, addressing crash patterns that were more visible on Fedora due to its early adoption of GCC 14 and Clang 18, whose aggressive optimizations exposed subtle bugs in previous Darktable builds.

Export reliability is improved through corrections in JPEG 2000 YCbCr 4:2:0 decoding and PNG 16‑bit color handling, fixing inconsistencies triggered by Fedora’s up‑to‑date libpng and openjpeg libraries.

On macOS, Darktable 5.6.1 provides separate builds for x86_64 and ARM64, ensuring optimized performance on Apple Silicon devices through improved integration with Metal and OpenCL layers, although the primary technical impact of this release remains centered on Linux and Fedora.

The update reduces crash frequency on macOS when applying 3D LUTs or running AI modules, thanks to adjustments aligned with recent Apple Clang and SDK changes, maintaining parity with Fedora’s stability improvements.

Windows users receive a fix for AMD OpenCL devices that were previously disabled, restoring full GPU acceleration, but Fedora remains the distribution with the most significant improvements due to its modern graphics stack and rapid package updates.

Package distribution for Linux is updated through OBS, PPA, Flatpak, and Fedora’s community repositories, ensuring that Fedora users receive the latest Darktable 5.6.1 builds compiled against current system libraries and toolchains.

News : Lightning Talk: GNOME Shell Design Dreams | Tobias Bernard & Jakub Steiner @ GUADEC 2026

Fedora : Fedora SilverBlue 44 on VirtualBox 7.2.10 - Lazarus I.D.E. video tutorial.

Fedora : testing basic example with python SELinux package.

Fedora : Fedora SilverBlue 44 and distrobox tool.

Distrobox on Fedora is a lightweight, rootless way to run any Linux distribution inside a tightly‑integrated container, powered by Podman. It’s more flexible than Fedora’s native Toolbox because it can pull any OCI image (Ubuntu, Arch, Debian, openSUSE, Alpine, etc.)

What Distrobox Does on Fedora

• Runs any distro inside your terminal using Podman or Docker.
• Integrates with the host: shared $HOME, USB devices, audio, GUI apps (X11/Wayland).
• No root needed — perfect for immutable Fedora variants like Silverblue/Kinoite.
• Exports apps from the container back to Fedora using distrobox-export.

Install Distrobox on Silverblue

rpm-ostree install distrobox
systemctl reboot

Create and enter a Gentoo container

distrobox create -i gentoo/stage3:latest -n gentoo
distrobox enter gentoo

Sync and update Gentoo

emerge --sync
emerge --ask --update --deep --newuse @world
...

Gentoo inside Distrobox is source‑based, this means:

Compiling packages happens inside the container

CPU and RAM usage will be high

Builds may take a long time (depending on your hardware)

Silverblue’s immutability does not affect Gentoo’s compilation.

Fedora : Fedora SilverBlue 44 on VirtualBox 7.2.10 - first commands to start .

Fedora Silverblue is an immutable desktop operating system built on top of rpm‑ostree. Instead of traditional package-based upgrades, Silverblue uses atomic deployments, making the system extremely stable, reliable, and easy to roll back. This blog-style guide shows you how to update your system, manage deployments, upgrade to new Fedora versions, and keep Flatpak applications current — all using simple terminal commands. Tested on VirtualBox.

Check your current system state

Before updating, it is useful to inspect your current deployment and any layered packages.

rpm-ostree status

Most apps in Silverblue come from Flatpak.

sudo su
flatpak update

Perform a standard system update

This updates your Silverblue installation to the latest available deployment for your current Fedora release.

sudo rpm-ostree upgrade
systemctl reboot

Clean up old deployments

Silverblue keeps multiple system deployments so you can roll back if needed. You can safely clean older ones to free space and reduce clutter.

rpm-ostree status
sudo rpm-ostree cleanup -p
sudo rpm-ostree cleanup -m

Roll back if something breaks

If an update causes issues, you can revert to the previous deployment quickly and safely.

rpm-ostree status
sudo rpm-ostree rollback
systemctl reboot

Rebase to a new Fedora Silverblue version

Major upgrades are done via rebase. Replace 41 with your target Fedora version. I used Fedora 44 and I keep that version.

rpm-ostree status
sudo rpm-ostree rebase fedora:fedora/41/x86_64/silverblue
systemctl reboot

Manage layered RPM packages

Although Silverblue is immutable, you can still layer RPM packages on top of the base image. Here is how to inspect and remove them.

rpm-ostree status
sudo rpm-ostree uninstall package-name
systemctl reboot

Troubleshooting tips

If updates fail or downloads hang, you can refresh metadata or inspect rpm-ostree logs.

sudo rpm-ostree refresh-md
journalctl -u rpm-ostreed

News : start translation updates was due to the migration on Fedora

Updates to translations of Fedora Documentation are again available. As announced on March 3rd, the unavailability of translation updates was due to the migration of the translation repositories and necessary tools from Pagure to the Fedora Forge. It took longer than expected but we are pleased to report this undertaking came finally to the end.

See the official website.

News : COSMIC Desktop 1.1 - System76.

System76 has released COSMIC Desktop 1.1, the latest update to its Rust-based desktop environment for Pop!_OS and other Linux distributions.

See the official website - system76.

Fedora : Fedora SilverBlue 44 on VirtualBox 7.2.10 - fast video tutorial.

Fedora immutable : Immutable Linux distributions and their development by the Fedora team.

What Are Immutable Linux Versions?

• Immutable Linux distributions are operating systems where the core system is read-only and cannot be modified directly by the user.
• Examples include Fedora Silverblue (GNOME-based) and Fedora Kinoite (KDE Plasma-based) ...
• The system is built from atomic images, similar to how mobile operating systems update.
• Applications and development tools run in containers instead of modifying the base system.

Main Characteristics and Functionality

• The base system is read-only, preventing accidental or harmful changes.
• Updates are atomic: the entire system updates as one unit and can be rolled back instantly.
• Applications are installed through Flatpak or container environments like Toolbox and Distrobox.
• System integrity is preserved because the OS image remains consistent across reboots.

Security Features

• The read-only system reduces the attack surface by preventing unauthorized modifications.
• Atomic updates ensure that incomplete or corrupted updates do not break the system.
• Containerized applications isolate software from the core system, improving security.
• Rollback capability allows users to revert to a previous working state after a failed update.

Hardware and Software Limitations

• Some proprietary drivers may require manual workarounds because the base system cannot be modified directly.
• Legacy hardware may not be fully supported due to the modern design of immutable systems.
• Traditional package managers like dnf or apt cannot install software into the base system.
• Advanced system customization is limited because configuration files are protected.

Advantages

• High stability due to the read-only system design.
• Fast and reliable updates with rollback support.
• Improved security through isolation and immutability.
• Ideal for developers using container-based workflows.
• Consistent system state across reboots and installations.

Disadvantages

• Less flexibility for users who want to modify system internals.
• Some software may not work if it requires direct system-level installation.
• Learning curve for users unfamiliar with Flatpak or container tools.
• Not ideal for niche hardware requiring custom drivers.

Immutable Fedora Linux Versions: Silverblue and Kinoite

What Are Immutable Linux Versions?

• Immutable Linux distributions are operating systems where the core system is read-only and cannot be modified directly by the user.
• Examples include Fedora Silverblue (GNOME-based) and Fedora Kinoite (KDE Plasma-based).
• The system is built from atomic images, similar to how mobile operating systems update.
• Applications and development tools run in containers instead of modifying the base system.

Main Characteristics and Functionality

• The base system is read-only, preventing accidental or harmful changes.
• Updates are atomic: the entire system updates as one unit and can be rolled back instantly.
• Applications are installed through Flatpak or container environments like Toolbox and Distrobox.
• System integrity is preserved because the OS image remains consistent across reboots.

Security Features

• The read-only system reduces the attack surface by preventing unauthorized modifications.
• Atomic updates ensure that incomplete or corrupted updates do not break the system.
• Containerized applications isolate software from the core system, improving security.
• Rollback capability allows users to revert to a previous working state after a failed update.

Hardware and Software Limitations

• Some proprietary drivers may require manual workarounds because the base system cannot be modified directly.
• Legacy hardware may not be fully supported due to the modern design of immutable systems.
• Traditional package managers like dnf or apt cannot install software into the base system.
• Advanced system customization is limited because configuration files are protected.

Advantages

• High stability due to the read-only system design.
• Fast and reliable updates with rollback support.
• Improved security through isolation and immutability.
• Ideal for developers using container-based workflows.
• Consistent system state across reboots and installations.

Disadvantages

• Less flexibility for users who want to modify system internals.
• Some software may not work if it requires direct system-level installation.
• Learning curve for users unfamiliar with Flatpak or container tools.
• Not ideal for niche hardware requiring custom drivers.

Why Fedora Atomic Desktop Versions Lag Behind Workstation

Fedora Atomic Desktops (immutable editions - 40) do not follow the same release pace as Fedora Workstation 44 – April 2026. While Workstation receives a new version every six months, the immutable editions often remain several versions behind. This happens because immutable systems require additional testing, image validation, and stability checks before release.

Main Reasons for Version Differences

• Immutable systems use rpm-ostree, which requires more complex testing than traditional package-based systems.
• Atomic updates and rollback functionality must be verified for every release.
• Desktop environments must be adapted to work correctly in a read-only system.
• The Fedora Atomic team is smaller and focuses on stability over rapid version progression.
• New immutable editions (Onyx, Aurora, Sericea) increased development workload.

Current Immutable Editions

• Fedora Silverblue (immutable, GNOME)
• Fedora Kinoite (immutable, KDE Plasma)
• Fedora Sericea (immutable, Sway)
• Fedora Onyx (immutable, Budgie)
• Fedora Aurora (immutable, LXQt)

Release Timeline for Immutable Editions

• Fedora releases occur twice per year: April and October.
• Workstation versions advance regularly (e.g., Fedora 44 in 2026).
• Immutable editions often remain at older versions (e.g., Silverblue 40) until stability is guaranteed.
• Development for immutable editions happens first in Rawhide, then moves to a stable branch.
• Version numbers for immutable editions may skip or delay compared to Workstation.

Development

• Atomic Rawhide (future Fedora 41 Atomic)
• Rawhide is the testing ground for all new immutable features.
• New images are built and validated before becoming a stable release.

How Development Works for Immutable Fedora

• All new changes are introduced in Rawhide, the rolling development branch.
• The system is built as an OSTree image instead of traditional packages.
• Each image must pass atomic update and rollback validation.
• Flatpak integration and container tools (Toolbox, Distrobox) must be tested for compatibility.
• Only after stability is confirmed, the immutable edition receives a new version number.

Why Immutable Editions Prioritize Stability

• Atomic systems must guarantee that updates never break the OS.
• Rollback must work flawlessly for every release.
• Desktop environments must behave correctly in a read-only environment.
• Consistency and reliability are more important than rapid version progression.