/rss20.xml">

Fedora People

Updates and reboots on Fedora infrastructure

Posted by Fedora Infrastructure Status on 2026-11-19 22:00:00 UTC

Fedora Infrastructure team will be applying updates to servers and rebooting them.

Many services will be affected, most should only be down for a short time as their particular resources are rebooted HOWEVER some will be upgraded to F45 from earlier releases and may take a bit longer.

Login issues with Forge & Bodhi

Posted by Fedora Infrastructure Status on 2026-11-17 10:00:00 UTC

Update: Now resolved, there was a configuration issue with our OIDC setup.

We are aware of an issue logging into the Forge & Bodhi. We are investigating.

Since the Forge is down, please log issues in #admin:fedoraproject.org for now.

From November 09 to November 15

Posted by Aurélien Bompard on 2026-11-16 09:51:00 UTC

Across the various Fedora working groups, a major focus this week was the transition between release cycles, heavily featuring post-release cleanup and monitoring for Fedora 45 alongside active planning for Fedora 46, including proposals like the removal of the legacy DNF4 stack. Infrastructure and tooling migrations were another prominent shared theme; multiple teams—including Docs and Gaming—are migrating references from Pagure and GitLab to Fedora Forge, while the Council and FESCo are actively investigating Forgejo-based replacements for the retiring Bugzilla issue tracker. Security and system maintenance also drove significant cross-team collaboration, highlighted by a coordinated infrastructure outage for server updates, the removal of inactive packagers, and widespread vulnerability patching in the Rust and CoreOS groups. Finally, community engagement teams like Mindshare and Ambassadors are aligning their efforts to finalize proposals, funding, and volunteer coordination for major upcoming open-source conferences, particularly FOSDEM 2027 and FOSSASIA 2027.

Announcements

Contributors should be aware of a planned infrastructure outage scheduled for November 19, 2026, at 22:00 UTC, which will last approximately four hours to accommodate server updates and reboots. Additionally, as part of routine maintenance for the Fedora 45 development cycle, 161 users are being removed from the packagers group due to inactivity. For those looking to get more involved, the latest Fedora Podcast (Episode 064) not only discusses the recent Fedora 45 release but also highlights several upcoming engagement opportunities for Fedora 46, including writing release notes, participating in test weeks, and submitting wallpaper ideas.

In broader community news, two new guides have been published to help users enhance their desktop experience. The first outlines a method to install the official Claude Desktop Linux beta on Fedora, utilizing a script to safely extract and run Anthropic's .deb package without root privileges. The second introduces TuxTalk, a free, locally-hosted voice dictation tool for Linux that allows users to dictate text directly into any application, terminal, or document without requiring an account or sending voice data off-device.

Council

This week, the Council addressed trademark usage for a new Fedora-derived distribution called Bibim, clarifying that the Fedora Remix logo is the intended branding for such projects, which led the creators to adopt the Remix guidelines instead of seeking a trademark variance (Trademark question: using the Fedora logo for a Fedora-derived distribution (Bibim)). Additionally, a significant community discussion began regarding the future of Fedora's issue tracking system in light of the upcoming retirement of Red Hat's hosted Bugzilla, with members debating the transition to a Forgejo-based system versus maintaining a community Bugzilla instance (What issue tracker do we want to use for Fedora 90?).

Contribution opportunities

  • Contribute to creating a script or packaging solution that simplifies converting a standard Fedora release into a Fedora Remix.
  • Help design a specific landing page for Fedora Remix users to encourage upstream contributions.
  • Submit concrete proposals, gather requirements, or write user stories for Fedora's future issue tracking system transition.

Learn more about the Council team.

FESCo

This week, FESCo held one meeting and processed numerous tickets, primarily focusing on approving System-Wide and Self-Contained Changes for upcoming Fedora releases. Key discussions centered around the ongoing investigation into replacing Bugzilla, managing the removal of unmaintained NetworkManager VPN plugins, and extending the F45 FESCo election voting period to accommodate the holidays. FESCo also formally set the EOL date for Fedora 43.

Decisions

  • The Fedora 43 End of Life was officially set to 2026-12-02.
  • Ticket #3703: Approved the change to move the distribution to the RPM v6 package format.
  • Ticket #3693: Approved removing NetworkManager-{vpnc,fortisslvpn} from F44 Atomic Desktops, but rejected adding obsoletes in F44.
  • Ticket #3708: Agreed to extend the FESCo election voting period to January 5th, leaving the nominations period as is.
  • Ticket #3705: Approved a permanent updates policy exception for media processing libraries (live555 and openapv).
  • Ticket #3706: Approved a one-time F45 Updates Policy Exception for python-openai.
  • Ticket #3701: Approved the LMDB 1.0 Transition.
  • Ticket #3700: Approved changing the Libvirt Network Filter default firewall backend to NFTables.
  • Ticket #3699: Approved the Libchewing 0.14 update.
  • Ticket #3698: Approved the Emacs Package Packaging change.
  • Ticket #3697: Transferred ownership of python-authlib to a new co-maintainer under the non-responsive maintainer policy.

Contribution opportunities

  • Julita Inca requested a mentor to help them start contributing to Ansible testing in Fedora (Meeting Log).
  • Feedback is requested on the draft policy for global CI tests (Ticket #3683).
  • Community members are invited to test and provide feedback on the ongoing Bugzilla replacement investigation and staging instances (Ticket #3664).

Learn more about the FESCo team.

Packaging Committee

The Packaging Committee focused this week on updating the Emacs packaging guidelines to support the built-in package management system in recent versions of GNU Emacs. This includes discussing and merging changes that provide new RPM macros and dependency generators for Emacs packages. Additionally, new tickets were opened to discuss allowing Emacs add-ons in RPM subpackages (Issue 1581) and marking up spec templates as source code (Issue 1582).

Decisions

  • The committee approved and merged PR#1577 (associated with Issue 1577), which introduces new RPM macros and dependency generators for Emacs packages, with plans to resolve minor formatting and Unicode issues post-merge.

Learn more about the Packaging Committee team.

Mindshare

The Mindshare group focused on upcoming conference preparations and deadlines. Reminders were issued for FOSSASIA 2027, noting the November 19 deadline to update the event wiki and November 29 for talk proposals. Additionally, a final call for financial assistance applications for FOSDEM 2027 was made ahead of the November 15 deadline. Community members also briefly connected regarding attendance at SFSCON 2026.

Decisions

  • Future FOSDEM financial assistance requests will transition from using the Wiki to a dedicated application form to better capture budget details and applicant motivations (URL).

Contribution opportunities

  • Update the FOSSASIA 2027 Fedora Project Wiki by November 19, 2026, if you plan to attend.
  • Submit talk or volunteering proposals for FOSSASIA 2027 on their official website by November 29, 2026.
  • Apply for financial assistance to attend FOSDEM 2027 by adding budget request details to the Wiki table by November 15, 2026.

Learn more about the Mindshare team.

Fedora Join

This week, the Fedora Join group received introductions from two new prospective contributors. Fardeen Khan introduced themselves as a developer and Fedora advocate looking for guidance on which teams to join. Lutz Weber also introduced themselves, expressing interest in starting with Quality Assurance (QA) and eventually contributing to the Python SIG and software packaging.

Contribution opportunities

  • Guide Fardeen Khan in finding a suitable team to contribute to, utilizing their development and ethical hacking background.
  • Welcome Lutz Weber and help them get started with the QA team and the Python SIG.

Learn more about the Fedora Join team.

Ambassadors

This week, the Ambassadors group focused on coordinating Fedora's presence at upcoming major open-source conferences. Reminders were issued for approaching deadlines regarding event proposals, talk submissions, and financial assistance requests for both FOSDEM 2027 and FOSSASIA 2027. Furthermore, community members discussed potential informal meetups at the South Tyrol Free Software Conference (SFSCON).

Contribution opportunities

Learn more about the Ambassadors team.

Workstation / GNOME

This week, the Workstation / GNOME group addressed several critical system behavior and packaging issues. Key discussions included a bug in GNOME 51's GDM that disables initial fingerprint login—breaking Fedora's authselect and oo7-daemon workflows—and a Btrfs metadata exhaustion issue prompting calls to reconsider auto-balancing defaults. Additionally, users reported a crash in pdftotext when handling certain PDFs, which has been forwarded upstream.

On the ticketing side, the group successfully completed the replacement of gnome-keyring-daemon with oo7-daemon. Active investigations are ongoing regarding automating appstream-data updates and a dependency resolution bug where removing Firefox via GNOME Software inadvertently changes the system's identity to Budgie.

Decisions

  • The migration to replace gnome-keyring-daemon with oo7-daemon as the default secret service provider was completed and the ticket was closed. (Issue #506)

Contribution opportunities

Learn more about the Workstation / GNOME team.

KDE

This week, the KDE group focused on resolving user-reported issues with recent Plasma updates and discussing future package replacements. Community members actively addressed a shutdown hang bug in Plasma 6.8 by providing unofficial fixes via COPR and pull requests for Qt, while also testing an unofficial build of Plasma 6.8.3. Additionally, discussions clarified the removal of X11 sessions in Fedora 44 and the expected weekly cadence for automated Discover updates on Kinoite. On the development front, new requests for enhancements (RFEs) were filed to replace kwalletmanager with KeepSecret and to remove live-system-only packages during Plasma Setup to save disk space. The ongoing effort to replace kwallet with oo7-daemon was deferred for KDE due to integration challenges.

Decisions

  • The replacement of kwallet with oo7-daemon has been deferred for KDE variants due to integration issues and a lack of time (URL).

Contribution opportunities

  • Test the unofficial COPR for KDE Plasma 6.8.3 on Fedora 44 and 45 and report any issues in the forum thread.
  • Test the Qt 6.11.2 COPR containing the cherry-picked fix for the Plasma 6.8 shutdown hang issue on Fedora 44 and 45 (URL).

Learn more about the KDE team.

Server

The Server working group met this week to discuss ongoing projects and potential changes for the upcoming Fedora 46 release. Key discussions centered around the 'Strengthening Server Updates' project, which was postponed to allow for further testing, and the future of Single Board Computer (SBC) images. Additionally, a community member published a comprehensive and highly successful test report detailing the upgrade path from Fedora 44 Server to the Fedora 45 release on a 2010-era machine, confirming excellent stability with no regressions.

Decisions

  • The working group agreed to evaluate switching the Single Board Computer (SBC) image to GPT/EFI and dropping Raspberry Pi 3 support for Fedora 46. (URL)
  • The group decided to keep NetworkManager for the time being rather than switching to systemd-networkd, citing issues with split DNS on virtual machine hosts and its utility in home lab setups. (URL)
  • Working group members agreed to catch up on outstanding tasks for the Strengthening Server Updates project and revisit the topic on November 25, 2026. (URL)

Contribution opportunities

  • Help is needed to test the procedures for the Strengthening Server Updates project and start a post-installation how-to style article.
  • Contributors with image building experience are invited to assist in evaluating and implementing the switch of the SBC image to GPT/EFI, which involves updating kiwi definitions.

Learn more about the Server team.

Infrastructure

This week, the Infrastructure team focused heavily on resolving service disruptions and preparing for an upcoming mass upgrade. Bodhi experienced significant load and timeouts due to aggressive scrapers, prompting the team to implement mitigations like blocking specific RSS endpoints and deploying a Valkey backend for caching. The team also addressed sporadic 404 errors for jQuery on the Fedora Forge caused by Varnish mis-caching, and resolved IPA replication issues after an OS upgrade on ipa01.

Additionally, a planned outage for mass updates and reboots was scheduled for November 19th, which will involve upgrading several servers to Fedora 45. The team also investigated a sophisticated phishing campaign targeting mailing list administrators and welcomed several new contributors to the group.

Decisions

Contribution opportunities

Learn more about the Infrastructure team.

Release Engineering

The Release Engineering team focused on post-release cleanup for Fedora 45, including resolving an issue with missing torrents for several Labs ISOs that were absent at release time. The team also addressed an out-of-date Fedora 45 COSMIC Atomic reference and handled routine package unretirements and SCM requests, while monitoring and unsticking the package signing service. Additionally, preparations for the Fedora 43 End of Life have begun.

Decisions

  • Fedora 43 End of Life is officially set for December 2, 2026, aligning with FESCo and existing policies (Meeting, Ticket #13588).

Contribution opportunities

Learn more about the Release Engineering team.

Quality

The Quality team monitored the recent release of Fedora 45, noting a smooth rollout with no major regressions, which was corroborated by a detailed community server test on older hardware. The team is now transitioning focus to Fedora 46, reviewing upcoming system-wide changes, and continuing to document common issues for Fedora 45. Additionally, the KDE Plasma 6.8 test days were launched and actively promoted across the community.

Decisions

  • Christopher Boni volunteered to send out the call for upcoming Test Days (Meeting log).
  • Bug 2538553 was published to the Fedora 45 Common Issues, while bugs 2560255 and 2537131 are being held for further investigation before publication (Ticket #952).

Contribution opportunities

  • Participate in the KDE Plasma 6.8 Test Days running from 2026-11-09 to 2026-11-15 by testing and submitting results.
  • Help is requested to investigate a navigation test failure in openQA where os-autoinst fails to recognize screen changes during Tux Racer gameplay (Ticket #954).

Learn more about the Quality team.

Websites and Apps

This week, the Websites and Apps team discussed the future of Fedora Magazine's hosting, prompted by a potential end of WP Engine support by the end of 2027. Conversations explored migrating from WordPress to a static site generator (like Nuxt or Hugo) paired with Decap CMS, or potentially using Discourse as a backend, though challenges remain regarding content conversion and comment integration. In the forums, a user reported that Fedora's wifi login detection domain is on the HSTS preload list, breaking captive portal detection, and suggested using a dedicated, independent domain. Additionally, the team handled a new collaborator request and tracked a deprecation warning for the @comark/nuxt module in the fedora-websites-3.0 repository.

Contribution opportunities

  • Help is needed to explore and draft a strawman proposal for migrating Fedora Magazine off WP Engine to a static site or alternative CMS before the end of 2027.
  • Contributors can assist in resolving the @comark/nuxt module deprecation warning in the fedora-websites-3.0 repository.
  • Feedback and solutions are welcome on the forum discussion regarding the Fedora wifi login detection domain breaking due to HSTS preloading.

Learn more about the Websites and Apps team.

Design

This week, the Design team received a new request to create a "Fedora loves GNOME" sticker for distribution at upcoming conferences such as FOSDEM. Additionally, ongoing work continued on the community involvement poster, with the contributor using AI-generated feedback to identify and resolve typography, spacing, and alignment issues. In the background, several automated repository actions failed in the design/backgrounds repository, and the weekly team meeting appears to have been cancelled.

Contribution opportunities

  • A graphic designer is needed to create a print-ready PDF for a "Fedora loves GNOME" sticker to be distributed at events like FOSDEM.
  • Contributors can help troubleshoot and fix the failing Update README.md automated actions across multiple branches in the design/backgrounds repository.

Learn more about the Design team.

Docs

This week, the Docs team focused heavily on migrating infrastructure references from the sunset Pagure and GitLab to Fedora Forge. This massive cleanup spanned multiple repositories, resulting in updated team documentation, build scripts, templates, and Quick Docs. The migration also resolved a bug in the translated builds by pointing the asciidoc-keywords repository to Forge. Additionally, discussions are underway to establish a Quay organization for hosting the team's CI container images.

In other content updates, the kernel testing patches guide was substantially reworked to use grubby and custom build IDs, making it safer and easier for users to manage test kernels. The team also prepared for Antora 3.2 by fixing malformed navigation entries, and updated the release notes to reflect that oo7 is delayed and not in F45, while adding a new note for Bash Color Prompt 1.0 in F46.

Decisions

  • The 'How to edit files on the Pagure Web UI' guide has been officially retired and replaced with the Fedora Forge guide.
  • The oo7 feature for KDE has been delayed and will not be included in the Fedora 45 Release Notes.
  • The default branch for site-builder and related translation scripts has been officially switched to main, and the legacy prod branch will be deleted (Ticket 77, Ticket 58).
  • The kernel testing guide has been updated to recommend using grubby and custom buildids instead of overwriting existing packages, preventing conflicts with standard Fedora updates (Ticket 1087).

Contribution opportunities

  • Team Decision Needed: Determine the future of the Publish RPMs on Copr Quick Doc, as its example repository was lost in the Pagure sunset.
  • Team Decision Needed: Clarify what permissions the docs-admin and docs FAS groups grant on Forge to update the team charter.
  • Contributor Opportunity: Help perform a full script sync for docsbuilder.sh to update it to the new Forge docs-template script format (Ticket 72).
  • Contributor Opportunity: Assist in replacing the remaining GitLab references with Fedora Forge in the team documentation.
  • Contributor Opportunity: Help replace legacy {partialsdir} includes with partial$ syntax in Quick Docs.

Learn more about the Docs team.

COPR

This week, the COPR team successfully executed a planned infrastructure outage to update machines to the latest packages. The outage was brief, and services were quickly restored. In discussions, the team addressed intermittent Bodhi outages affecting builds and identified an ongoing issue where internal messaging changes at Red Hat have broken the Fedora review bot. Additionally, the team clarified that some group-owned projects that missed the initial Pulp migration will be queried and migrated once the current batch of owners is finished. Maintainers also provided guidance on packaging non-crates.io Rust applications, clarifying the scope of rust2rpm.

Decisions

  • Executed a planned infrastructure update for COPR on November 12, 2026, temporarily halting build queue processing and Frontend/Web-UI task acceptance (Mailing List).
  • Group-owned projects that missed the initial Pulp migration will be migrated in a final sweep after the last batch of individual owners is completed (Matrix Chat).
  • Deferred modifying the PR input schema to a follow-up PR, opting to merge the current PR as-is to maintain stability for both string and list variants (Matrix Chat).

Contribution opportunities

  • Help improve the Fedora documentation for packaging non-crates.io Rust applications, specifically by making the manual .spec file template more prominent for inexperienced packagers.
  • Investigate and help resolve the bazelisk build failure on Rawhide, which currently fails despite building locally.

Learn more about the COPR team.

EPEL

The EPEL team successfully completed the retirement of EPEL 10.2 and switched EPEL 10.3 to build against the newly released RHEL 10.3. Additionally, an EPEL 9.8 archive snapshot was created in response to the RHEL 9.9 release.

Other activities included delivering an RPM packaging workshop at the Texas Linux Fest, ongoing efforts to package Mailman 3 and Incus for EPEL 10, and closing the investigation into ffmpeg CVE-2025-59734 as it could not be reproduced.

Decisions

Contribution opportunities

Learn more about the EPEL team.

Atomic

During this week, the Atomic group focused heavily on system update mechanisms, configuration management, and security. A recurring theme was the handling of file merges and updates across different system directories (/etc vs /var), specifically addressing how to safely regenerate certificates, crypto-policies, and appstream caches during system finalization or boot. Other significant activities included resolving a stalled update pipeline for the Fedora Cosmic-Atomic image and addressing compatibility issues with the new RPM v6 package format in rpm-ostree. The group also initiated discussions on improving the security of sealed images against CVE-2026-121876 by restricting auto-mounted partitions, and continued tracking the long-term goal of migrating away from nss-altfiles.

Decisions

  • Fixed the stalled Fedora Cosmic-Atomic updates by correcting the release engineering scripts, allowing users to receive the latest nightly builds and updates.
  • Determined that the rpm-ostree installation failure for RPM v6 packages (like Google Chrome 157) is an upstream issue; users are advised to use Flathub or hold back the update as a workaround (Ticket 138).
  • Decided to run /etc-only updates (such as ca-certificates, crypto-policies, dconf, and SELinux) in advance at finalization time to avoid boot delays, while acknowledging that /var-dependent updates like mandb and appstream cannot be pre-run (Ticket 145).

Contribution opportunities

  • Investigate and define default restrictive systemd image policies for sealed images to mitigate CVE-2026-121876.
  • Help design a migration path and build images to transition away from nss-altfiles to standard systemd-sysusers or JSON records (Ticket 87).

Learn more about the Atomic team.

CoreOS

This week, the CoreOS group held a meeting to review the Fedora 46 Release Schedule, noting that Rawhide development has begun and that change proposals requiring mass builds or system-wide changes are due in December. In community discussions, a proof-of-concept for live kernel takeover on Fedora bootc using kmorph was shared, demonstrating a potential path forward for rebootless kernel updates.

Ticket activity was high, with 17 tickets addressed. Notable resolutions include a fix for a systemd-journald failure on ppc64le, the rollout of a patch for the CVE-2026-98432 TCP use-after-free vulnerability across multiple streams, and the resolution of an rpm-ostree package download issue in Konflux hermetic builds. Ongoing discussions include a proposed adjustment to the end-of-year release schedule to accommodate holidays and resolving SELinux denials for podman-remote socket connections.

Decisions

  • The community agreed to migrate the automated engineering newsletter repository to the official CoreOS organization (Issue #2240).

Learn more about the CoreOS team.

IoT

This week, the IoT group addressed a system upgrade issue where a user was unable to perform further updates after upgrading to Fedora 45 due to a missing GPG public key. The problem was traced to an outdated GPG key path in the ostree remote configuration that had not been automatically replaced during the upgrade. The user successfully resolved the issue by manually updating the path to the correct directory.

Decisions

  • The maintainers decided to close the GPG public key upgrade issue as an isolated incident, leaving the ticket available as a reference for any other community members who might experience the same configuration problem (Issue #143).

Learn more about the IoT team.

Alternative Images

The Alternative Images group met on November 12 to discuss the status of this quarter's image releases, which are currently delayed due to the setup of a new omni repository for RISC-V. The team expects to release the standard images shortly and is actively developing bootable aarch64 raw images for CentOS Stream 10. Additionally, the group noted that kiwi has been updated to version 11.x in EPEL 10, which integrates the stackbuild and boxbuild plugins directly into the core. In broader news for the Linux community, the CentOS ISA SIG is building a Fedora Omni kernel monthly to ensure compatibility across almost any RISC-V machine. The group also plans to triage their migrated GitLab issues to clear out older, closed items.

Decisions

  • The CentOS ISA SIG decided to create an omni repository for RISC-V, which will include a Fedora Omni kernel built monthly to support a wide range of RISC-V hardware (Meeting Log).
  • The group decided to roadmap the production of both live media and raw disk images for RISC-V for a future quarter, pending the availability of necessary EPEL packages (Meeting Log).
  • It was decided to formally retire the kiwi-boxed-plugin and kiwi-stackbuild-plugin packages in EPEL 10, following the EPEL Retirement Policy, as their functionality is now integrated into the core of kiwi 11.x.

Learn more about the Alternative Images team.

AI

This week, the AI group saw activity across package reviews and AI tooling. A contributor proposed a review swap for a stack of packages including parrotia (a local transcription tool using Whisper) and its dependencies, python-darkdetect and python-customtkinter. In the Matrix channel, discussions covered the Fedora AI contribution policy regarding LLM usage in source code, an AI skill for converting Markdown to Gutenberg-ready print, and a fix for a ROCm upgrade issue between Fedora 44 and 45. Additionally, a new package review request was opened for agent-skills.

Contribution opportunities

  • A contributor is seeking a package review swap and a sponsor for three packages: python-darkdetect, python-customtkinter, and parrotia (link).
  • Testing and karma are requested for a fix addressing the Fedora 44 to 45 upgrade issue with ROCm (link).
  • A package review is requested for agent-skills (link).

Learn more about the AI team.

RISC-V

The Fedora RISC-V group spent significant effort debugging a severe CPU lockup issue specific to the SpacemiT K3 SoC when building Rust with the RVA23 target for ELN (Ticket 40). After extensive testing, contributors identified that the lockup occurs when the CPU speculatively fetches instructions from unmapped code pages. A reliable workaround was found by increasing the page fault size (echo 2097152 > /sys/kernel/debug/fault_around_bytes), allowing multi-core Rust builds to complete successfully.

In other developments, a bug in the GCC build system's multilib configuration causing incorrect rva23u64 target paths was identified. The team also investigated KVM guest initialization failures on the K3 SoC when using QEMU with -cpu max (Ticket 39), noting that -cpu host with EDK2/OVMF bypasses the crash. Additionally, the Titan devicetree was merged into a maintainer tree, paving the way for full usability with the generic v7.5 kernel, and a workaround for a Titan EDK2 boot bug was confirmed.

Decisions

  • Implemented a temporary workaround to increase fault_around_bytes to 2 MiB on K3 builders to prevent CPU lockups during Rust compilation (Ticket 40).
  • Identified that the target-lexicon crate in several Rust packages (e.g., keylime, tss-esapi) needs to be bumped to at least version 0.13.5 to properly support the RVA23 target.
  • Determined that QEMU KVM guests on the K3 SoC currently require -cpu host and EDK2/OVMF to boot successfully, as -cpu max causes instant initialization failures (Ticket 39).

Contribution opportunities

  • Help is needed to update the target-lexicon crate dependencies in various Fedora Rust packages (such as keylime and tss-esapi-sys) to support RVA23.
  • Contributors with access to JTAG hardware for the SpacemiT K3 (e.g., CoM260) are encouraged to help capture low-level CPU traces to find the root cause of the speculative fetch lockups.
  • Assistance is welcome in testing and refining the QEMU/KVM ACPI boot combinations across different RISC-V hardware platforms to document what virtualization configurations work reliably.

Learn more about the RISC-V team.

Gaming

The Gaming group focused on infrastructure and documentation updates this week. Specifically, they completed a migration effort to update repository links and workflows, transitioning references from Pagure to the new Fedora Forge. This included updating the issue tracker links and refining the README with instructions for the Forge PR workflow and site-builder previews. Migrate links from Pagure to Fedora Forge

Learn more about the Gaming team.

Perl

This week, the Perl group primarily focused on package updates and architecture support. Steve Traylen submitted and merged multiple pull requests to update perl-SQL-Abstract to version v2.000003 and bump the EPEL 8 build post-unretire. Additionally, Emmanuel Seyman reported that perl-Algorithm-BloomFilter is failing to build on i686 systems, prompting discussions about dropping support for that architecture.

Decisions

  • Exclude the i686 architecture for the perl-Algorithm-BloomFilter package due to unresolved build failures, unless a fix is provided. Discussed in this thread.
  • Update the perl-SQL-Abstract package to v2.000003 and bump the EPEL 8 build post-unretire, as seen in PR #11 and PR #10.

Contribution opportunities

  • Help resolve the build failure for perl-Algorithm-BloomFilter on i686 hosts to prevent the architecture from being excluded, as noted in this thread.

Learn more about the Perl team.

Ruby

Development for Ruby 4.1 is ongoing, with recent efforts focused on rebuilding the gem ecosystem and addressing Fail To Build From Source (FTBFS) issues against the latest snapshot. A significant change in Ruby 4.1 is the removal of net/pop and net/ftp from the default bundled gems. This removal breaks rubygem-mail and, recursively, Ruby on Rails (RoR) related packages. To mitigate this, a review request for rubygem-net-pop has been submitted. Additionally, maintainers have identified priority FTBFS issues that need resolution, specifically for rubygem-mysql2 and rubygem-ruby-libvirt, which block other major packages like RoR and Vagrant. Upstream Ruby has already fixed the rubygem-ffi FTBFS issue.

Decisions

  • Maintainers decided not to fix the FTBFS issue for rubygem-narray during the Ruby 4.1 migration, as it is an old package and lacks dependent packages.

Contribution opportunities

  • Review or swap-review the new rubygem-net-pop package to help fix Ruby on Rails dependencies.
  • Help resolve the FTBFS issue for rubygem-mysql2 (testsuite failures), which blocks Ruby on Rails packages.
  • Help migrate rubygem-ruby-libvirt to the TypedData API to fix its FTBFS status, which currently blocks vagrant-libvirt.

Learn more about the Ruby team.

Rust

This week, the Rust SIG focused heavily on security updates and package cleanups. Major efforts included rebuilding numerous packages to address security advisories in the zstd, zstd-safe, and quick-xml crates, as well as filing bugs for packages statically linking a vulnerable bundled sqlite. Additionally, the group discussed the challenges of packaging crubit for Chromium builds, ultimately advising against shipping the unstable rustc-dev in Fedora, and successfully concluded the retirement of outdated gtk-rs-core and gtk4-rs compatibility packages.

Decisions

  • The group decided against shipping rustc-dev in Fedora or RHEL due to its reliance on unstable APIs, which impacts the Chromium build process. Alternatives like bundling Rust sources or pre-generating bindings were recommended (URL).
  • Outdated compatibility packages for gtk-rs-core v0.20 and gtk4-rs v0.9 were officially retired from Rawhide after confirming they were no longer in use (URL).
  • Stable branches of msedit will diverge from Rawhide and remain at version 1.x to bypass a test failure on s390x, leaving the Rawhide package temporarily affected by the zstd vulnerability (URL).

Contribution opportunities

  • Maintainers of packages statically linking sqlite (such as flare-im, nodejs-pnpm12, task, and vaultwarden) need to update their packages to address CVE-2026-119375 (URL).
  • Help is needed to port older packages relying on quick-xml v0.38 and v0.37 to the secure v0.41 release, which may require working directly with upstream developers due to default behavior changes (URL).
  • The msedit maintainer has an opportunity to fix an s390x test failure on Rawhide to allow the package to receive the latest zstd security updates (URL).

Learn more about the Rust team.

Other Discussions

Orphaning Packages

  • Dominik 'Rathann' Mierzejewski orphaned the xorg-x11-drv-amdgpu package as they switched to Wayland; it was briefly claimed by Leigh Scott before being orphaned again.
  • Michael J Gruber announced the intent to orphan portmidi, noting a switch to portmidi2 is overdue.

Package Updates

  • On the devel-announce list, Aoife Moloney posted about the Libical4 update, and Michel Lind coordinated the final rebuilds to land it in Rawhide.
  • Adrian Reber announced the libcdio 2.4.0 update in Rawhide, which includes SONAME bumps for libcdio, libiso9660, and libcdio++.
  • Mattia Verga announced that python-dateutil 4.0.0 is coming to Rawhide, un-deprecating the package as upstream has become active again.
  • Dominik 'Rathann' Mierzejewski announced a mac SONAME bump for Monkey's Audio Codec to version 13.46.
  • Shawn W Dunn notified the list of a SONAME update for libfm-qt when version 2.5.0 hits Rawhide.
  • Gwyn Ciesla announced an Angelscript SONAME bump for version 2.39.0.

New Contributor Introductions

  • Alexey Savchkov introduced themselves as a DevOps engineer interested in adopting orphaned C/C++ packages like ptl and usbsniff, and asked about using short vs. full git commit hashes in spec files.
  • Kanishk Bansal introduced themselves with a focus on security, submitting a rebase of expat to fix several CVEs, and expressed interest in automating CVE triage.
  • Igor Bispo introduced themselves as the upstream author of ParrotIA, seeking a sponsor to package it and its Python dependencies for Fedora.

All contribution opportunities

Developers and scripters can tackle a variety of language-specific and system-level challenges across the project. Rust developers are needed to port packages to quick-xml v0.41 and address CVE-2026-119375 in statically linked SQLite packages. Ruby developers can help fix FTBFS issues for rubygem-mysql2 and migrate rubygem-ruby-libvirt to the TypedData API, while Perl experts can resolve an i686 build failure for perl-Algorithm-BloomFilter. Web and scripting contributors can resolve a @comark/nuxt module deprecation, fix failing automated actions in the design repository, or update the docsbuilder.sh script to the new Forge format. Additionally, system-level programmers can assist with a dnf5daemon-server bug or provide patches for a GDM fingerprint login issue.

For those with RPM packaging experience, there are numerous opportunities to review new submissions or adopt orphaned software. Contributors can provide package reviews for agent-skills, rubygem-net-pop, or ParrotIA and its dependencies. Experienced packagers can also adopt orphaned packages like xorg-x11-drv-amdgpu and portmidi, take over a stalled EPEL 10 request for gparted, or help bring mailman3 to EPEL 10 to assist Release Engineering.

Quality assurance and infrastructure enthusiasts are highly encouraged to participate in testing and system maintenance. Testers can join the KDE Plasma 6.8 Test Days, evaluate an unofficial Plasma 6.8.3 COPR, or provide karma for a ROCm upgrade fix. OpenQA experts are needed to investigate a Tux Racer navigation test failure. On the infrastructure side, beginners can learn Ansible by configuring ELN Monitoring for Matrix, while those interested in Zabbix can help refactor external HTTP checks. Contributors with image-building experience can also assist the Server team in updating kiwi definitions to switch the SBC image to GPT/EFI.

Finally, non-code contributions are vital for documentation, design, and community growth. Graphic designers can create a print-ready PDF for a "Fedora loves GNOME" sticker or design a landing page for Fedora Remix. Writers can draft a migration proposal for Fedora Magazine, write a post-installation guide for Strengthening Server Updates, or update legacy syntax in Quick Docs. Community veterans can also provide mentorship by guiding newcomers like Fardeen Khan and Lutz Weber, or by helping Julita Inca get started with Ansible testing.

Dictate into any app on Fedora with TuxTalk

Posted by Fedora Magazine on 2026-11-16 08:00:00 UTC

TuxTalk is a free voice dictation tool for Linux. You hold a key, talk, and let go. What you say appears wherever your cursor is located: a document, an email, a chat box or a terminal. The speech model runs on your own computer, so your voice never leaves it and there is no account to create. This is provided under the MIT license and the code is on GitHub.

This article walks through installing it on Fedora Workstation or Fedora KDE Plasma Desktop, what the first run changes on your system and why, using it day to day, and removing it if you wish.

Before you start

You need a working microphone and a 64-bit Fedora install on x86_64. No graphics card is required. The default speech model is fast on an ordinary processor, and if you have an NVIDIA, AMD or Intel graphics chip, TuxTalk can use it through Vulkan.

TuxTalk isn't in the Fedora repositories and there's no Copr build. You install the RPM from the project's GitHub releases page and check it against the checksum file published with it.

Install the RPM

Download both tuxtalk-0.23.1-1.x86_64.rpm and SHA256SUMS.txt from the latest release at https://github.com/ronb1964/TuxTalk/releases into the same folder. Then check the RPM against the checksum file:

$ cd ~/Downloads
$ sha256sum -c --ignore-missing SHA256SUMS.txt
tuxtalk-0.23.1-1.x86_64.rpm: OK

If it says anything other than OK, delete the file and download it again. Then install it with dnf, which also pulls in the few system libraries it needs:

$ sudo dnf install ./tuxtalk-0.23.1-1.x86_64.rpm

dnf warns that it skipped the OpenPGP check for the package. This is because the RPM isn't signed with a key and why the checksum step, indicated above, matters.

The package installs into /opt/talktype (the folder kept the app's old name so upgrades replace files in place), adds a tuxtalk command, and puts TuxTalk in your applications menu.

Installing on Atomic Desktops

For Silverblue and the other Fedora Atomic desktops, download the AppImage from the same release page indicated above (see the Assets section). Make it executable and run it:

$ chmod +x TuxTalk-v0.23.1-x86_64.AppImage
$ ./TuxTalk-v0.23.1-x86_64.AppImage

What the first run changes

Start TuxTalk from your applications menu. The first-run screen looks at your graphics card and your language and recommends a setup. The default is NVIDIA's Parakeet model, which covers English and 24 other European languages. If you need another language, OpenAI's Whisper covers 99 of them. Either one downloads once and then works offline.

TuxTalk's first-run welcome screen on Fedora KDE Plasma, listing its key features and the three steps: hold F8, talk, let go.
The first-run screen

The first run also asks for your admin password once, to set up two things:

  • The hotkey helper. On Wayland an ordinary program cannot detect keys pressed in other windows, so TuxTalk needs help to notice F8. A small helper program runs as a systemd service, tuxtalk-hotkeys, and it's the only part of TuxTalk that reads the keyboard. It doesn't run as root. It runs as a throwaway user (systemd's DynamicUser) whose only extra right is the input group, with no network, no access to home folders, a read-only system and no way to gain more privileges. It only reports hotkeys, never what you type: F-keys and the few other keys that never type anything, Right Ctrl or Right Alt on their own, or a key held together with two of Ctrl, Alt and Super. Letters, numbers and Enter are never reported. And it only reports them to the user who's at the screen. The file it runs sits in a root-owned folder, /usr/local/libexec/tuxtalk, so nothing you run as yourself can change it.
  • A udev rule that gives /dev/uinput to the user at the screen, the same way Steam's rule does for game controllers. TuxTalk uses it to type, through its own virtual keyboard. A program can press keys with /dev/uinput, but it can't read them.

A restart is not needed. You can look at the helper yourself:

$ systemctl status tuxtalk-hotkeys
$ systemd-analyze security tuxtalk-hotkeys

The second command rates it 0.6, "SAFE".

On Fedora Workstation, TuxTalk also offers to install its GNOME Shell extension, which puts its menu in the top bar. GNOME only loads a new extension after you log out and back in once. On KDE Plasma it shows a tray icon instead.

Dictate

Click where you want the text to go, hold F8, say what you want, and let go. A moment later the text appears. If you'd rather not hold a key for a long dictation, tap F9 to start and tap it again to stop.

KWrite on Fedora KDE Plasma with two dictated sentences: This is a test of the dictation system. Is that right?
Two sentences dictated into KWrite

A few things that make it more useful:

  • Say punctuation and it appears: "comma", "period", "question mark", "new paragraph".
  • Say an email address the way you'd say it out loud. "john at gmail dot com" comes out as john@gmail.com.
  • In a terminal it leaves off the capital letter and the period, so a dictated command is ready to run.
  • Names and terms it keeps getting wrong go in Your Words in Preferences, spelled your way. Or say "fix that word" right after a dictation.
  • For hands-free use, turn on the double-tap option under Preferences → General. Then double-tap F9, talk as long as you like, and it stops by itself when you stop talking.

If your F-keys need the Fn key, Preferences → General also offers Right Ctrl, Right Alt, Scroll Lock or Left Ctrl+Space.

There's more in TuxTalk Labs under Preferences → Advanced. Each feature in this menu is off until you turn it on. The newest feature is running the desktop by voice: opening apps, snapping windows, and a numbered mouse grid you can click with by voice.

Remove TuxTalk

Open Preferences, go to Updates & Backup and click Uninstall TuxTalk…. It asks for your password once and removes everything it set up: the program, the hotkey helper, the udev rule, the downloaded models and the GNOME extension. Your settings are retained unless you tick the box to delete them as well. If TuxTalk won't open, the same thing can run from a terminal:

$ tuxtalk --uninstall

Removing only the package with sudo dnf remove tuxtalk takes the hotkey helper with it, but leaves your settings and the downloaded models in your home folder.

Feedback

TuxTalk is a hobby project, and it gets better when people tell me what doesn't work for them. Questions, problems and ideas are welcome in the Discussion section in the GitHub project at: https://github.com/ronb1964/TuxTalk/discussions

A note on how this was made:

I can't write code. TuxTalk is written by Claude, Anthropic's AI, and I test it and use it every day. I do my best to make sure the code is held to a standard a human developer can respect. Claude also helped me draft this article. I went through it and changed it to sound more like me, and I've checked every step in it. (Assisted-by: Claude)

New badge: F50 i18n Test Day Participant !

Posted by Fedora Badges on 2026-11-16 07:52:19 UTC
F50 i18n Test Day ParticipantYou helped testing Fedora 50 i18n features

New badge: F49 i18n Test Day Participant !

Posted by Fedora Badges on 2026-11-16 07:51:30 UTC
F49 i18n Test Day ParticipantYou helped testing Fedora 49 i18n features

New badge: F48 i18n Test Day Participant !

Posted by Fedora Badges on 2026-11-16 07:50:51 UTC
F48 i18n Test Day ParticipantYou helped testing Fedora 48 i18n features

New badge: F47 i18n Test Day Participant !

Posted by Fedora Badges on 2026-11-16 07:50:13 UTC
F47 i18n Test Day ParticipantYou helped testing Fedora 47 i18n features

New badge: F46 i18n Test Day Participant !

Posted by Fedora Badges on 2026-11-16 07:49:21 UTC
F46 i18n Test Day ParticipantYou helped testing Fedora 46 i18n features

New badge: Fedora 50 CoreOS Test Day !

Posted by Fedora Badges on 2026-11-16 06:38:57 UTC
Fedora 50 CoreOS Test DayYou helped solidify the core for the Fedora 50 rebase!

New badge: Fedora 49 CoreOS Test Day !

Posted by Fedora Badges on 2026-11-16 06:38:26 UTC
Fedora 49 CoreOS Test DayYou helped solidify the core for the Fedora 49 rebase!

New badge: Fedora 48 CoreOS Test Day !

Posted by Fedora Badges on 2026-11-16 06:37:47 UTC
Fedora 48 CoreOS Test DayYou helped solidify the core for the Fedora 48 rebase!

New badge: Fedora 47 CoreOS Test Day !

Posted by Fedora Badges on 2026-11-16 06:37:20 UTC
Fedora 47 CoreOS Test DayYou helped solidify the core for the Fedora 47 rebase!

New badge: Fedora 46 CoreOS Test Day !

Posted by Fedora Badges on 2026-11-16 06:35:19 UTC
Fedora 46 CoreOS Test DayYou helped solidify the core for the Fedora 46 rebase!

New badge: Fedora 45 CoreOS Test Day !

Posted by Fedora Badges on 2026-11-16 06:34:33 UTC
Fedora 45 CoreOS Test DayYou helped solidify the core for the Fedora 45 rebase!

misc fedora bits: second week of november 2026

Posted by Kevin Fenzi on 2026-11-15 18:22:53 UTC
Scrye into the crystal ball

Another busy week gone by, here's a bit belated long form recap of doings in the last week.

anubis adjustments

We use anubis in front of a number of our sites to somewhat keep the scraper menace at bay. For a while I have been puzzled as to why there were so many challenges. After digging into it recently I think I figured out why.

We have a network of proxies all over the world. They each run an anubis instance. Proxies are reached via round robin dns (ie, if you are in say south america you will get a selection of proxies in that region when resolving things).

When you make a request, and anubis decides to challenge you, your browser will do a challenge, anbuis will sign a cookie for you that shows you solved the challenge and are good for a week.

All the proxies use the same key to sign the cookie, so they should all be good on any proxy. Right? Well, no. Because it turns out there's a bit more to make it so you can't just replay a connection and bypass things.

So, you might hit proxy a, get a challenge, be fine for a while, then you hit proxy b. The cookie is valid, but it looks like a replay since it doesn't have any knowlege of it, so you get another challenge.

So, sadly the answer is a shared store for this information for all the proxies. Not great to add another point of failure in but if the proxy cannot reach the backend anyhow, it probibly doesn't matter that it can't reach a valkey store.

So, I setup a common valkey in our openshift cluster with multiple pods, sentinal setup for failover and replication. It was a bit tricky to get it working with our vpn setup, but I managed to do so and rolled it out this last week. First to staging, then a few production hosts, then all of them.

The valkey backend also stores some other info to speed things up.

So, the TLDR version: I hope legit folks will see a good deal less challenges now and thus everything should be a bit faster.

bodhi and the scrapers

Of course that leads into scrapers. poor bodhi.fedoraproject.org ( Our updates system ) has been getting hit pretty hard by scrapers lately. Many of them are "security scanners" trying to get information about security updates. Thats fine, but when you ask for security updates for EOL releases, or security updates for some package where you want page 10000 (ie, updates that came out years and years ago) it puts quite a strain on things.

Bodhi would get a bunch of these database heavy queries, then the backend database would get slow because it's doing so many of them and then the pods would fail liveness check and get restarted.

I did a few things to try and help this:

  • A 30s timeout on web queries. If it takes longer than 30s to answer some query, just teminiate it and take the next request. This should hopefully help prevent long queries from taking all threads up.

  • Scrapers were using the bodhi rss feed feature to bypass anubis We had allowed rss feeds because they often cannot do challenges but the scrapers found you could do '?search=' on rss feeds to search for things. This should now get you a challenge.

  • Increased threads in general to handle more requests.

It seems to have helped, but time will tell.

Also, I think we should look at providing static dumps of common information around updates that people could just download and parse directly. This will take some doing to identify what data people want and get bodhi able to generate it.

mass update/reboot cycle next week

Last week RHEL 10.3 and 9.8 came out, the week before fedora 45 came out. So, next week we are going to update/reboot things, move a bunch of our fedora instances to fedora 45 and resize some things to handle current usage patterns.

As usual, monday should be staging, tuesday/wed should be various hosts we can do without causing any service impact and thursday will be the actual outage when we do the rest.

Hopefully that will leave us into a good state for...

US Thanksgiving holiday

The week after next is the US Thanksgiving holiday. I'm going to be "off" that week, so don't expect me in meetings or the like. I will of course still be around in case problems arise. Hopefully I can actually get to some of my packaging backlog.

As always, comment on the fediverse: https://fosstodon.org/@nirik/117621967377857471

The Butterfly House

Posted by Björn Lindström on 2026-11-14 23:00:00 UTC

Giant owl butterfly (Caligo telamonius memnon) in the Haga Butterfly House in Solna. I thought I was lucky finding them sitting opposite each other like this, but then learned they do that habitually.

Fedora 44 bootc on the Raspberry Pi 5: Status Update (Still Partially Supported)

Posted by Yashwanth Rathakrishnan on 2026-11-13 15:25:27 UTC

Long Story Short

Fedora 44 is a big step up from Fedora 42 on the Raspberry Pi 5. The install process is still the same, and it supports the Pi well. The main limit is still the UEFI to VideoCore translation layer, but the base OS clearly has potential.

What’s Changed With Fedora 44

Starting a Hummingbird Image for RPi5

I started working on a Raspberry Pi 5 compatible Fedora Hummingbird bootc image. The goal is simple: get hummingbird-bootc running on the Pi 5.

Installing the official Claude Desktop Linux beta on Fedora Linux

Posted by Fedora Magazine on 2026-11-13 08:00:00 UTC

Anthropic released a Linux beta of Claude Desktop, but only as a .deb package for Debian and Ubuntu. claude-desktop-rpm is a small Bash script that installs that same package on Fedora. This article covers what the script checks, what it changes on your system, and how to remove it again.

Before you start: what this is and what it costs

Claude Desktop is proprietary software from Anthropic, released under Anthropic's own terms. The install script described here is MIT licensed. It is not made by Anthropic and it does not redistribute any of Anthropic's files: it downloads the package from Anthropic's own repository each time.

You need a Claude account to use the app. Chat works on every plan, including the free one. Claude Code and Cowork, the two features most people install the desktop app for, need a paid plan (Pro, Max, Ultra, Team or Enterprise). Anthropic's download page lists the current plans and prices.

If you would rather use free and open source tools for this kind of work, there are good options that run on Fedora too, such as OpenCode and Hermes Agent. This article is for people who already use Claude and want the official app on Fedora.

What the script checks before installing

Anthropic publishes the Linux beta as a signed APT repository. The script described here reads that repository the same way APT would, and stops if any check fails:

  1. Anthropic's public key must match a fingerprint pinned in the script.
  2. The repository index (InRelease) must be signed by that key, and its Valid-Until date must not have passed.
  3. The package list's checksum must match the signed index.
  4. The .deb's checksum must match the package list.

Only if all these checks are passed does it unpack the .deb. A reader on Fedora Discussion found a gap in the first version (the index could be signed by any key in the key file, not only the pinned one). That is fixed, and the test suite now runs each of these checks against a tampered copy of the repository.

Installing it

The script needs four packages that most Fedora Workstation systems already have. You might verify that these are available:

sudo dnf install curl gnupg2 binutils tar

Next, download the Claude script from the latest release into a folder and run it as your normal user:

curl -fLO https://github.com/ajithakdev/claude-desktop-rpm/releases/latest/download/claude-desktop-rpm.sh

chmod +x claude-desktop-rpm.sh && ./claude-desktop-rpm.sh install

Each release also publishes a checksum file, SHA256SUMS. To check the downloaded script before running it, fetch that file into the same folder used to contain the script and compare:

curl -fLO https://github.com/ajithakdev/claude-desktop-rpm/releases/latest/download/SHA256SUMS

sha256sum -c SHA256SUMS

The script is a single Bash file so you can also read it before running it.

The installation does NOT use sudo. Everything goes into ~/.local (the app, a launcher, the menu entry and icons) and ~/.config (a systemd user timer for updates). The script also copies itself to ~/.local/bin/claude-desktop-rpm, so from then on you can run it by name.

Open Claude from the application menu and sign in. If something looks wrong, run:

claude-desktop-rpm doctor

This checks the installation, the launcher, automatic updates, the tray icon, the keyring that stores your sign-in, and the Cowork prerequisites. Each warning comes with the command that fixes it.

Why the app stays light in dark mode

On GNOME, the app stays light even when the desktop is set to dark. Electron apps on Linux read the GTK theme name, and GNOME's dark style does not change that name. It sets a separate color-scheme preference that Electron ignores.

The script does not touch Anthropic's files. Instead, the launcher created checks GNOME's color-scheme setting when you start the app, and sets GTK_THEME=Adwaita:dark for Claude only when it is dark. If you set GTK_THEME yourself, the launcher leaves it alone.

GNOME also hides tray icons by default, and Claude's tray menu is where Quit lives. The doctor command tells you how to turn on the AppIndicator extension if you want the icon.

Setting up Cowork

Cowork runs tasks inside a small virtual machine, so it needs KVM, QEMU, UEFI firmware and virtiofsd. On Fedora all of these come from Fedora's own repositories. Run this once:

claude-desktop-rpm cowork

This is the only command that uses sudo. It performs the following steps:

  • installs qemu-system-x86-core, edk2-ovmf and virtiofsd with dnf
  • writes /etc/modules-load.d/vhost_vsock.conf and loads the vhost_vsock module
  • adds you to the kvm group

Log out and back in for the group change to take effect. The command does not change any file that a package owns, so rpm -V stays clean. An earlier version did replace two firmware links that edk2-ovmf ships. That was a mistake, and the current version restores the packaged links if it finds the old ones.

Plan for disk space

The app's Cowork virtual machine files take about 12 GB in ~/.config/Claude.

Updates

The script installs a systemd user timer that checks Anthropic's repository once a day. Each update goes through the same checks as the first install. If Claude is open when an update arrives, the script downloads and verifies it but waits, and the launcher puts it in place the next time you start the app.

To turn the daily check off or on again use these commands:

claude-desktop-rpm auto-update off

claude-desktop-rpm auto-update on

Note: If the app shows its own "Update available" button, ignore it. Its link points to APT. The timer handles updates, or you can quit Claude and run claude-desktop-rpm update.

A second account

Some people keep separate Claude accounts for work and personal use. Version 1.2.0 added profiles for that:

claude-desktop-rpm profile add work

This adds "Claude (work)" to the app menu. It opens with its own sign-in and chats in ~/.config/Claude-work, and it can run next to your normal Claude window. The launcher passes Chromium's --user-data-dir flag to do this. Anthropic does not document that flag for Claude Desktop, so a future version could ignore it. If that happens, both menu entries open your normal account and nothing is lost. Both tray icons also look the same; the tray menu, which shows each account's plan, tells them apart.

What does not work yet

  • Computer Use is not in Anthropic's Linux build on any distribution yet.
  • The script is tested on Fedora 44 Workstation (GNOME, x86_64), and its automated install test also passes on Fedora 45. A user reported it working on KDE Plasma on Aurora, an atomic Fedora variant. Other desktops and RHEL-based systems have not been tested much.
  • Anthropic officially supports only Debian and Ubuntu for now. If something breaks after an update, the problem may be in the script, so please report it on the project's issue tracker rather than to Anthropic. (See the project link in the Links section below)

Removing it

claude-desktop-rpm uninstall

This removes everything the install added to ~/.local and ~/.config, including the timer and any profile menu entries, and rebuilds the menu, file-type and icon caches.

Your chats and sign-in in ~/.config/Claude stay, in case you reinstall. Delete that folder (and any Claude-NAME folders) to erase them too.

The uninstall never uses sudo, so the Cowork setup stays: remove the packages with dnf and delete /etc/modules-load.d/vhost_vsock.conf if you no longer need them.

Links

AI Use

Assisted-by: Claude (drafting help for the script and this article; the author reviewed every part and tested each command on Fedora 44).

Friday Links 26-34

Posted by Christof Damian on 2026-11-12 23:00:00 UTC
A rusty metal public bookcase full of books standing on a riverside promenade, with the river and city skyline behind it

This week, give the podcasts about Uber’s AI infrastructure and the Serbian student movement a listen.

Quote of the Week
You’d be amazed at how fast you can get going with a tiny acceleration over a long time.
The Martian
Andy Weir

Leadership

The revised rules of engineering management with Will Larson [Podcast] - It is a bit depressing, but he is probably right that it isn’t as much about people any more.

The syslog-ng Insider 2026-11: Tor; Java; Elasticsearch

Posted by Peter Czanik on 2026-11-12 13:05:28 UTC

Dear syslog-ng users,

This is the 143rd issue of syslog-ng Insider, a monthly newsletter that brings you syslog-ng-related news.

NEWS

Syslog-ng hardening using Tor

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.

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

Syslog-ng end of August news, and about scaling back Java support

Most of August, I was on vacation, but now I’m back and I try catching up on the events of the past weeks, just like my colleagues do. Currently, we are fixing issues and reviewing contributions, but we also discussed scaling back our efforts on Java support.

https://www.syslog-ng.com/community/b/blog/posts/syslog-ng-end-of-august-news-and-about-scaling-back-java-support

Using syslog-ng with Elasticsearch 9.5

Recently, I heard complaints within the syslog-ng community that using Elasticsearch is not that easy anymore. I installed Elasticsearch 9.5 with Kibana to verify these claims.

https://www.syslog-ng.com/community/b/blog/posts/using-syslog-ng-with-elasticsearch-9-5

WEBINARS

Your feedback and news, or tips about the next issue are welcome. To read this newsletter online, visit: https://www.syslog-ng.com/syslog-ng-blog/

syslog-ng logo

Fedora Copr outage - updating servers

Posted by Fedora Infrastructure Status on 2026-11-12 10:30:00 UTC

There will be a Fedora Copr outage while we upgrade infrastructure machines to the latest Copr packages.

The build queue processing will be stopped during the outage, and the Frontend/Web-UI will be down most of the time (no new tasks accepted). The DNF packages and repositories (hosted on copr-backend …

TWIF: November 02 to 08, 2026

Posted by Fedora Community Blog on 2026-11-11 17:02:45 UTC

This Week in Fedora (TWIF) is the Fedora community’s weekly report on project news, decisions, and contribution opportunities. Across the Fedora ecosystem this week, the primary focus was the highly anticipated release of Fedora Linux 45, with teams including Release Engineering, Quality, Infrastructure, Server, and Docs finalizing release candidates, deploying updates, and immediately transitioning into Fedora 46 planning. Beyond the release cycle, a major shared initiative is the Bootable Image Unification (“Atomic Fusion”) project, which dominated the agendas for the Council, Atomic, IoT, and Hummingbird groups as they prepared proof-of-concept demos. Infrastructure and tooling migrations also commanded significant cross-team collaboration; the Council, FESCo, and Quality teams are actively evaluating a potential transition from Bugzilla to a Forgejo-integrated issue tracker, while FESCo, Release Engineering, and ELN are coordinating the complete removal of the legacy DNF4 stack. Finally, adapting to upstream shifts and reinforcing system security were key technical themes, highlighted by FESCo and the KDE SIG managing the deprecation of X11 in KDE Plasma 6.8, alongside widespread security patching and cryptographic upgrades—such as the adoption of %openpgpverify—across the Perl, Rust, Cloud, and Infrastructure teams.

NOTE: This is an experiment of translating the This Week in Fedora report into a Fedora Community Blog series. Do you have feedback? Reply to the Fedora Discussion topic attached to this post and let us know your thoughts.

This Week in Fedora is generated with AI assistance, and this Community Blog edition was prepared with AI assistance too. AI-assisted summaries can be wrong, so please check anything important against the linked sources. If you spot a problem, open an issue in the TWIF repository or reply to this post’s Fedora Discussion topic.

Announcements

Announcements

The highly anticipated release of Fedora Linux 45 is now officially available, as announced across the project forums, community posts, and the announce and devel-announce mailing lists. This milestone brings exciting updates across the ecosystem, including Fedora Workstation 45 featuring GNOME 51’s reworked frame scheduling, and the KDE Plasma Desktop Edition highlighting KDE Plasma 6.8, the 30th-anniversary release of KDE. Hardware support continues to expand with the Fedora Asahi Remix 45 introducing out-of-the-box support for Apple M3 chips, alongside community-maintained RISC-V GA images available for testing, providing a great opportunity for contributors to report hardware enablement issues. For immutable OS users, detailed instructions are available for rebasing to Silverblue 45, while Fedora Atomic Desktops now utilize the new Anaconda Web UI and have migrated their repositories to the atomic-desktops organization, offering streamlined engagement for future contributors.

To avoid disruptive surprises, users and system administrators should note several key technical shifts in this release. The Anaconda installer now includes native support for Stratis storage configuration, simplifying advanced local storage management through an easy-to-use interface. Additionally, the unmaintained NetworkManager-vpnc and NetworkManager-fortisslvpn plugins are officially retired in Fedora 45, requiring users to migrate to actively supported VPN alternatives to maintain enterprise connectivity. Finally, on the infrastructure side, a brief planned server outage occurred on November 6th to reboot main VPN, email, and bastion servers into a new kernel for CVE mitigation, ensuring the ongoing security of the project’s backend services.

AI

AI

The AI/ML SIG discussed new package reviews, notably OpenShell, an NVIDIA-driven tool for agent sandboxing. Packaging updates were announced, with the latest AI and ROCm packages now available in COPRs for released distributions, and new LLM servers like Gufo and Colibri landing in Rawhide. The group is also collaborating on a Fedora Magazine article highlighting the use of the pi-coding-agent to help Fedora contributors, which may evolve into a broader series exploring how AI is utilized within the Fedora ecosystem. Other chat discussions touched on integrating hardware volunteering for AI tasks and addressing Wayland compatibility issues for freelance time-tracking tools.

Decisions

  • The latest AI and ROCm packages are now available for general use in COPRs for released Fedora distributions.
  • New LLM servers, Gufo and Colibri, have been packaged and are available in Rawhide.
  • The SIG will pitch and publish a Fedora Magazine article focusing on the pi-coding-agent, potentially kicking off a series on how AI is used in Fedora.

Contribution opportunities

Learn more about the AI team.

Ambassadors

Ambassadors

The Ambassadors group saw two forum discussions this week. A new contributor asked for help setting up their Fedora Campus Ambassador profile, including access to the wiki, Fedora People, and Libravatar, and received troubleshooting steps from the community. Additionally, a member started an organizational thread to coordinate a meetup for Fedora, CentOS, AlmaLinux, and RockyLinux contributors attending SFSCON 2026 in Bolzano, Italy.

Contribution opportunities

  • Contributors attending SFSCON 2026 in Bolzano, Italy (Nov 13-14) are invited to connect and team up with other community members.

Learn more about the Ambassadors team.

Atomic

Atomic

This week, the Atomic group focused on bootable image unification (“Atomic Fusion”) with an upcoming presentation to the Workstation WG and a seed proof-of-concept demo (Meeting Agenda). In addition, there are ongoing discussions about rebasing Fedora Atomic Desktops on Fedora Bootc base images, which will modernize the build flow (Issue #88).

Several technical issues were also addressed, including a bug where systemd-oomd fails to intervene during memory exhaustion on Kinoite 44 (Issue #130), a syncing issue with the Fedora Cosmic-Atomic image (Issue #137), and an anomaly where rpm-ostree stable commits occasionally bundle packages from the updates-testing repository (Discussion).

Decisions

  • Systemd services in Atomic images will use ConditionPathIsMountPoint=/sysroot instead of checking for /run/ostree-booted to ensure compatibility with the composefs backend (Issue #133).
  • The Fedora Cosmic-Atomic update failure was identified as a release tooling script issue and moved to a releng ticket (Issue #137).

Contribution opportunities

  • Help is needed to file a releng ticket to investigate why rpm-ostree stable commits occasionally pull packages from the updates-testing repository (Discussion).
  • Contributors are invited to help create and review test cases for the upcoming Fedora Atomic Desktops Test Week, covering installations and upgrades via rpm-ostree, gnome-software, and plasma-discover (Issue #87).
  • Assistance is requested to test and provide a controlled reproducer for a memory exhaustion bug where systemd-oomd fails to intervene on Kinoite 44 (Issue #130).

Learn more about the Atomic team.

Cloud

Cloud

This week, the Cloud group focused on image configuration and distribution infrastructure. A key update involves adding the SUSPEND_SAFE_FPR guest OS feature to Fedora Cloud GCP images to address a page reporting suspend UAF vulnerability (CVE-2026-74481), which is now being applied to new nightly builds (Issue 449). Additionally, following the announcement that the HCP Vagrant Registry is shutting down on December 31, the group is discussing setting up a self-hosted Vagrant registry to ensure continued availability of Vagrant boxes, drawing inspiration from AlmaLinux’s recent implementation (Issue 450).

Contribution opportunities

  • Help is needed to set up a self-hosted Vagrant registry for Fedora to replace the retiring HCP Vagrant Registry before December 31 (Issue 450).

Learn more about the Cloud team.

COPR

COPR

This week, the COPR team successfully completed a scheduled server upgrade on November 3rd, bringing new features and bug fixes to the platform. Following the upgrade, an ongoing data migration to Pulp temporarily affected several projects (alphabetically from “sar” to “siddharthvipul1”), causing some 404 errors and pending builds which are expected to resolve as the migration progresses. Additionally, the team discussed the timeline for IPv6 support on the Pulp instance, estimating a fix for early next year, and provided support for building bleeding-edge Rust packages with vendored crates in Copr.

Decisions

  • Completed the scheduled COPR server upgrade on November 3rd to deploy new features and bug fixes. Details can be found in the mailing list thread, the Fedora Infra ticket, and the release notes.
  • Proceeded with the ongoing data migration to Pulp, which temporarily causes 404 errors and pending builds for affected project owners while their specific data is being migrated.

Contribution opportunities

  • Help is welcome to set up automation that recognizes new copr-cli tags being pushed, creates the sdist tarball, and automatically uploads it to PyPI.

Learn more about the COPR team.

CoreOS

CoreOS

This week, the CoreOS team celebrated the general availability release of Fedora Linux 45. The testing stream has been successfully rebased to version 45.20261030.2.1, bringing notable changes such as native Butane support in Ignition, the use of chunkah for better layer reuse in container images, the relocation of RPM repository configs out of /etc, and the update to Podman 6.0. The team is currently in the post-release cleanup phase and has already opened the tracker for the upcoming Fedora 46 rebase. In addition to the release activities, the team addressed several critical bugs and infrastructure tasks. A fix for the IPv4 TCP use-after-free vulnerability (CVE-2026-98432) was shipped in the stable stream, and workarounds are being tested for an ext4 /boot corruption issue affecting upgrades. The team also approved a proposal to switch Konflux-driven streams to a Jenkins poll-based import model to simplify downstream pipeline management.

Decisions

Contribution opportunities

Learn more about the CoreOS team.

Council

Council

This week, the Council focused on the long-term future of Fedora’s issue tracking and ongoing image unification efforts. A major discussion was initiated regarding the potential transition from Bugzilla to a Forgejo-integrated system (related to FESCO#3664), weighing the necessity of adopting modern, open-source infrastructure against concerns over Forgejo’s current maturity and feature parity. Additionally, the agenda for the November 5th Bootable Image Unification (“Atomic Fusion”) meeting was published, featuring a review of the project board, a seed proof-of-concept demo, and a planned presentation to the Workstation Working Group.

Contribution opportunities

Learn more about the Council team.

Design

Design

The Design team focused on the initial sketches for the F46 wallpaper, discussing the use of alternative geometric shapes for bubbles while prioritizing iridescence. They also reviewed poster designs, noting layout inconsistencies and the need for better text hierarchy and spacing, and successfully closed the F45 Virtual Release Party graphics ticket. Additionally, the team discussed accessibility improvements for international audiences, agreeing to spell out acronyms like DEI. In the Matrix chat, automated alerts indicated that the “Fix time of day path” action failed in both the main and f45-backgrounds branches of the backgrounds repository.

Decisions

  • Iridescence will remain the primary visual focus for the F46 wallpaper bubbles, regardless of the final geometric shape chosen.
  • The Fedora logo and mascots will not be included in the wallpaper to comply with guidelines and avoid clutter; instead, mascot concepts will be repurposed for promotional art.
  • Acronyms such as DEI (Diversity, Equity, and Inclusion) will be spelled out in designs to improve accessibility and clarity for international audiences.

Learn more about the Design team.

Docs

Docs

The Fedora Docs team successfully navigated the Fedora 45 release, merging numerous release notes covering updates like GNOME 51, KDE Plasma 6.8, and various system changes. Following the release, the team is restructuring the release notes repository to stop versioning; future notes will be built directly from the main branch, displaying the three most recent supported releases on a single page while older notes remain available via the Internet Archive.

Additionally, the team is revamping its infrastructure by transitioning the site-builder repository to build from main rather than prod. They are also evaluating “Bruce,” a new broken-link detection script, for CI integration to automatically generate static reports and eventually file issues for broken links. Furthermore, discussions are ongoing regarding Antora component consolidation to allow cross-repository module inclusion and integrating the Fedora Design Suite documentation.

Decisions

  • Stop versioning the release notes repository and build them exclusively from the main branch, preserving only the three most recent supported releases (Meeting, Issue #449).
  • Transition the site-builder repository (formerly docs-fp-o) to drop the prod branch and build the production site directly from main (Meeting, Issue #61).
  • Integrate the “Bruce” link-checking script into the CI pipeline in phases, starting with generating a static HTML report before moving to automated issue creation (Issue #69).
  • Retain docsbuilder.sh as a wrapper for local documentation previews while updating the underlying container to support Aarch64 and dropping npm dependencies (Issue #65).

Contribution opportunities

  • Review and merge open pull requests for the Fedora 45 Release Notes, as requested by community members (Forum Topic).
  • Help replace legacy {partialsdir} includes with the partial$ syntax across documentation repositories to align with current Antora standards (Issue #38).
  • Assist in documenting the Fedora Docs site build and monitoring process for the prod and stg branches (Issue #59).
  • Provide feedback on the proposed integration of the Fedora Design Suite documentation into the official Fedora Docs website (Issue #68).
  • Test and provide feedback on the proposed Antora module inclusion methods (component merge vs. Antora extension) to improve cross-SIG documentation discoverability (Issue #66).

Learn more about the Docs team.

ELN

ELN

The ELN SIG held a meeting on November 3, 2026 (meeting log). Key updates include the complete removal of dnf-4 from ELN, the completion of rebuilds for libxml2 2.15, and the replacement of perl-Params-Util with perl-Params-SomeUtil. Additionally, the Content Resolver now displays daily diffs. On the RISC-V front, approximately 140 packages have been built, though progress is currently paused pending fixes for toolchains like gcc, golang, and rust. The group also discussed ongoing issues with KDE Discover (Issue #633) and the unmaintained libappstream-glib (Issue #486), as well as upcoming libical4 rebuilds.

Decisions

  • dnf-4 has been completely removed from ELN and will not be included in RHEL 11.
  • perl-Params-Util has been replaced with perl-Params-SomeUtil.

Learn more about the ELN team.

EPEL

EPEL

This week in EPEL, discussions highlighted a known daily cache delay in the CentOS Stream repo for Fedora’s Koji, which temporarily caused scratch build failures in epel9-next (URL). Security updates were a major focus, with uv (v0.13.5) and ruff (v0.17.2) being pushed to stable for the EPEL10 leading branch to address multiple RUSTSEC vulnerabilities and the eMudhra CA compromise (URL). Additionally, pipx is being retired from EPEL9 due to 23 security vulnerabilities that cannot be practically patched on the older Python 3.9 stack (URL). Other activities included the EPEL 10.2 retirement announcement, progress on bringing mailman to EPEL10, and participation in the release party CLE presentation.

Decisions

  • The pipx package is being retired from EPEL9 due to severe security vulnerabilities and incompatible Python version requirements (URL).
  • Versions 0.13.5 of uv and 0.17.2 of ruff were pushed to stable for the EPEL10 leading branch to address critical security flaws (URL).

Learn more about the EPEL team.

Fedora Join

Fedora Join

Andrew Heath introduced himself to the Fedora community, sharing his extensive background in enterprise Linux, infrastructure automation, and image building. He expressed interest in contributing to packaging, image building, QA, and infrastructure automation. In response, he was welcomed by the community and advised to engage with the packaging team in their Matrix room to find a sponsor and initial tasks.

Contribution opportunities

  • Andrew Heath is seeking a packaging sponsor and looking for good first tasks, particularly in co-maintaining existing packages or picking up orphaned ones in the automation and sysadmin tooling space.
  • Opportunities exist to mentor or collaborate with Andrew in areas like image building (osbuild), QA testing, and infrastructure automation.

Learn more about the Fedora Join team.

FESCo

FESCo

During this week, FESCo celebrated the release of Fedora 45 and announced upcoming elections. The committee held a meeting and processed numerous tickets, focusing heavily on the future of Fedora’s issue tracking system, with extensive debate on whether to migrate to Forgejo or maintain a community-run Bugzilla instance. Other major topics included the coordinated removal of the legacy DNF4 stack and Modularity, as well as handling the deprecation of X11 support in KDE Plasma 6.8 for stable releases.

Decisions

  • Rejected the request to revert the removal of plasma-workspace-x11 from Fedora 44 and 45 in Ticket #3707.
  • Approved the pull request clarifying the responsibilities of the Engineering representative for the Council in Ticket #3613.
  • Rejected the Thin LTO Build Flag (F47) change proposal due to a lack of votes over five weeks in Ticket #3692.
  • Transferred maintainership of python-authlib to a new co-maintainer following the non-responsive maintainer policy in Ticket #3697.

Contribution opportunities

  • Community members are asked to help identify tools and scripts that depend on the legacy DNF4 stack or libmodulemd to assist with their planned removal in Ticket #3702.
  • Volunteers interested in maintaining a community-run Bugzilla instance are invited to put forward a proposal to the Fedora Infrastructure group, as discussed in Ticket #3664.

Learn more about the FESCo team.

Hummingbird

Hummingbird

The Hummingbird group prepared for their upcoming “Atomic Fusion” (bootable image unification) meeting on November 5, 2026. The agenda included a project board review, a potential demo of a seed proof-of-concept, and preparations for presenting to the Workstation Working Group.

Contribution opportunities

Learn more about the Hummingbird team.

Infrastructure

Infrastructure

The Infrastructure team successfully navigated the Fedora 45 release, officially lifting the infrastructure freeze on November 4th. The week involved significant maintenance and troubleshooting, including resolving a storage-related outage on Fedora Forge by resizing its Persistent Volume Claim and NetApp volume, and investigating persistent login issues with Fedora Accounts (FAS) linked to FreeIPA OTP interactions.

In addition to routine maintenance, the team began planning the deployment of Siguldry to the production environment for RPM and OSTree signing. They also scheduled a mass upgrade and reboot of infrastructure servers for November 19th, and discussed ongoing efforts to optimize AWS resource usage and clean up untagged cloud instances.

Decisions

  • The infrastructure freeze for the Fedora 45 release was officially lifted on November 4th. (URL)
  • A mass upgrade and reboot of most infrastructure servers is scheduled for November 19th at 22:00 UTC, which will cause short outages for many contributor services. (URL)
  • Mirrors that transparently redirect HTTP traffic to HTTPS will be updated in MirrorManager to explicitly use HTTPS URLs only, improving crawler compatibility. (URL)
  • The Limestone Networks mirror (mirror.lstn.net) was disabled in MirrorManager due to an expired TLS certificate. (URL)
  • New FAS groups were created for chromium-sig, sysadmin-oraculum, napkinstack-labs, tablepro, and nanlang.

Contribution opportunities

  • Help is needed to investigate and resolve the persistent Unauthorized: bad credentials login errors on accounts.fedoraproject.org, which appear to be related to FreeIPA OTP module interactions. (URL)
  • Contributors can help clean up NetApp and host storage, including moving older releases to archive volumes, increasing partition sizes on alerting hosts, and compressing logs. (URL)
  • Assistance is requested to set up a Zabbix HTTP check for Oraculum and retire its old watchdog email alerts. (URL)
  • There is an opportunity to help set up Zabbix monitoring for the staging autosign service by implementing checks for AMQP, RPMs, OSTree, and CoreOS metrics. (URL)
  • Help is needed to create an announcebot Discourse service user and API key for sending compose announcements. (URL)
  • A new contributor expressed interest in helping with virtualization and infrastructure tasks, presenting an opportunity for onboarding and mentorship. (URL)

Learn more about the Infrastructure team.

IoT

IoT

This week, the IoT group focused on bootable image unification and resolving a system upgrade issue. Laura Santamaria shared the agenda for the “Atomic Fusion” meeting, which included a seed proof-of-concept demo and a presentation to the Workstation Working Group (URL). Additionally, a user reported a bug where upgrading to Fedora 45 fails due to a missing GPG public key in rpm-ostree. The issue was resolved locally by updating the gpgkeypath in the fedora-iot.conf file to point to /usr/share/pki/rpm-gpg/ (URL).

Contribution opportunities

Learn more about the IoT team.

KDE

KDE

This week, the Fedora KDE group navigated discussions regarding Plasma 6.8 updates and overall desktop stability. Notably, the update to Plasma 6.8 officially drops X11 session support upstream, resulting in the obsoletion of kwin-x11 and plasma-workspace-x11 packages in Fedora 44. Users relying on X11 were advised that locking packages might prevent future UI updates, though community workarounds like Copr repositories have emerged. Additionally, the community discussed the marketing and perceived stability of Fedora KDE, with maintainers emphasizing that upstream KDE’s rapid release cadence inherently involves trade-offs. Users seeking long-term support might look toward LTS distributions, while those experiencing bugs are encouraged to contribute directly to upstream bug resolution.

Decisions

  • The update to Plasma 6.8 proceeds with the obsoletion of X11 packages (kwin-x11 and plasma-workspace-x11) due to upstream dropping X11 session support, as discussed in Why the Obsoletes: kwin-x11 and plasma-workspace-x11 in 6.8?.
  • The replacement of kwallet with oo7-daemon is currently deferred for KDE Plasma and Plasma Mobile variants due to a lack of time for integration, as noted in Issue #700.
  • The screen package will not be added to the Kinoite base image; users are advised to use package layering or system extensions instead (Issue #723).

Contribution opportunities

  • Contribute to upstream KDE bug resolution to improve the stability of the Plasma desktop environment, as suggested in the discussion on Fedora KDE stability.
  • Assist with testing and providing feedback on whether KDE processes crashing on boot is still an ongoing issue.
  • Help integrate oo7-daemon and build automatic migration paths from kwallet for future releases (Issue #700).

Learn more about the KDE team.

Legal

In a discussion regarding the koneko license and copyright, Cristian Le followed up on concerns regarding copyrighted sprites included in the project, specifically characters from Cardcaptor Sakura and the BSD Daemon. Following previous advice to drop the artwork, Cristian confirmed that the issue has been flagged to the upstream developers and that the problematic sprites will be removed via a downstream patch if necessary.

Decisions

  • The copyrighted sprites (Cardcaptor Sakura and BSD Daemon) in koneko must be removed, either by upstream or via a downstream patch. (Source)

Learn more about the Legal team.

Magazine

Magazine

This week, the Magazine group’s activity centered around a comprehensive guide on Complete FIDO2 Integration with Fedora Luks2, Unlock, GUI Login, and Sudo Auth. Administrative actions were taken to split three posts from this discussion into a new topic dedicated to revising the guide for Fedora Linux 44.

Contribution opportunities

  • Community feedback is welcome to improve the FIDO2 integration living document.
  • Contributors are encouraged to explore, test, and share improvements regarding FIDO2 integration for Polkit GUI prompts, as the original author left this partially incomplete.

Learn more about the Magazine team.

Mindshare

Mindshare

This week, Mindshare began early planning for the Virtual F46 Release Party, aiming for May 2027, to ensure a smooth event by crowd-sourcing ideas and recruiting role leads well in advance. Additionally, a community member reached out to organize an informal meetup for Fedora, CentOS, AlmaLinux, and RockyLinux contributors attending SFSCON 2026 in Bolzano, Italy.

Contribution opportunities

  • Help organize the Virtual F46 Release Party by volunteering for event team roles including Wrangler, Speakers, Design, Promotion & Content, and Production & Video. To get involved, join the #commops:fedoraproject.org Matrix room and reply to the ticket.
  • Connect with other community members at SFSCON 2026 in Bolzano, Italy, by joining the organizational thread.

Learn more about the Mindshare team.

Perl

Perl

This week, the Perl group focused heavily on package maintenance, dependency management, and security enhancements. Maintainers implemented source signature verification using openpgpverify for packages like perl-Net-DNS and mod_perl. Several packages received routine version bumps, including perl-Mozilla-CA, perl-CGI, and perl-Tk-Text-SuperText. Additionally, contributors collaborated on adjusting dependencies for downstream distributions, such as adding build conditionals for Lexical::Var in perl-Exporter-Tiny and disabling optional dependencies in RHEL builds for perl-File-ShareDir.

Decisions

Learn more about the Perl team.

Python

Python

The Python group discussed reversing the deprecation of python-dateutil following a new upstream 4.0.0 release. Contributors agreed to undeprecate the package and patch out its new tzdata dependency to rely on the system’s time zone data instead. Additionally, a proposal was made to automatically set LD_LIBRARY_PATH in %py3_test_envvars to streamline testing, and feedback is currently being sought on potential breakages.

Decisions

  • Undeprecate the python-dateutil package following the new upstream 4.0.0 release.
  • Patch out the tzdata dependency in python-dateutil 4.0.0 to rely on system timezone data instead.

Contribution opportunities

Learn more about the Python team.

Quality

Quality

The Quality team successfully verified and tested the release candidates for Fedora 45, officially declaring it “GO” for release, alongside publishing and updating the Common Issues. The team also hosted a Test Week for Linux Kernel 7.3, encouraging users to test the kernel rebase on Fedora 44 and 45.

In other activities, the team concluded the F45 test days planning and GRUB EFI for Confidential Computing test days, while scheduling an upcoming KDE Plasma 6.8 test week for November 9-15. Infrastructure and CI improvements continued, including fixes for ELN Koji repositories and successful Fedora 45 installations on Beaker hardware. The team also finalized their requirements for the Bugzilla to Forgejo migration.

Decisions

  • Fedora 45 is officially approved (“GO”) for release after successful release candidate testing.
  • The Bugzilla to Forgejo migration requirements have been formally gathered and submitted, closing the investigation.
  • The Cockpit test day has been postponed to the Fedora 46 release cycle.

Contribution opportunities

Learn more about the Quality team.

Release Engineering

Release Engineering

Fedora 45 has been officially released, with the team handling final release candidate composes, signing the IoT compose, and managing post-release cleanup and synchronization. During the rollout, a minor synchronization issue with the Labs images was manually resolved, and discussions were held to better align fedora_distro_aliases and releases.json updates in future cycles.

In addition to the release, the team resolved several infrastructure and build issues. This included fixing broken RHEL 9 repositories for EPEL 9 builds, addressing a bug where Rawhide .treeinfo files were missing kernel image information, and removing several underpowered x86_64 hosts from the heavybuilder channel to prevent Out-Of-Memory errors during large builds like Chromium.

Decisions

  • Fedora 45 has been officially released.
  • Several underpowered x86_64 build hosts were removed from the heavybuilder channel to prevent OOM errors during large package builds. (URL)
  • A fix was implemented and backported in Pungi to ensure .treeinfo files contain kernel image information, restoring virt-install functionality for Rawhide. (URL)
  • The EPEL 7 meson tagging order issue will not be fixed because EPEL 7 is End of Life. (URL)

Contribution opportunities

Learn more about the Release Engineering team.

RISC-V

RISC-V

The Fedora RISC-V team successfully finalized and announced the Fedora 45 RISC-V GA images, including Server, Container, and Cloud variants. A major focus this cycle was clarifying kernel recommendations: the ‘Omni’ kernel is highly recommended for most physical hardware to avoid issues like PCIe/NVMe data corruption on JH7110-based boards (e.g., VisionFive 2), while the ‘Generic’ kernel is primarily targeted at QEMU and a select few boards. Meanwhile, the bootstrap of Fedora ELN (Enterprise Linux Next) for RISC-V is making significant progress, with Koji fully configured for ELN and RVA23 channels, and over 140 packages already built. The team is also actively debugging hardware-specific issues, including GCC build hangs on the SpacemiT K3 and a QEMU KVM guest initialization bug.

Decisions

  • The ‘Omni’ kernel is officially recommended for most physical RISC-V hardware (including VisionFive 2) to prevent potential data corruption with certain PCIe/NVMe storage configurations, while the ‘Generic’ kernel is recommended primarily for QEMU.
  • Koji hub policies and channels have been updated to route RVA23-specific builds appropriately, enabling the ongoing Fedora ELN bootstrap.

Contribution opportunities

  • Help is needed to debug and resolve a hard lockup issue occurring during GCC ELN and Rust builds on SpacemiT K3 hardware (disabling Transparent Huge Pages is currently being tested as a workaround).
  • Contributors can assist with upstreaming vendor patches from the Omni kernel to the Mainline kernel to improve out-of-the-box hardware support.
  • Developers familiar with QEMU and KVM can help investigate a guest initialization failure when using -cpu max on RISC-V KVM hosts.

Learn more about the RISC-V team.

Rust

Rust

The Rust group focused heavily on security updates and package rebuilds this week, addressing multiple RUSTSEC advisories across crates like zstd, zip, ruzstd, rustls, and webpki-roots. Additionally, there was a mailing list discussion regarding a request to package crubit for Fedora and EPEL to support Chromium builds, though it faces significant hurdles due to its reliance on nightly Rust and unstable compiler internals.

Decisions

  • The request to package crubit for Fedora to support Chromium builds is currently blocked, as the required cc_bindings_from_rs tool depends on a nightly compiler and unstable compiler internals, which cannot be shipped in Fedora (Mailing List).
  • The effort to update packages to ruzstd v0.9 to address RUSTSEC-2026-0344 has been completed and the tracking ticket is closed (Issue 42).

Contribution opportunities

  • Assist with rebuilding or updating applications not co-maintained by the Rust SIG that vendor affected versions of zstd, zstd-safe, rustls, and webpki-roots (Issue 48, Issue 43, Issue 46).
  • Help port applications currently depending on older versions of zip (v0.6), rustls (v0.21/v0.22), and webpki-roots (v0.25) to their latest secure releases (Issue 47).

Learn more about the Rust team.

Server

Server

The Server Working Group celebrated the release of Fedora 45 Server and immediately began preparing for Fedora 46 by setting up a new testing project. A significant portion of the week was dedicated to the “Strengthening Server Updates” project, focusing on system resilience using LVM snapshots. Following the F45 release, the group closed numerous tracking tickets for system-wide changes and package updates.

In addition, the group discussed ongoing work on Ansible support, deciding to catch up on outstanding tasks over the next two weeks before reconvening on the topic. New contributors joined the meeting and immediately volunteered to help with testing and documentation efforts.

Decisions

  • The group agreed to continue using the ticket system for release testing (starting with Fedora 46), with optimizations to be discussed in the process. (Meeting Log, Mailing List)
  • For the “Strengthening Server Updates” project, the agreed next steps are testing the snapshot procedures, adding them as a step in post-installation, and preparing a Fedora Magazine article. (Meeting Log, Mailing List)
  • Members will use the coming weeks to catch up on outstanding tasks for the Ansible support project, deferring further discussion for 14 days. (Meeting Log)

Contribution opportunities

  • Testers are highly needed for the “System Resilience Using LVM Snapshots” procedures. Findings should be reported in Ticket #272.
  • Contributors are invited to help write a how-to style article for the post-installation section regarding server update resilience (Ticket #271).
  • There is an open opportunity to help draft a Fedora Magazine article about the “Strengthening Server Updates” project.
  • Assistance is welcome for the ongoing Ansible support project, specifically regarding the creation of an Ansible management CLI and configuring CI/CD runners (Ticket #268).

Learn more about the Server team.

Websites and Apps

Websites and Apps

This week, the Websites and Apps team resolved an issue where the x86_64 folder was missing from the Fedora 45 Labs download page by syncing the content and rebuilding the site. The team also successfully closed the F45 beta release tracker and opened tickets for UI improvements, including fixing dark-mode logos on the CoreOS page and improving contrast in the Fedora Media Writer section. In addition, a community member reported that the captive portal check URL is on an HSTS-preloaded domain, which breaks Wi-Fi login detection; the infrastructure team plans to move it to another domain in the future. Finally, a bug in Fedocal where events with past repeat-end dates fail to appear was identified and resolved for a user.

Decisions

Contribution opportunities

  • Review requested for the Fedora Maubot/Zodbot plugin for cookies: PR #257 and PR #161.
  • Help needed to fix missing dark-mode variant logos on the CoreOS page (Work item #439).
  • Help needed to improve the contrast of download items in the Fedora Media Writer section (Work item #438).

Learn more about the Websites and Apps team.

Workstation / GNOME

Workstation / GNOME

A brief 20-minute meeting was held on November 3rd, following up on the agenda from October 27th. The original agenda included topics such as Fedora 45 blockers and exceptions, appstream-data automation, and DNF updating without wheel.

Learn more about the Workstation / GNOME team.

Other Discussions

Other Discussions

  • From F45 onwards: Fedora-maintained (self-updating) hardening…: Chris announced a new self-updating kernel hardening feature available from Fedora 45 onwards. Designed for both beginners and advanced users on GNOME and KDE, it applies security-first configurations automatically, overriding certain defaults like yama-ptrace-enable. Users discussed its interaction with Atomic variants, Toolbox containers, and potential impacts on specific applications, with Chris noting that a new #hardening tag will be used to consolidate feedback.
  • Btrfs-patrol: snapshots before every dnf transaction…: JC shared updates on btrfs-patrol, a snapshot and rollback tool tailored for Fedora’s default Btrfs layout. It automatically takes read-only snapshots before dnf5 transactions and allows for one-command rollbacks while ensuring the restored snapshot has the necessary kernel modules to boot.
  • GitLab access for inactive accounts: Shaun McCance announced that due to Fedora exceeding its seat limit on GitLab, accounts with no activity in the past 12 months will be downgraded to view-only access. This will free up seats for active teams without deleting any data, and edit access can be restored if needed.
  • Proposal: Optional CJK input method support for Fedora’s kmscon console: Skyter Lin proposed adding optional CJK (Chinese, Japanese, Korean) input method support for Fedora’s new kmscon virtual console, having successfully tested Traditional Chinese using uim-fep and m17n. Jocelyn Falempe confirmed the technical feasibility of using Super+Space for toggling and suggested starting by adding a kmscon-uim man page.
  • Some news about the Audinux activity for october: Yann Collette provided an October update for the Audinux repository, highlighting the addition of 29 new audio-related packages and 155 package updates. Notable additions include several AI-generated standalone applications like bytebeat, ibniz-rust, and mx44-rust, which underwent security and performance audits.
  • New packages in Fedora Linux (October 2026): Miroslav Suchý shared a comprehensive list of newly added packages to Fedora Linux during October 2026, generated using the rawhide-changes.py script.
  • F46 Change Proposal: Usermode2 (self-contained): On the devel-announce mailing list, Aoife Moloney shared a Fedora 46 Change Proposal to replace the C implementation of the usermode package with a memory-safe Rust rewrite of its userhelper and consolehelper tools. The rewrite serves as a drop-in replacement while dropping several obsolete standalone GUI tools, and developers discussed ensuring the Rust standard library safely handles the SUID execution environment.
  • Is packaging a fork permissible?: Łukasz Wojniłowicz asked if packaging a fork under the same name as the upstream project is permissible. Developers clarified that while it is allowed and sometimes necessary for dormant projects, the spec file should clearly explain the relationship between the original repository and the fork to avoid confusion.
  • F46 Change Proposal: Libical4 (system-wide): On the devel-announce mailing list, Aoife Moloney announced a Fedora 46 Change Proposal to update the libical library to its 4.x series, which introduces an API/ABI break from the 3.x series. Milan Crha and Michel Lind coordinated the necessary package rebuilds in a side tag, noting that only a subset of dependent packages required direct updates.
  • Heads-up: %gpgverify -> %openpgpverify PRs are coming: Jakub Jelen notified maintainers about upcoming pull requests to migrate packages from %gpgverify to the new %openpgpverify macro, which uses Sequoia’s sqv for upstream source signature verification. He advised maintainers to check if their upstream keys need refreshing or updating to comply with current cryptographic standards.
  • Other discussions included Orion Poplawski checking on a non-responsive maintainer for cmake, Nick inquiring about src.fedoraproject.org UI issues, Dawid Wrobel raising concerns about Btrfs metadata exhaustion defaults, Gordon Messmer offering review swaps for podman-desktop, Nick seeking to co-maintain c-toxcore, Miro Hrončok noting a license change in python-cffi, Benson Muite unretiring python-hl7, the cancellation of a Fedora Council meeting, and Petr Pisar correcting the createrepo_c-devel license.

Orphaning packages

  • Orphaned packages looking for new maintainers (on devel-announce): Several orphaned packages were adopted, including tunneler and openfortivpn, while Dominik Mierzejewski advised against adopting rubygem-drake due to obsolescence.
  • Orphaned – singularity-ce: David Trudgian orphaned singularity-ce as the upstream project reached EOL, recommending apptainer as a suitable replacement.

Package updates

  • libcdio 2.4.0 update comes with new sonames: Adrian Reber announced an upcoming update to libcdio 2.4.0 in Rawhide, which bumps several SONAMEs and requires rebuilding dependent packages in a side tag.
  • Soname bump: libcamera: Milan Zamazal planned an update to libcamera 0.8.0 in Rawhide, noting ABI changes that require rebuilding pipewire-plugin-libcamera, libcamera-apps, and plasma-camera.
  • openapv SONAME bump: Dominik Mierzejewski announced an update to openapv that includes a SONAME bump and API changes, requiring a rebuild of FFmpeg to fix a high-severity CVE.
  • sonivox SONAME bump: Yaakov Selkowitz noted an upcoming update to sonivox 4.0.2, which will involve a side tag rebuild for its dependents.
  • CRI-O v1.37 and Go: Brad Smith reported that CRI-O v1.37.3 now requires Go 1.27.1 or newer, blocking updates on F43 and F44.
  • Heads-up: croaring 5.4.0 coming to Rawhide: Ben Beasley announced an ABI-breaking update for croaring to version 5.4.0, which will be coordinated with updates to python-pyroaring and groonga.

New contributor introductions

  • Aashish Jha: A software engineer at Microsoft working on Azure Confidential VMs, introduced himself and his work packaging azure-protected-vm-secrets as his first contribution to Fedora.
All contribution opportunities

All contribution opportunities

Quality Assurance and testing offer some of the most accessible entry points for community members outside of specific working groups. Contributors can participate in the Linux Kernel 7.3 Test Week and the upcoming KDE Plasma 6.8 Test Week, or help draft test cases for the Fedora Atomic Desktops Test Week. There are also numerous opportunities to test specific system features and provide feedback, such as evaluating “System Resilience Using LVM Snapshots” (Ticket #272), the btrfs-patrol snapshot tool, and the new self-updating kernel hardening feature. Furthermore, testers are needed to reproduce a memory exhaustion bug in Kinoite 44, verify if KDE processes are still crashing on boot, and validate a workaround for an ext4 /boot corruption issue in CoreOS.

For those with skills in technical writing, design, or event organization, there are several ways to make an immediate impact. The community is seeking volunteers to fill Wrangler, Speaker, Design, and Promotion roles for the Virtual F46 Release Party, as well as attendees to connect at SFSCON 2026. Writers can help draft Fedora Magazine articles covering Server Update Resilience and AI in Fedora, or write a how-to guide for post-installation server updates (Ticket #271). Documentation contributors are encouraged to review F45 Release Notes pull requests, replace legacy includes with Antora syntax (Issue #38), and provide feedback on integrating the Design Suite docs. Additionally, general feedback is requested on the proposed transition to Forgejo and agenda topics for the Bootable Image Unification meetings.

Contributors with system administration and infrastructure experience can assist with vital operational tasks, and mentorship is available for newcomers interested in virtualization and infrastructure. Immediate needs include setting up a self-hosted Vagrant registry for the Cloud SIG, configuring Zabbix monitoring for the staging autosign service and Oraculum, and cleaning up NetApp and host storage. Automation enthusiasts can help the COPR team set up PyPI upload automation for copr-cli tags, or assist the Server SIG with creating an Ansible management CLI and configuring CI/CD runners (Ticket #268). There is also an ongoing investigation into persistent login errors on accounts.fedoraproject.org related to FreeIPA OTP modules.

Developers and packagers can contribute by adopting orphaned packages like cmake and c-toxcore, or by helping identify tools that still depend on the legacy DNF4 stack for its planned removal. The Rust SIG needs help rebuilding applications that vendor affected versions of libraries like zstd and rustls, and porting others to secure releases. Web developers can submit fixes for missing dark-mode logos on the CoreOS page and review Maubot plugin pull requests. Finally, systems programmers can tackle complex hardware issues, such as debugging a hard lockup during GCC and Rust builds on RISC-V SpacemiT K3 hardware, or investigating a guest initialization failure on RISC-V KVM hosts.

The post TWIF: November 02 to 08, 2026 appeared first on Fedora Community Blog.

Thanks to Sam Altman... ;-)

Posted by Peter Czanik on 2026-11-10 11:50:41 UTC

Wow. Sam Altman did something fantastic. He motivated me. I’m using my AI workstation to work on Linux and experiment with AI!

Last winter I bought a new machine to edit my photos and learn AI on Linux. I’m still doing the photo editing part, but not the AI part. I wanted to keep going, but with my new work responsibilities I was too tired to spend energy on Learning. However, the statement about RAM by Sam Altman turned out to be a good motivation. No promises for regular new articles tough…

First of all, some RAM p*rn :-) 128 GB of RAM, from that 8 GB is set to be video RAM (but it could be set to anything from 512 MB to 96 GB…). The price of the little box doubled within a month of purchase simply due to the amount of RAM included. Sam & Co. have made RAM pretty much unaffordable…

root@fedora:~# free -h
               total        used        free      shared  buff/cache   available
Mem:           117Gi       2.2Gi       115Gi       8.0Mi       1.1Gi       115Gi
Swap:           39Gi          0B        39Gi

And finally, I’m working on Linux and AI again. Fedora is now updated from version 44 to 45 on the machine. And openSUSE Tumbleweed has also seen gigabytes worth of updates. Next up: getting AI workloads running again. I had to remove ROCm during upgrade: dependency problems, as far as I could see. I have just reinstalled the packages, and checking documentation…

I have Open WebUI installed from half a year ago, together with ollama. I tested both from the command line and from the Open WebUI: they work. Next time I will try to do something actually useful. :-)

root@fedora:~# ollama list
NAME               ID              SIZE      MODIFIED       
llama3.2:latest    a80c4f17acd5    2.0 GB    24 minutes ago    
gemma3:27b         a418f5838eaf    17 GB     7 months ago      
granite4:latest    4235724a127c    2.1 GB    7 months ago      
root@fedora:~# ollama show granite4
  Model
    architecture        granite    
    parameters          3.4B       
    context length      131072     
    embedding length    2560       
    quantization        Q4_K_M     

  Capabilities
    completion    
    tools         

  License
    Apache License               
    Version 2.0, January 2004    
    ...                          

root@fedora:~# ollama --verbose
>>> who are you?
I am Hermes, a language model created by IBM to assist with a variety of tasks and answer questions on many topics. I strive to provide helpful, informative, and engaging responses 
while being respectful and avoiding any harmful or unethical content.

total duration:       1.111554719s
load duration:        42.916831ms
prompt eval count:    12 token(s)
prompt eval duration: 23.637941ms
prompt eval rate:     507.66 tokens/s
eval count:           47 token(s)
eval duration:        1.020660833s
eval rate:            46.05 tokens/s
>>> print the first 10 prime numbers
The first 10 prime numbers are:

1. 2
2. 3
3. 5
4. 7
5. 11
6. 13
7. 17
8. 19
9. 23
10. 29

total duration:       1.434860225s
load duration:        47.052753ms
prompt eval count:    75 token(s)
prompt eval duration: 106.452539ms
prompt eval rate:     704.54 tokens/s
eval count:           58 token(s)
eval duration:        1.254814127s
eval rate:            46.22 tokens/s
>>> Send a message (/? for help)

AI in a miniature box :-)

You can read my older posts about my AI box under the toy tag.

Copr, explained: the sandbox where Fedora packaging starts

Posted by Justin Wheeler on 2026-11-10 08:00:00 UTC
Copr, explained: the sandbox where Fedora packaging starts

In 2017, I wanted a small tool to change my laptop’s screen brightness. I found one that worked, but Fedora did not have an RPM package for it. So I set out to package it myself. Fedora Copr made that first attempt far less stressful. I wrote up that first package at the time: How I created my first RPM package in Fedora. Copr remains one of the most useful tools in the Fedora contribution ecosystem.

This post is the introduction I wish I had read before I started. It explains what Copr is, why packagers and users rely on it, and why its sandbox-like design matters now.

What Copr is 🔗

Copr, short for Community Projects, is a build service. You give it a source RPM (SRPM), and it builds the package and hosts the results in a DNF or YUM repository. Copr runs on Fedora infrastructure. You can use the public instance at copr.fedorainfracloud.org.

If you use Arch Linux, Copr is the closest parallel to the Arch User Repository (AUR). Both are community spaces where people share packages for others to use. The AUR shares build scripts, and you build the package on your own machine. Copr goes a step further. It builds the RPM for you and hosts the repository, so you enable it and install with DNF.

You need a Fedora Account System (FAS) login to create a project. You do not need special approval. You can build for several Fedora releases, EPEL releases, and other targets in one step. One SRPM can produce packages for many releases and architectures.

Why packagers use Copr 🔗

When I started, my biggest question was whether my package would build on the releases I cared about. Koji is Fedora’s official build system, and I used scratch builds there to test. Copr solved a different problem. It let me host the package, install it on my own machine, and share a repository with others before I submitted anything for review.

Koji scratch builds caught a Fedora 27 failure that I fixed before I submitted my package for review. Copr is not a replacement for that process. It is a place to test first.

Copr as an instant enablement path 🔗

Recently, I used Copr to package something new I was working on. I packaged a set of Markdown files, each one an Agent Skill, from the Fedora Agent Skills Library into a single RPM. I published it in the AI/ML SIG Copr project and started sharing it for testing and use.

My plan is to package agent-skills officially in Fedora. Copr made that first step possible because it gave me the fastest path to get an RPM into users' hands. Users got a semi-official channel to install the package now, and I got real feedback while the official process moves along.

Copr as a sandbox 🔗

Copr works well as a sandbox. Several design choices make that true.

  • Projects are separate. Packages in your Copr project do not enter Fedora’s official repositories. Your experiments stay in your own repository.

  • Packaging rules are relaxed. Copr packages do not have to follow the Fedora Packaging Guidelines. The guidelines are still recommended, but you can test ideas before you meet every rule.

  • Projects can expire. You can set a project to delete itself after a number of days. This suits short tests and one-off experiments.

  • Old builds are removed. By default, Copr keeps one build per package and deletes the others after 14 days. Projects on the newer Pulp backend keep the five most recent successful builds per package instead, so test projects do not grow forever.

A sandbox does not mean anything goes. Copr is Free Software, and its repositories are signed. However, the Copr maintainers do not review every package. Before you install a package from a Copr project, check who maintains it. If you can, look at the SRPM and spec file. Projects distributed in Copr must also follow Fedora’s license rules.

Where Copr fits in the innovation discussion 🔗

Fedora is discussing a Council proposal for an Innovation Lifecycle. The proposal includes a "sandbox stage" for experimental work that is too large for a single change proposal. One of its stated goals is to isolate risk. Experiments should be able to break without affecting the main distribution or the people who depend on it.

The proposal also notes that it does not yet define standard sandbox infrastructure. Copr is not part of that proposal. It already shows what a low-risk space for experiments can look like. Work stays separate from official releases, feedback comes quickly, and strong packages can follow a path into Fedora. I hope we keep that spirit as the larger discussion moves forward.

Packaging as a fallback 🔗

Distribution methods will change over time. Right now, RPM packaging works well. It is tested, proven, and well understood by Fedora contributors and users. When we do not know how to share something new, RPM packaging is a path we can always fall back on. It provides versioning and a distribution mechanism for large varieties of software. Copr makes that RPM packaging fallback fast.

Getting started 🔗

You need a FAS account, a project, and an SRPM or RPM spec. These commands create a project for Fedora Rawhide and submit a build:

copr-cli create --chroot fedora-rawhide-x86_64 my-first-project
copr-cli build my-first-project ./my-package.spec

For more detail, read the Copr user documentation.

Final thoughts 🔗

Copr gave me a low-risk way to learn packaging, and it can do the same for you. If you have a package that is too early for Fedora, build it in Copr, share it, and learn from the results. Thank you to everyone who maintains Copr and helps packagers use it.


Featured image generated by LLM-gen-AI using the OpenAI image API.

Falando de uma Revolução

Posted by Avi Alkalay on 2026-11-09 21:36:56 UTC

Joyce Moreno adaptou para português do Brasil a linda canção Talkin’ Bout a Revolution, de Tracy Chapman. Foi lançado em seu álbum Music Inside de 1990. O álbum não está disponível nas plataformas musicais, mas tem no YouTube da Joyce. Eis a letra que ela adaptou e a rara gravação.


Todos ‘tão falando de uma revolução
Assim, baixinho

Sopra o vento nos seringais
O que está marcado a fogo e aço nas usinas
Sobe os morros, os becos das capitais
E lá vai o buxixo nas esquinas

Todos ‘tão falando de uma revolução
Assim, baixinho

Quem não tem nada vai querer
Pegar o que é seu
Quem não tem nada vai querer
Ganhar o que perdeu

E corre, anda logo logo logo logo
Corre corre corre corre corre, vai vai corre

Um dia vira a mesa, não dá prá evitar
Uma revolução vem vindo
Um dia vira a mesa e todos vão falar
E já não vai ser baixinho

From November 02 to November 08

Posted by Aurélien Bompard on 2026-11-09 09:48:00 UTC

Across the Fedora ecosystem this week, the primary focus was the highly anticipated release of Fedora Linux 45, with teams including Release Engineering, Quality, Infrastructure, Server, and Docs finalizing release candidates, deploying updates, and immediately transitioning into Fedora 46 planning. Beyond the release cycle, a major shared initiative is the Bootable Image Unification ("Atomic Fusion") project, which dominated the agendas for the Council, Atomic, IoT, and Hummingbird groups as they prepared proof-of-concept demos. Infrastructure and tooling migrations also commanded significant cross-team collaboration; the Council, FESCo, and Quality teams are actively evaluating a potential transition from Bugzilla to a Forgejo-integrated issue tracker, while FESCo, Release Engineering, and ELN are coordinating the complete removal of the legacy DNF4 stack. Finally, adapting to upstream shifts and reinforcing system security were key technical themes, highlighted by FESCo and the KDE SIG managing the deprecation of X11 in KDE Plasma 6.8, alongside widespread security patching and cryptographic upgrades—such as the adoption of %openpgpverify—across the Perl, Rust, Cloud, and Infrastructure teams.

Announcements

The highly anticipated release of Fedora Linux 45 is now officially available, as announced across the project forums, community posts, and the announce and devel-announce mailing lists. This milestone brings exciting updates across the ecosystem, including Fedora Workstation 45 featuring GNOME 51's reworked frame scheduling, and the KDE Plasma Desktop Edition highlighting KDE Plasma 6.8, the 30th-anniversary release of KDE. Hardware support continues to expand with the Fedora Asahi Remix 45 introducing out-of-the-box support for Apple M3 chips, alongside community-maintained RISC-V GA images available for testing, providing a great opportunity for contributors to report hardware enablement issues. For immutable OS users, detailed instructions are available for rebasing to Silverblue 45, while Fedora Atomic Desktops now utilize the new Anaconda Web UI and have migrated their repositories to the atomic-desktops organization, offering streamlined engagement for future contributors.

To avoid disruptive surprises, users and system administrators should note several key technical shifts in this release. The Anaconda installer now includes native support for Stratis storage configuration, simplifying advanced local storage management through an easy-to-use interface. Additionally, the unmaintained NetworkManager-vpnc and NetworkManager-fortisslvpn plugins are officially retired in Fedora 45, requiring users to migrate to actively supported VPN alternatives to maintain enterprise connectivity. Finally, on the infrastructure side, a brief planned server outage occurred on November 6th to reboot main VPN, email, and bastion servers into a new kernel for CVE mitigation, ensuring the ongoing security of the project's backend services.

Council

This week, the Council focused on the long-term future of Fedora's issue tracking and ongoing image unification efforts. A major discussion was initiated regarding the potential transition from Bugzilla to a Forgejo-integrated system (related to FESCO#3664), weighing the necessity of adopting modern, open-source infrastructure against concerns over Forgejo's current maturity and feature parity. Additionally, the agenda for the November 5th Bootable Image Unification ("Atomic Fusion") meeting was published, featuring a review of the project board, a seed proof-of-concept demo, and a planned presentation to the Workstation Working Group.

Contribution opportunities

Learn more about the Council team.

FESCo

During this week, FESCo celebrated the release of Fedora 45 and announced upcoming elections. The committee held a meeting and processed numerous tickets, focusing heavily on the future of Fedora's issue tracking system, with extensive debate on whether to migrate to Forgejo or maintain a community-run Bugzilla instance. Other major topics included the coordinated removal of the legacy DNF4 stack and Modularity, as well as handling the deprecation of X11 support in KDE Plasma 6.8 for stable releases.

Decisions

  • Rejected the request to revert the removal of plasma-workspace-x11 from Fedora 44 and 45 in Ticket #3707.
  • Approved the pull request clarifying the responsibilities of the Engineering representative for the Council in Ticket #3613.
  • Rejected the Thin LTO Build Flag (F47) change proposal due to a lack of votes over five weeks in Ticket #3692.
  • Transferred maintainership of python-authlib to a new co-maintainer following the non-responsive maintainer policy in Ticket #3697.

Contribution opportunities

  • Community members are asked to help identify tools and scripts that depend on the legacy DNF4 stack or libmodulemd to assist with their planned removal in Ticket #3702.
  • Volunteers interested in maintaining a community-run Bugzilla instance are invited to put forward a proposal to the Fedora Infrastructure group, as discussed in Ticket #3664.

Learn more about the FESCo team.

Mindshare

This week, Mindshare began early planning for the Virtual F46 Release Party, aiming for May 2027, to ensure a smooth event by crowd-sourcing ideas and recruiting role leads well in advance. Additionally, a community member reached out to organize an informal meetup for Fedora, CentOS, AlmaLinux, and RockyLinux contributors attending SFSCON 2026 in Bolzano, Italy.

Contribution opportunities

  • Help organize the Virtual F46 Release Party by volunteering for event team roles including Wrangler, Speakers, Design, Promotion & Content, and Production & Video. To get involved, join the #commops:fedoraproject.org Matrix room and reply to the ticket.
  • Connect with other community members at SFSCON 2026 in Bolzano, Italy, by joining the organizational thread.

Learn more about the Mindshare team.

Magazine

This week, the Magazine group's activity centered around a comprehensive guide on Complete FIDO2 Integration with Fedora Luks2, Unlock, GUI Login, and Sudo Auth. Administrative actions were taken to split three posts from this discussion into a new topic dedicated to revising the guide for Fedora Linux 44.

Contribution opportunities

  • Community feedback is welcome to improve the FIDO2 integration living document.
  • Contributors are encouraged to explore, test, and share improvements regarding FIDO2 integration for Polkit GUI prompts, as the original author left this partially incomplete.

Learn more about the Magazine team.

Fedora Join

Andrew Heath introduced himself to the Fedora community, sharing his extensive background in enterprise Linux, infrastructure automation, and image building. He expressed interest in contributing to packaging, image building, QA, and infrastructure automation. In response, he was welcomed by the community and advised to engage with the packaging team in their Matrix room to find a sponsor and initial tasks.

Contribution opportunities

  • Andrew Heath is seeking a packaging sponsor and looking for good first tasks, particularly in co-maintaining existing packages or picking up orphaned ones in the automation and sysadmin tooling space.
  • Opportunities exist to mentor or collaborate with Andrew in areas like image building (osbuild), QA testing, and infrastructure automation.

Learn more about the Fedora Join team.

Ambassadors

The Ambassadors group saw two forum discussions this week. A new contributor asked for help setting up their Fedora Campus Ambassador profile, including access to the wiki, Fedora People, and Libravatar, and received troubleshooting steps from the community. Additionally, a member started an organizational thread to coordinate a meetup for Fedora, CentOS, AlmaLinux, and RockyLinux contributors attending SFSCON 2026 in Bolzano, Italy.

Contribution opportunities

  • Contributors attending SFSCON 2026 in Bolzano, Italy (Nov 13-14) are invited to connect and team up with other community members.

Learn more about the Ambassadors team.

Workstation / GNOME

A brief 20-minute meeting was held on November 3rd, following up on the agenda from October 27th. The original agenda included topics such as Fedora 45 blockers and exceptions, appstream-data automation, and DNF updating without wheel.

Learn more about the Workstation / GNOME team.

KDE

This week, the Fedora KDE group navigated discussions regarding Plasma 6.8 updates and overall desktop stability. Notably, the update to Plasma 6.8 officially drops X11 session support upstream, resulting in the obsoletion of kwin-x11 and plasma-workspace-x11 packages in Fedora 44. Users relying on X11 were advised that locking packages might prevent future UI updates, though community workarounds like Copr repositories have emerged. Additionally, the community discussed the marketing and perceived stability of Fedora KDE, with maintainers emphasizing that upstream KDE's rapid release cadence inherently involves trade-offs. Users seeking long-term support might look toward LTS distributions, while those experiencing bugs are encouraged to contribute directly to upstream bug resolution.

Decisions

  • The update to Plasma 6.8 proceeds with the obsoletion of X11 packages (kwin-x11 and plasma-workspace-x11) due to upstream dropping X11 session support, as discussed in Why the Obsoletes: kwin-x11 and plasma-workspace-x11 in 6.8?.
  • The replacement of kwallet with oo7-daemon is currently deferred for KDE Plasma and Plasma Mobile variants due to a lack of time for integration, as noted in Issue #700.
  • The screen package will not be added to the Kinoite base image; users are advised to use package layering or system extensions instead (Issue #723).

Contribution opportunities

  • Contribute to upstream KDE bug resolution to improve the stability of the Plasma desktop environment, as suggested in the discussion on Fedora KDE stability.
  • Assist with testing and providing feedback on whether KDE processes crashing on boot is still an ongoing issue.
  • Help integrate oo7-daemon and build automatic migration paths from kwallet for future releases (Issue #700).

Learn more about the KDE team.

Server

The Server Working Group celebrated the release of Fedora 45 Server and immediately began preparing for Fedora 46 by setting up a new testing project. A significant portion of the week was dedicated to the "Strengthening Server Updates" project, focusing on system resilience using LVM snapshots. Following the F45 release, the group closed numerous tracking tickets for system-wide changes and package updates.

In addition, the group discussed ongoing work on Ansible support, deciding to catch up on outstanding tasks over the next two weeks before reconvening on the topic. New contributors joined the meeting and immediately volunteered to help with testing and documentation efforts.

Decisions

  • The group agreed to continue using the ticket system for release testing (starting with Fedora 46), with optimizations to be discussed in the process. (Meeting Log, Mailing List)
  • For the "Strengthening Server Updates" project, the agreed next steps are testing the snapshot procedures, adding them as a step in post-installation, and preparing a Fedora Magazine article. (Meeting Log, Mailing List)
  • Members will use the coming weeks to catch up on outstanding tasks for the Ansible support project, deferring further discussion for 14 days. (Meeting Log)

Contribution opportunities

  • Testers are highly needed for the "System Resilience Using LVM Snapshots" procedures. Findings should be reported in Ticket #272.
  • Contributors are invited to help write a how-to style article for the post-installation section regarding server update resilience (Ticket #271).
  • There is an open opportunity to help draft a Fedora Magazine article about the "Strengthening Server Updates" project.
  • Assistance is welcome for the ongoing Ansible support project, specifically regarding the creation of an Ansible management CLI and configuring CI/CD runners (Ticket #268).

Learn more about the Server team.

Infrastructure

The Infrastructure team successfully navigated the Fedora 45 release, officially lifting the infrastructure freeze on November 4th. The week involved significant maintenance and troubleshooting, including resolving a storage-related outage on Fedora Forge by resizing its Persistent Volume Claim and NetApp volume, and investigating persistent login issues with Fedora Accounts (FAS) linked to FreeIPA OTP interactions.

In addition to routine maintenance, the team began planning the deployment of Siguldry to the production environment for RPM and OSTree signing. They also scheduled a mass upgrade and reboot of infrastructure servers for November 19th, and discussed ongoing efforts to optimize AWS resource usage and clean up untagged cloud instances.

Decisions

  • The infrastructure freeze for the Fedora 45 release was officially lifted on November 4th. (URL)
  • A mass upgrade and reboot of most infrastructure servers is scheduled for November 19th at 22:00 UTC, which will cause short outages for many contributor services. (URL)
  • Mirrors that transparently redirect HTTP traffic to HTTPS will be updated in MirrorManager to explicitly use HTTPS URLs only, improving crawler compatibility. (URL)
  • The Limestone Networks mirror (mirror.lstn.net) was disabled in MirrorManager due to an expired TLS certificate. (URL)
  • New FAS groups were created for chromium-sig, sysadmin-oraculum, napkinstack-labs, tablepro, and nanlang.

Contribution opportunities

  • Help is needed to investigate and resolve the persistent Unauthorized: bad credentials login errors on accounts.fedoraproject.org, which appear to be related to FreeIPA OTP module interactions. (URL)
  • Contributors can help clean up NetApp and host storage, including moving older releases to archive volumes, increasing partition sizes on alerting hosts, and compressing logs. (URL)
  • Assistance is requested to set up a Zabbix HTTP check for Oraculum and retire its old watchdog email alerts. (URL)
  • There is an opportunity to help set up Zabbix monitoring for the staging autosign service by implementing checks for AMQP, RPMs, OSTree, and CoreOS metrics. (URL)
  • Help is needed to create an announcebot Discourse service user and API key for sending compose announcements. (URL)
  • A new contributor expressed interest in helping with virtualization and infrastructure tasks, presenting an opportunity for onboarding and mentorship. (URL)

Learn more about the Infrastructure team.

Release Engineering

Fedora 45 has been officially released, with the team handling final release candidate composes, signing the IoT compose, and managing post-release cleanup and synchronization. During the rollout, a minor synchronization issue with the Labs images was manually resolved, and discussions were held to better align fedora_distro_aliases and releases.json updates in future cycles.

In addition to the release, the team resolved several infrastructure and build issues. This included fixing broken RHEL 9 repositories for EPEL 9 builds, addressing a bug where Rawhide .treeinfo files were missing kernel image information, and removing several underpowered x86_64 hosts from the heavybuilder channel to prevent Out-Of-Memory errors during large builds like Chromium.

Decisions

  • Fedora 45 has been officially released.
  • Several underpowered x86_64 build hosts were removed from the heavybuilder channel to prevent OOM errors during large package builds. (URL)
  • A fix was implemented and backported in Pungi to ensure .treeinfo files contain kernel image information, restoring virt-install functionality for Rawhide. (URL)
  • The EPEL 7 meson tagging order issue will not be fixed because EPEL 7 is End of Life. (URL)

Contribution opportunities

Learn more about the Release Engineering team.

Quality

The Quality team successfully verified and tested the release candidates for Fedora 45, officially declaring it "GO" for release, alongside publishing and updating the Common Issues. The team also hosted a Test Week for Linux Kernel 7.3, encouraging users to test the kernel rebase on Fedora 44 and 45.

In other activities, the team concluded the F45 test days planning and GRUB EFI for Confidential Computing test days, while scheduling an upcoming KDE Plasma 6.8 test week for November 9-15. Infrastructure and CI improvements continued, including fixes for ELN Koji repositories and successful Fedora 45 installations on Beaker hardware. The team also finalized their requirements for the Bugzilla to Forgejo migration.

Decisions

Contribution opportunities

Learn more about the Quality team.

Websites and Apps

This week, the Websites and Apps team resolved an issue where the x86_64 folder was missing from the Fedora 45 Labs download page by syncing the content and rebuilding the site. The team also successfully closed the F45 beta release tracker and opened tickets for UI improvements, including fixing dark-mode logos on the CoreOS page and improving contrast in the Fedora Media Writer section. In addition, a community member reported that the captive portal check URL is on an HSTS-preloaded domain, which breaks Wi-Fi login detection; the infrastructure team plans to move it to another domain in the future. Finally, a bug in Fedocal where events with past repeat-end dates fail to appear was identified and resolved for a user.

Decisions

Contribution opportunities

  • Review requested for the Fedora Maubot/Zodbot plugin for cookies: PR #257 and PR #161.
  • Help needed to fix missing dark-mode variant logos on the CoreOS page (Work item #439).
  • Help needed to improve the contrast of download items in the Fedora Media Writer section (Work item #438).

Learn more about the Websites and Apps team.

Design

The Design team focused on the initial sketches for the F46 wallpaper, discussing the use of alternative geometric shapes for bubbles while prioritizing iridescence. They also reviewed poster designs, noting layout inconsistencies and the need for better text hierarchy and spacing, and successfully closed the F45 Virtual Release Party graphics ticket. Additionally, the team discussed accessibility improvements for international audiences, agreeing to spell out acronyms like DEI. In the Matrix chat, automated alerts indicated that the "Fix time of day path" action failed in both the main and f45-backgrounds branches of the backgrounds repository.

Decisions

  • Iridescence will remain the primary visual focus for the F46 wallpaper bubbles, regardless of the final geometric shape chosen.
  • The Fedora logo and mascots will not be included in the wallpaper to comply with guidelines and avoid clutter; instead, mascot concepts will be repurposed for promotional art.
  • Acronyms such as DEI (Diversity, Equity, and Inclusion) will be spelled out in designs to improve accessibility and clarity for international audiences.

Learn more about the Design team.

Docs

The Fedora Docs team successfully navigated the Fedora 45 release, merging numerous release notes covering updates like GNOME 51, KDE Plasma 6.8, and various system changes. Following the release, the team is restructuring the release notes repository to stop versioning; future notes will be built directly from the main branch, displaying the three most recent supported releases on a single page while older notes remain available via the Internet Archive.

Additionally, the team is revamping its infrastructure by transitioning the site-builder repository to build from main rather than prod. They are also evaluating "Bruce," a new broken-link detection script, for CI integration to automatically generate static reports and eventually file issues for broken links. Furthermore, discussions are ongoing regarding Antora component consolidation to allow cross-repository module inclusion and integrating the Fedora Design Suite documentation.

Decisions

  • Stop versioning the release notes repository and build them exclusively from the main branch, preserving only the three most recent supported releases (Meeting, Issue #449).
  • Transition the site-builder repository (formerly docs-fp-o) to drop the prod branch and build the production site directly from main (Meeting, Issue #61).
  • Integrate the "Bruce" link-checking script into the CI pipeline in phases, starting with generating a static HTML report before moving to automated issue creation (Issue #69).
  • Retain docsbuilder.sh as a wrapper for local documentation previews while updating the underlying container to support Aarch64 and dropping npm dependencies (Issue #65).

Contribution opportunities

  • Review and merge open pull requests for the Fedora 45 Release Notes, as requested by community members (Forum Topic).
  • Help replace legacy {partialsdir} includes with the partial$ syntax across documentation repositories to align with current Antora standards (Issue #38).
  • Assist in documenting the Fedora Docs site build and monitoring process for the prod and stg branches (Issue #59).
  • Provide feedback on the proposed integration of the Fedora Design Suite documentation into the official Fedora Docs website (Issue #68).
  • Test and provide feedback on the proposed Antora module inclusion methods (component merge vs. Antora extension) to improve cross-SIG documentation discoverability (Issue #66).

Learn more about the Docs team.

In a discussion regarding the koneko license and copyright, Cristian Le followed up on concerns regarding copyrighted sprites included in the project, specifically characters from Cardcaptor Sakura and the BSD Daemon. Following previous advice to drop the artwork, Cristian confirmed that the issue has been flagged to the upstream developers and that the problematic sprites will be removed via a downstream patch if necessary.

Decisions

  • The copyrighted sprites (Cardcaptor Sakura and BSD Daemon) in koneko must be removed, either by upstream or via a downstream patch. (Source)

Learn more about the Legal team.

COPR

This week, the COPR team successfully completed a scheduled server upgrade on November 3rd, bringing new features and bug fixes to the platform. Following the upgrade, an ongoing data migration to Pulp temporarily affected several projects (alphabetically from "sar" to "siddharthvipul1"), causing some 404 errors and pending builds which are expected to resolve as the migration progresses. Additionally, the team discussed the timeline for IPv6 support on the Pulp instance, estimating a fix for early next year, and provided support for building bleeding-edge Rust packages with vendored crates in Copr.

Decisions

  • Completed the scheduled COPR server upgrade on November 3rd to deploy new features and bug fixes. Details can be found in the mailing list thread, the Fedora Infra ticket, and the release notes.
  • Proceeded with the ongoing data migration to Pulp, which temporarily causes 404 errors and pending builds for affected project owners while their specific data is being migrated.

Contribution opportunities

  • Help is welcome to set up automation that recognizes new copr-cli tags being pushed, creates the sdist tarball, and automatically uploads it to PyPI.

Learn more about the COPR team.

EPEL

This week in EPEL, discussions highlighted a known daily cache delay in the CentOS Stream repo for Fedora's Koji, which temporarily caused scratch build failures in epel9-next (URL). Security updates were a major focus, with uv (v0.13.5) and ruff (v0.17.2) being pushed to stable for the EPEL10 leading branch to address multiple RUSTSEC vulnerabilities and the eMudhra CA compromise (URL). Additionally, pipx is being retired from EPEL9 due to 23 security vulnerabilities that cannot be practically patched on the older Python 3.9 stack (URL). Other activities included the EPEL 10.2 retirement announcement, progress on bringing mailman to EPEL10, and participation in the release party CLE presentation.

Decisions

  • The pipx package is being retired from EPEL9 due to severe security vulnerabilities and incompatible Python version requirements (URL).
  • Versions 0.13.5 of uv and 0.17.2 of ruff were pushed to stable for the EPEL10 leading branch to address critical security flaws (URL).

Learn more about the EPEL team.

ELN

The ELN SIG held a meeting on November 3, 2026 (meeting log). Key updates include the complete removal of dnf-4 from ELN, the completion of rebuilds for libxml2 2.15, and the replacement of perl-Params-Util with perl-Params-SomeUtil. Additionally, the Content Resolver now displays daily diffs. On the RISC-V front, approximately 140 packages have been built, though progress is currently paused pending fixes for toolchains like gcc, golang, and rust. The group also discussed ongoing issues with KDE Discover (Issue #633) and the unmaintained libappstream-glib (Issue #486), as well as upcoming libical4 rebuilds.

Decisions

  • dnf-4 has been completely removed from ELN and will not be included in RHEL 11.
  • perl-Params-Util has been replaced with perl-Params-SomeUtil.

Learn more about the ELN team.

Atomic

This week, the Atomic group focused on bootable image unification ("Atomic Fusion") with an upcoming presentation to the Workstation WG and a seed proof-of-concept demo (Meeting Agenda). In addition, there are ongoing discussions about rebasing Fedora Atomic Desktops on Fedora Bootc base images, which will modernize the build flow (Issue #88).

Several technical issues were also addressed, including a bug where systemd-oomd fails to intervene during memory exhaustion on Kinoite 44 (Issue #130), a syncing issue with the Fedora Cosmic-Atomic image (Issue #137), and an anomaly where rpm-ostree stable commits occasionally bundle packages from the updates-testing repository (Discussion).

Decisions

  • Systemd services in Atomic images will use ConditionPathIsMountPoint=/sysroot instead of checking for /run/ostree-booted to ensure compatibility with the composefs backend (Issue #133).
  • The Fedora Cosmic-Atomic update failure was identified as a release tooling script issue and moved to a releng ticket (Issue #137).

Contribution opportunities

  • Help is needed to file a releng ticket to investigate why rpm-ostree stable commits occasionally pull packages from the updates-testing repository (Discussion).
  • Contributors are invited to help create and review test cases for the upcoming Fedora Atomic Desktops Test Week, covering installations and upgrades via rpm-ostree, gnome-software, and plasma-discover (Issue #87).
  • Assistance is requested to test and provide a controlled reproducer for a memory exhaustion bug where systemd-oomd fails to intervene on Kinoite 44 (Issue #130).

Learn more about the Atomic team.

CoreOS

This week, the CoreOS team celebrated the general availability release of Fedora Linux 45. The testing stream has been successfully rebased to version 45.20261030.2.1, bringing notable changes such as native Butane support in Ignition, the use of chunkah for better layer reuse in container images, the relocation of RPM repository configs out of /etc, and the update to Podman 6.0. The team is currently in the post-release cleanup phase and has already opened the tracker for the upcoming Fedora 46 rebase. In addition to the release activities, the team addressed several critical bugs and infrastructure tasks. A fix for the IPv4 TCP use-after-free vulnerability (CVE-2026-98432) was shipped in the stable stream, and workarounds are being tested for an ext4 /boot corruption issue affecting upgrades. The team also approved a proposal to switch Konflux-driven streams to a Jenkins poll-based import model to simplify downstream pipeline management.

Decisions

Contribution opportunities

Learn more about the CoreOS team.

IoT

This week, the IoT group focused on bootable image unification and resolving a system upgrade issue. Laura Santamaria shared the agenda for the "Atomic Fusion" meeting, which included a seed proof-of-concept demo and a presentation to the Workstation Working Group (URL). Additionally, a user reported a bug where upgrading to Fedora 45 fails due to a missing GPG public key in rpm-ostree. The issue was resolved locally by updating the gpgkeypath in the fedora-iot.conf file to point to /usr/share/pki/rpm-gpg/ (URL).

Contribution opportunities

Learn more about the IoT team.

Cloud

This week, the Cloud group focused on image configuration and distribution infrastructure. A key update involves adding the SUSPEND_SAFE_FPR guest OS feature to Fedora Cloud GCP images to address a page reporting suspend UAF vulnerability (CVE-2026-74481), which is now being applied to new nightly builds (Issue 449). Additionally, following the announcement that the HCP Vagrant Registry is shutting down on December 31, the group is discussing setting up a self-hosted Vagrant registry to ensure continued availability of Vagrant boxes, drawing inspiration from AlmaLinux's recent implementation (Issue 450).

Contribution opportunities

  • Help is needed to set up a self-hosted Vagrant registry for Fedora to replace the retiring HCP Vagrant Registry before December 31 (Issue 450).

Learn more about the Cloud team.

Hummingbird

The Hummingbird group prepared for their upcoming "Atomic Fusion" (bootable image unification) meeting on November 5, 2026. The agenda included a project board review, a potential demo of a seed proof-of-concept, and preparations for presenting to the Workstation Working Group.

Contribution opportunities

Learn more about the Hummingbird team.

AI

The AI/ML SIG discussed new package reviews, notably OpenShell, an NVIDIA-driven tool for agent sandboxing. Packaging updates were announced, with the latest AI and ROCm packages now available in COPRs for released distributions, and new LLM servers like Gufo and Colibri landing in Rawhide. The group is also collaborating on a Fedora Magazine article highlighting the use of the pi-coding-agent to help Fedora contributors, which may evolve into a broader series exploring how AI is utilized within the Fedora ecosystem. Other chat discussions touched on integrating hardware volunteering for AI tasks and addressing Wayland compatibility issues for freelance time-tracking tools.

Decisions

  • The latest AI and ROCm packages are now available for general use in COPRs for released Fedora distributions.
  • New LLM servers, Gufo and Colibri, have been packaged and are available in Rawhide.
  • The SIG will pitch and publish a Fedora Magazine article focusing on the pi-coding-agent, potentially kicking off a series on how AI is used in Fedora.

Contribution opportunities

Learn more about the AI team.

RISC-V

The Fedora RISC-V team successfully finalized and announced the Fedora 45 RISC-V GA images, including Server, Container, and Cloud variants. A major focus this cycle was clarifying kernel recommendations: the 'Omni' kernel is highly recommended for most physical hardware to avoid issues like PCIe/NVMe data corruption on JH7110-based boards (e.g., VisionFive 2), while the 'Generic' kernel is primarily targeted at QEMU and a select few boards. Meanwhile, the bootstrap of Fedora ELN (Enterprise Linux Next) for RISC-V is making significant progress, with Koji fully configured for ELN and RVA23 channels, and over 140 packages already built. The team is also actively debugging hardware-specific issues, including GCC build hangs on the SpacemiT K3 and a QEMU KVM guest initialization bug.

Decisions

  • The 'Omni' kernel is officially recommended for most physical RISC-V hardware (including VisionFive 2) to prevent potential data corruption with certain PCIe/NVMe storage configurations, while the 'Generic' kernel is recommended primarily for QEMU.
  • Koji hub policies and channels have been updated to route RVA23-specific builds appropriately, enabling the ongoing Fedora ELN bootstrap.

Contribution opportunities

  • Help is needed to debug and resolve a hard lockup issue occurring during GCC ELN and Rust builds on SpacemiT K3 hardware (disabling Transparent Huge Pages is currently being tested as a workaround).
  • Contributors can assist with upstreaming vendor patches from the Omni kernel to the Mainline kernel to improve out-of-the-box hardware support.
  • Developers familiar with QEMU and KVM can help investigate a guest initialization failure when using -cpu max on RISC-V KVM hosts.

Learn more about the RISC-V team.

Perl

This week, the Perl group focused heavily on package maintenance, dependency management, and security enhancements. Maintainers implemented source signature verification using openpgpverify for packages like perl-Net-DNS and mod_perl. Several packages received routine version bumps, including perl-Mozilla-CA, perl-CGI, and perl-Tk-Text-SuperText. Additionally, contributors collaborated on adjusting dependencies for downstream distributions, such as adding build conditionals for Lexical::Var in perl-Exporter-Tiny and disabling optional dependencies in RHEL builds for perl-File-ShareDir.

Decisions

Learn more about the Perl team.

Python

The Python group discussed reversing the deprecation of python-dateutil following a new upstream 4.0.0 release. Contributors agreed to undeprecate the package and patch out its new tzdata dependency to rely on the system's time zone data instead. Additionally, a proposal was made to automatically set LD_LIBRARY_PATH in %py3_test_envvars to streamline testing, and feedback is currently being sought on potential breakages.

Decisions

  • Undeprecate the python-dateutil package following the new upstream 4.0.0 release.
  • Patch out the tzdata dependency in python-dateutil 4.0.0 to rely on system timezone data instead.

Contribution opportunities

Learn more about the Python team.

Rust

The Rust group focused heavily on security updates and package rebuilds this week, addressing multiple RUSTSEC advisories across crates like zstd, zip, ruzstd, rustls, and webpki-roots. Additionally, there was a mailing list discussion regarding a request to package crubit for Fedora and EPEL to support Chromium builds, though it faces significant hurdles due to its reliance on nightly Rust and unstable compiler internals.

Decisions

  • The request to package crubit for Fedora to support Chromium builds is currently blocked, as the required cc_bindings_from_rs tool depends on a nightly compiler and unstable compiler internals, which cannot be shipped in Fedora (Mailing List).
  • The effort to update packages to ruzstd v0.9 to address RUSTSEC-2026-0344 has been completed and the tracking ticket is closed (Issue 42).

Contribution opportunities

  • Assist with rebuilding or updating applications not co-maintained by the Rust SIG that vendor affected versions of zstd, zstd-safe, rustls, and webpki-roots (Issue 48, Issue 43, Issue 46).
  • Help port applications currently depending on older versions of zip (v0.6), rustls (v0.21/v0.22), and webpki-roots (v0.25) to their latest secure releases (Issue 47).

Learn more about the Rust team.

Other Discussions

  • From F45 onwards: Fedora-maintained (self-updating) hardening...: Chris announced a new self-updating kernel hardening feature available from Fedora 45 onwards. Designed for both beginners and advanced users on GNOME and KDE, it applies security-first configurations automatically, overriding certain defaults like yama-ptrace-enable. Users discussed its interaction with Atomic variants, Toolbox containers, and potential impacts on specific applications, with Chris noting that a new #hardening tag will be used to consolidate feedback.
  • Btrfs-patrol: snapshots before every dnf transaction...: JC shared updates on btrfs-patrol, a snapshot and rollback tool tailored for Fedora's default Btrfs layout. It automatically takes read-only snapshots before dnf5 transactions and allows for one-command rollbacks while ensuring the restored snapshot has the necessary kernel modules to boot.
  • GitLab access for inactive accounts: Shaun McCance announced that due to Fedora exceeding its seat limit on GitLab, accounts with no activity in the past 12 months will be downgraded to view-only access. This will free up seats for active teams without deleting any data, and edit access can be restored if needed.
  • Proposal: Optional CJK input method support for Fedora's kmscon console: Skyter Lin proposed adding optional CJK (Chinese, Japanese, Korean) input method support for Fedora's new kmscon virtual console, having successfully tested Traditional Chinese using uim-fep and m17n. Jocelyn Falempe confirmed the technical feasibility of using Super+Space for toggling and suggested starting by adding a kmscon-uim man page.
  • Some news about the Audinux activity for october: Yann Collette provided an October update for the Audinux repository, highlighting the addition of 29 new audio-related packages and 155 package updates. Notable additions include several AI-generated standalone applications like bytebeat, ibniz-rust, and mx44-rust, which underwent security and performance audits.
  • New packages in Fedora Linux (October 2026): Miroslav Suchý shared a comprehensive list of newly added packages to Fedora Linux during October 2026, generated using the rawhide-changes.py script.
  • F46 Change Proposal: Usermode2 (self-contained): On the devel-announce mailing list, Aoife Moloney shared a Fedora 46 Change Proposal to replace the C implementation of the usermode package with a memory-safe Rust rewrite of its userhelper and consolehelper tools. The rewrite serves as a drop-in replacement while dropping several obsolete standalone GUI tools, and developers discussed ensuring the Rust standard library safely handles the SUID execution environment.
  • Is packaging a fork permissible?: Łukasz Wojniłowicz asked if packaging a fork under the same name as the upstream project is permissible. Developers clarified that while it is allowed and sometimes necessary for dormant projects, the spec file should clearly explain the relationship between the original repository and the fork to avoid confusion.
  • F46 Change Proposal: Libical4 (system-wide): On the devel-announce mailing list, Aoife Moloney announced a Fedora 46 Change Proposal to update the libical library to its 4.x series, which introduces an API/ABI break from the 3.x series. Milan Crha and Michel Lind coordinated the necessary package rebuilds in a side tag, noting that only a subset of dependent packages required direct updates.
  • Heads-up: %gpgverify -> %openpgpverify PRs are coming: Jakub Jelen notified maintainers about upcoming pull requests to migrate packages from %gpgverify to the new %openpgpverify macro, which uses Sequoia's sqv for upstream source signature verification. He advised maintainers to check if their upstream keys need refreshing or updating to comply with current cryptographic standards.
  • Other discussions included Orion Poplawski checking on a non-responsive maintainer for cmake, Nick inquiring about src.fedoraproject.org UI issues, Dawid Wrobel raising concerns about Btrfs metadata exhaustion defaults, Gordon Messmer offering review swaps for podman-desktop, Nick seeking to co-maintain c-toxcore, Miro Hrončok noting a license change in python-cffi, Benson Muite unretiring python-hl7, the cancellation of a Fedora Council meeting, and Petr Pisar correcting the createrepo_c-devel license.

Orphaning packages

  • Orphaned packages looking for new maintainers (on devel-announce): Several orphaned packages were adopted, including tunneler and openfortivpn, while Dominik Mierzejewski advised against adopting rubygem-drake due to obsolescence.
  • Orphaned - singularity-ce: David Trudgian orphaned singularity-ce as the upstream project reached EOL, recommending apptainer as a suitable replacement.

Package updates

  • libcdio 2.4.0 update comes with new sonames: Adrian Reber announced an upcoming update to libcdio 2.4.0 in Rawhide, which bumps several SONAMEs and requires rebuilding dependent packages in a side tag.
  • Soname bump: libcamera: Milan Zamazal planned an update to libcamera 0.8.0 in Rawhide, noting ABI changes that require rebuilding pipewire-plugin-libcamera, libcamera-apps, and plasma-camera.
  • openapv SONAME bump: Dominik Mierzejewski announced an update to openapv that includes a SONAME bump and API changes, requiring a rebuild of FFmpeg to fix a high-severity CVE.
  • sonivox SONAME bump: Yaakov Selkowitz noted an upcoming update to sonivox 4.0.2, which will involve a side tag rebuild for its dependents.
  • CRI-O v1.37 and Go: Brad Smith reported that CRI-O v1.37.3 now requires Go 1.27.1 or newer, blocking updates on F43 and F44.
  • Heads-up: croaring 5.4.0 coming to Rawhide: Ben Beasley announced an ABI-breaking update for croaring to version 5.4.0, which will be coordinated with updates to python-pyroaring and groonga.

New contributor introductions

  • Aashish Jha: A software engineer at Microsoft working on Azure Confidential VMs, introduced himself and his work packaging azure-protected-vm-secrets as his first contribution to Fedora.

All contribution opportunities

Quality Assurance and testing offer some of the most accessible entry points for community members outside of specific working groups. Contributors can participate in the Linux Kernel 7.3 Test Week and the upcoming KDE Plasma 6.8 Test Week, or help draft test cases for the Fedora Atomic Desktops Test Week. There are also numerous opportunities to test specific system features and provide feedback, such as evaluating "System Resilience Using LVM Snapshots" (Ticket #272), the btrfs-patrol snapshot tool, and the new self-updating kernel hardening feature. Furthermore, testers are needed to reproduce a memory exhaustion bug in Kinoite 44, verify if KDE processes are still crashing on boot, and validate a workaround for an ext4 /boot corruption issue in CoreOS.

For those with skills in technical writing, design, or event organization, there are several ways to make an immediate impact. The community is seeking volunteers to fill Wrangler, Speaker, Design, and Promotion roles for the Virtual F46 Release Party, as well as attendees to connect at SFSCON 2026. Writers can help draft Fedora Magazine articles covering Server Update Resilience and AI in Fedora, or write a how-to guide for post-installation server updates (Ticket #271). Documentation contributors are encouraged to review F45 Release Notes pull requests, replace legacy includes with Antora syntax (Issue #38), and provide feedback on integrating the Design Suite docs. Additionally, general feedback is requested on the proposed transition to Forgejo and agenda topics for the Bootable Image Unification meetings.

Contributors with system administration and infrastructure experience can assist with vital operational tasks, and mentorship is available for newcomers interested in virtualization and infrastructure. Immediate needs include setting up a self-hosted Vagrant registry for the Cloud SIG, configuring Zabbix monitoring for the staging autosign service and Oraculum, and cleaning up NetApp and host storage. Automation enthusiasts can help the COPR team set up PyPI upload automation for copr-cli tags, or assist the Server SIG with creating an Ansible management CLI and configuring CI/CD runners (Ticket #268). There is also an ongoing investigation into persistent login errors on accounts.fedoraproject.org related to FreeIPA OTP modules.

Developers and packagers can contribute by adopting orphaned packages like cmake and c-toxcore, or by helping identify tools that still depend on the legacy DNF4 stack for its planned removal. The Rust SIG needs help rebuilding applications that vendor affected versions of libraries like zstd and rustls, and porting others to secure releases. Web developers can submit fixes for missing dark-mode logos on the CoreOS page and review Maubot plugin pull requests. Finally, systems programmers can tackle complex hardware issues, such as debugging a hard lockup during GCC and Rust builds on RISC-V SpacemiT K3 hardware, or investigating a guest initialization failure on RISC-V KVM hosts.

On sovereign AI

Posted by Fabio Alessandro Locati on 2026-11-08 23:00:00 UTC

Although AI has become a very mainstream topic in the last three years, the concept of sovereign AI has not reached the mainstream yet. The problem isn’t only its low profile, but also that it is often used as a sovereignty theater rather than real sovereignty. The first thing to realize is that sovereignty is not a boolean characteristic; it is a multidimensional spectrum, and any conversation that treats it as boolean fails to be informative. Although the exact number of dimensions is arbitrary, and different people might consider different ones, I prefer a three-dimensional model.

misc fedora bits: first week of november 2026

Posted by Kevin Fenzi on 2026-11-07 19:45:48 UTC
Scrye into the crystal ball

Hello everyone. Another week gone by and some longer form recapping.

Fedora 45 released!

Fedora 45 was released on tuesday. Things went mostly smoothly, with just some few things needing tweaking. There was also some Labs missing from the master mirror sync (fixed) and torrents (will be fixed soon).

Our master mirrors were doing 20-25Gbps a second for tuesday and wed, so definitely lots of bits flowing.

I think this is a pretty solid release, I hope you like it too.

Post release unfreeze

After the release was all out, we ended our Infrastructure freeze. I merged/deployed 8 pull requests that were blocked by the freeze, and processed some ticket backlog. More of that next week.

The "AI" security apocolypse

So, there's been a lot of discussion in social media/around about all the new security vulnerabilities that are being found and the effect that has been having on open source projects and maintainers. It's quite relentless over the previous months for many folks, and has a lot of ill effects, including:

  • Always having to be ready for security bugs

  • No more disclosure time/embargoes, so you have to release fast

  • Inability to have time to actually work on features or regular maint, have to focus on security all the time.

Thats all well known, but I thought I would add the effect this has on operations folks. Case in point, late last week anthropic announced they had found a criticial bug in the linux kernel (all versions at the time after 4.14 or so). This became CVE-2026-98432, with a super high CVSS score (9.8 out of 10!).

I looked at it last weekend and anthropic in their announcement said: "In our proof of concept, it takes 48 minutes to leak a kernel pointer and another five minutes to reach the shell command execution." But it doesn't actally provide any details. Whats the connection? whats the kernel? Whats the hardware?

Everything else I saw said no one had seen a public exploit yet. Forgive me for not trusting a company that has a large incentive to talk up their tooling and a track record of breathless announcements that turn out to not be exactly what they say.

In any case, I upgraded most of out public facing servers as soon as their was a RHEL update, along with our openshift clusters. However there were a few that I wanted to actually schedule an outage for just in case there was issues, so I scheduled that for friday. I also had to wait until after release, because I didn't want to break things right before our release went out.

By the time friday rolled around: There were 2 new kernel updates fixing more CVEs and 2 more openshift updates (fixing the same).

Granted that it's nice to be in a state where you can just reboot anything as soon as updates come along, but there's cases where that is just not a very great idea (like if you are about to do a major release and don't want to possibly break things).

Anyhow, I am sure it's not going to get better for a while, but I hold out some hope that someday we will have found all the obvious bugs and it will slow down.

As always, comment on the fediverse: https://fosstodon.org/@nirik/117576954904513971

Community Connection Part Two - IndiaFOSS 2026

Posted by Akashdeep Dhar on 2026-11-07 18:30:00 UTC
Community Connection Part Two - IndiaFOSS 2026

We took some time to interact with the booth visitors at the IndiaFOSS 2026 conference's Red Hat Community Booth. While representing Fedora Project on the event grounds and handing out special swags, we were the conduits for the community's sentiments both as users and contributors to free and open source software projects like that of ours.

11:44am IST

Community Connection Part Two - IndiaFOSS 2026
Manifest A
  1. Open Alternatives
    LibreOffice Calc could be used as a zero-cost in-place software alternative to Office Excel for taxation, compliance and logistics.
  2. Software Interoperability
    Proprietary formats from Office Excel are a barrier for cross-platform collaboration and open formats should hence be preferred.

12:12pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest B
  1. Beginner Friendly
    Starting from Microsoft Windows, it is crucial to account for a smoother learning curve while seeking next alternatives for operating systems.
  2. Individual Requirements
    Alternatives can be tried in virtual machines and live environments to check if they fit their personal needs or if other variants are required.
  3. Innovative Approach
    The fast release cycle does not necessarily mean that Fedora Linux is unstable as all the updates are duly tested before being published.
  4. Gradual Exploration
    A good starting point with a general purpose GNU/Linux distribution like ours could be helpful in someone learning about the ecosystem.

12:20pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest C
  1. Personal Exploration
    After jumping in the deep end with Arch Linux's installation steps, a CA student found Fedora Linux's installation steps to be refreshing.
  2. Troubleshooting Resources
    The active community helped them resolve software and hardware issues, with Realtek WiFi adapters on their Lenovo LOQ laptop device.
  3. Getting Occupied
    With the information on Join SIG and FAS accounts, they were asked to participate and find their circle of interest within the community.
  4. Desktop Experience
    Their personal usage with i3 window manager and various dotfiles let them to truly make the Fedora Linux experience as their own.

12:36pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest D
  1. EndeavourOS Movement
    Seeking a fresh desktop environment experience from GNOME, they moved from Fedora Linux to EndeavourOS, only come back later.
  2. Positive Experience
    Acknowledging Fedora Linux's capabilities, they admitted it to be mostly GNOME, and hence, the KDE variant was suggested to them.
  3. Encouraging Contributors
    They appreciated how they could get started with contributing meaningfully to Fedora Project with zero technical expertise to begin with.
  4. Software Availability
    Some moved away from Fedora Linux as certain proprietary cyber security tools were not available packaged in the official repositories.
  5. Diverse Opportunities
    Community driven mentorship guidance helped individuals with designing, testing, documenting, triaging etc. to help Fedora Project.
  6. Existing Contributions
    They previously helped with software packaging build systems for 3D modelling tools and libraries, with UPI support for various platforms.
  7. Contribution Motivations
    Their participation was a passion project rooted in community connection and निष्काम सेवा or selfless service, with freedom and sharing.
  8. Maintainer Challenges
    Human reviews for generated contributions made it harder for maintainers to provide meaningful efforts expended to guide contributors.
  9. Controversial Opinions
    Excessive generation significantly undermines meaningful contributions, with constant struggles for finding time to review everything.
  10. Genuine Contributions
    Open source software movement thrives on genuine participation, shared ownership, constructive feedback and welcoming communities.

02:02pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest E
  1. Personal Problems
    The participant shared contributions to basic call conversation recording for Android phones and generic kernel images for Snapdragon.
  2. Appreciating Community
    Without any factors that discouraged them from participation, they had blessings for multimedia suite like VLC and MPV in the open.
  3. Exploring Alternatives
    From Endeavour Linux to Fedora Linux, they experimented with window managers and desktop environments to see what fits the best.
  4. Proprietary Limitations
    Users cannot investigate issues and resolve problems in proprietary codebases, thus making it crucial to explore what everyone uses.

02:10pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest F
  1. Atomic Future
    Immutable distributions are sought to eventually replace traditional installations with package managers leading to greater reliability.
  2. Habitual Transitions
    Widespread adoption would require workflow changes to users habituated to classic commands and hence, this will take some time.
  3. Reproducible Configuration
    Tooling like Ignition and Butane enable shareable customization with recommendation to directly use YAML configuration for processing.
  4. System Provisioning
    While NixOS provides greater advanced controls, the Fedora CoreOS suite covers the requirements without a steep learning curve.
  5. Bootable Containers
    Image mode operating systems are gradually becoming the refreshed normal with the layering packages for purpose specific systems.
  6. Immutable Systems
    Comparing against previous controversial changes that ended up being standards, the immutable systems would soon end up being one.

02:20pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest G
  1. Recommended Discovery
    The participant started using Fedora Linux on their friend's recommendation before moving on to join many parts of the community.
  2. Contemporary Relevance
    For a general purpose operating system, it is important to have access to recent updates in the rapidly evolving software landscape with AI.
  3. Improving Experience
    They sought Fedora Linux as a user friendly operating system and its versatility and stability are what keeps drawing users towards it.
  4. Welcoming Community
    The openness and patience of the mentoring members made them want to stay back in the community and keep helping in their ways.
  5. Friends Foundation
    From Friends, Features, Freedom and First – they preferred the Friends foundation the most as it resonated with why they contribute here.
  6. General Usability
    Instead of treating zero price as an excuse for poor usability, open source should invest more into design thinking and user experience.

02:34pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest H
  1. Better Performance
    A third year engineering student from PES University Bengaluru went from Microsoft Windows to Fedora Linux for its lightweightness.
  2. Installation Experience
    The setup process was relatively straightforward with the Anaconda WebUI but needed more troubleshooting for fingerprint readers etc.
  3. Community Resources
    Using the official subreddit and Fedora Discussions for initial issues, they gradually began answering questions from fellow members.
  4. Contributing Back
    After being introduced to FAS accounts and Join SIG, they intend to contribute more into updating documentation and other resources.
  5. Free Alternatives
    They had found home in the LibreOffice Suite and are appreciative of the open formats to help collaborate with other platforms equally.
  6. Difficult Balance
    From an over-involved experience of Microsoft Windows, they mentioned how Fedora Linux stayed out of their way while they worked.
  7. Exploring Editions
    They were introduced to the multiple variants and distinct editions of Fedora Linux for various purposes like servers and embedded etc.
  8. Encouraging Contributors
    They made it a point to promote Fedora Linux among their circles as a means to give back to the free and open source software resources.
  9. Exploration Decade
    Another participant explored over fifty alternatives in the previous decade before going with a custom build of Manjaro Linux now.
  10. Experienced Perspectives
    With an appreciation for Fedora Linux's overall simplicity and software availability, they are looking forward for image mode.
  11. Immutable Appeal
    Fedora Silverblue and other immutable alternatives helped shape consumer operating systems like SteamOS with a similar architecture.
  12. Problem Solving
    Multiple individuals can come together to solve problems that can be iterated upon by others, thus finding strength in the community.
  13. User Generated
    A great example was that of Arch User Repository (AUR) and Collection of Private Repositories (COPR) to allow for that to happen.
  14. Hardware Compatibility
    When official companies hold back their hardware devices, community members have come together to deliver solutions for the same.
  15. Vendor Partnerships
    Partnering with Slimbook, Lenovo, Framework and others have allowed Fedora Linux to be available out-of-the-box in the laptops.
  16. Innovative Stability
    The conversation concluded with recognizing how Fedora Linux balances innovation and stability at the cost of missing release dates.

03:00pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest I
  1. Developer First
    Since using it for almost over two years now, they appreciated the recent build updates that Fedora Linux provided for development.
  2. Update Frequency
    Frequent updates every after six months can be offputting for some, but that is exactly what makes them recommend Fedora Linux.
  3. Experimental Discovery
    From using GNU/Linux distributions on Raspberry Pi to daily driving Fedora Linux on resource limited hardware devices, they grew.
  4. Community Career
    They plan to make a career in free and open source software communities at some time after learning the ropes from the mentors.

03:08pm IST

Community Connection Part Two - IndiaFOSS 2026
Manifest J
  1. Technological Compliance
    The two participants from the legal sector assisted the startups establishing platforms and navigating regulatory challenges.
  2. Legal Oversight
    Software companies sometimes avoid compliance requirements if they comply with one jurisdiction since it costs a fortune.
  3. Generated Misuse
    Generated terms of services without a foundational understanding and substantial review can only end up in a bad manner.
  4. Professional Expertise
    Lawyers invest considerable efforts in deep research and due diligence to understand the clients produce before providing advice.
  5. Limitation Violations
    SaaS providers copy products from competing services by barely making superficial changes rather than addressing issues.
  6. Regulatory Responsibility
    Financial pressure should not be an excuse to minimize necessary legal expenditure, as an oversight could cause great fines later.

Glory or Gold

Posted by Adam Price on 2026-11-07 12:00:00 UTC

Glory or Gold

2026-11-07

Crawling across the sky
All of my crew and I are
Wanted for the highest form of treason

For questioning authority
Demanding we sweat and bleed
And slave our lives away, then call it freedom

So hoist up the Jolly Roger
We’re taking a ride
Take back the life that they denied

For glory or gold
We sail across the galaxy
Our sovereign starship flying free
Forever, our treasure
Taken from plutocracy
We’ve all got mouths to fucking feed
So it’s a pirate’s life for me

So you’ve got to make a choice
If you will raise your voice
For all of those who suffer now in silence

‘Cause the crown would never hesitate
To laugh while we suffocate
Then ask us why we must reply with violence

So hoist up the Jolly Roger
We’re taking a ride
Take back the life that they denied

For glory or gold
We sail across the galaxy
Our sovereign starship flying free
Forever, our treasure
Taken from plutocracy
We’ve all got mouths to fucking feed
So it’s a pirate’s life for me!
Yeah! It’s a pirate’s life for me!


Lyrics from Glory or Gold by Galactikraken & Jonathan Young

Server reboots

Posted by Fedora Infrastructure Status on 2026-11-06 21:00:00 UTC

We will be rebooting our vpn hub / smtp gateway / bastion hosts in order to apply a new kernel to mitigate possible CVEs.

The outage should hopefully only take a few minutes.

forge.fedoraproject.org is down

Posted by Fedora Infrastructure Status on 2026-11-06 11:00:00 UTC

The forge.fedoraproject.org is down because of space issue. We are currently working on fixing it. You can watch the progress in https://matrix.to/#/#forge:fedoraproject.org

🎲 PHP version 8.4.28RC1 and 8.5.13RC1

Posted by Remi Collet on 2026-11-06 05:47:00 UTC

Release Candidate versions are available in the testing repository for Fedora and Enterprise Linux (RHEL / CentOS / Alma / Rocky and other clones) to allow more people to test them. They are available as Software Collections, for parallel installation, the perfect solution for such tests, and as base packages.

RPMs of PHP version 8.5.13RC1 are available

  • as base packages in the remi-modular-test for Fedora 43-45 and Enterprise Linux ≥ 8
  • as SCL in remi-test repository

RPMs of PHP version 8.4.23RC1 are available

  • as base packages in the remi-modular-test for Fedora 43-45 and Enterprise Linux ≥ 8
  • as SCL in remi-test repository

ℹ️ The packages are available for x86_64 and aarch64.

ℹ️ PHP version 8.3 is now in security mode only, so no more RC will be released.

ℹ️ Installation: follow the wizard instructions.

ℹ️ Announcements:

Parallel installation of version 8.5 as Software Collection:

yum --enablerepo=remi-test install php85

Parallel installation of version 8.4 as Software Collection:

yum --enablerepo=remi-test install php84

Update of system version 8.5:

dnf module switch-to php:remi-8.5
dnf --enablerepo=remi-modular-test update php\*

Update of system version 8.4:

dnf module switch-to php:remi-8.4
dnf --enablerepo=remi-modular-test update php\*

ℹ️ Notice:

  • Version 8.5.13RC1 is in Fedora rawhide for QA
  • Version 8.6.0RC5 is also available in the repository
  • EL-10 packages are built using RHEL-10.2 and EPEL-10.2
  • EL-9 packages are built using RHEL-9.8 and EPEL-9
  • EL-8 packages are built using RHEL-8.10 and EPEL-8
  • oci8 extension uses the RPM of the Oracle Instant Client version 23.26 on x86_64 and aarch64
  • intl extension uses libicu 78.3 and can take advantage of icu-tzdata
  • RC version is usually the same as the final version (no change accepted after RC, exception for security fix).
  • versions 8.4.19 and 8.5.4 are planed for March 12th, in 2 weeks.

Software Collections (php84, php85)

Base packages (php)

Nebula from Ansible

Posted by Fabio Alessandro Locati on 2026-11-05 23:00:00 UTC

For many years, I have managed all my systems with Ansible. For a similar amount of time, I have used Nebula as my VPN of choice, so I can always connect securely to all my systems, even on the move.

There are no official Ansible modules for Nebula, so over the years many people asked me how I manage it. I changed my approach over time. Although my previous iterations worked, I wasn’t satisfied enough to share the details. I’m now at a point where I think the process is fairly good, so here I am.

What’s new for Fedora Atomic Desktops in Fedora 45

Posted by Timothée Ravier on 2026-11-02 23:00:00 UTC

Fedora 45 is now available ! 🎉 So let’s see what this new release for the Fedora Atomic Desktops variants includes for Silverblue, Kinoite, Sway Atomic, Budgie Atomic and COSMIC Atomic.

Note: You can also read this post on the Fedora Magazine.

Changes for all Atomic Desktops

Completed the migration to the new Fedora forge

Everything related to the Atomic Desktops now resides in the atomic-desktops organization.

The only remaining repo on GitLab.com/fedora is the one used to build the unofficial bootable container images (gitlab.com/fedora/ostree/ci-test). The migration of this repo is planned as well.

Anaconda Web UI

The Atomic Desktops installer ISOs now use the new Anaconda WebUI. This follows the same change that occured for Fedora Workstation 42 and Fedora 43 Spins.

This also enables remote installation of a system using a Web browser on another machine over HTTPS.

See the Fedora Change pages for the switch to the WebUI and for Web based remote installations.

Installer images (ISO) and disk images built by Image Builder

The installer images (ISO) are now built by Image Builder. While there should not be any immediate visible changes, this will help us move to the bootable container images in the future.

This also enables us to offer pre-installed disk images for Silverblue and Kinoite. Those images are currently in preview and only those variants are covered for now. They are the only ones with a first boot experience from a disk image.

See the Fedora Change page for further information.

General Fedora changes worth noting

Those changes are part of the general set of changes that come with Fedora 45 and that are worth noting for Atomic Desktops users:

What’s new in Silverblue

Fedora Silverblue comes with the latest GNOME 51 release.

For more details about the changes alongside GNOME 51, see What’s new in Fedora Workstation 45 on the Fedora Magazine.

What’s new in Kinoite

Fedora Kinoite ships with Plasma 6.7, Frameworks 6.31 and Gear 26.08.

Plasma 6.8 is expected to land right after the release.

See also What’s new in Fedora KDE Plasma Desktop 45 on the Fedora Magazine.

What’s new in Sway Atomic

Fedora Sway Atomic comes with the latest 1.12 Sway release.

What’s new in Budgie Atomic

Fedora Budgie Atomic comes with the brand new version 10.10.3 of Budgie Desktop: New Favorites in Budgie Menu, re-introduced Keyboard applet with Wayland support, massive improvements to our desktop view, primary monitor selection, and more!

What’s new in COSMIC Atomic

Fedora COSMIC Atomic comes with the 1.10.0 release of the COSMIC desktop.

Universal Blue, Bluefin, Bazzite, Aurora and secureblue

Our friends in the Universal Blue project (Bazzite, Bluefin, Aurora) have prepared the update to Fedora 45. Look for upcoming announcements in their Discourse.

As always, I heavily recommend checking them out, especially if you feel like some things are missing from the Fedora Atomic Desktops and you depend on them (NVIDIA drivers, extra media codec, out of tree kernel drivers, etc.).

If you are interested in more security focused variants, I recommend taking a look at the secureblue project.

What’s next

Roadmap to Bootable Containers and bootc / CoreOS / Atomic unification

A lot of work is happening to make the transition to Bootable Containers as smooth as possible for our existing users. You can look at the roadmap for this transition at atomic-desktops#26.

Most of the progress in this release cycle was (again) focused on getting our bootable container images ready for general consumption in Fedora. A part of this work is being able to build them reliably in the Fedora Infra.

The people involved in the bootc, CoreOS and other Atomic variants are working on this effort as part of the new Atomic SIG. See atomic#137 and the project board.

Making it easier to derive images into Fedora Remix images

Work is in progress to make it easier to create derived container images from the Fedora Atomic Desktops images, notably in order to comply with the logo and branding policy.

Once this is ready, we may start publishing “Fedora Remix” branded container images of the Fedora Atomic Desktops. Those images would not include official Fedora branding and would thus be better suited for projects that want to layer their changes on top.

See atomic-desktops#125 and atomic-desktops#132.

Helping us with a few nasty bugs

If you are interested in contributing to Fedora Atomic Desktops, here are some bugs that we will have to fix in the short term. We would greatly appreciate help with:

  • Fixing root mount options (atomic-desktops#72): This is a long standing and mostly invisible bug that impacts performance.

  • Moving away from nss-altfiles (atomic-desktops#108): This is another long standing source of issues that new users regularly face.

Where to reach us

We are looking for contributors to help us make the Fedora Atomic Desktops the best experience for Fedora users.

I am tired

Posted by Kushal Das on 2026-11-05 18:39:59 UTC

I am sure I am not the only in this situation. There are more Open Source maintainers and defenders who are in the same situation. From last July I started poking into various libraries/projects/deployments of open source projects to find vulnerabilites, and it became very tiring 16+ hours long days. As of today morning I found 90+ such issues, many are in projects written or used by Sunet, many has other bigger userbase too.

The things I am poking at are boring Infrastructure pieces. "National Research and Education Network/NREN" (s) in every country are not the top receivers of grant money. Small number of people working years after years to keep the infrastructure on.

And not many are that lucky to have access to the modern LLMs or knowldge on how to use them to find and fix issues. I am lucky and thankful to Anthropic and OpenAI that they provided me with access to latest models with capabilities to do this work. But, not many has it, this crates too much pressure in my mind, and for sure friends told me similar stories (in other fields). To defend Sweden (or your respective country) we will need more capabilites and compute/hardware and people willing to do this work. Where we are not dependent on another country's political views to defend our own country.

Many will say open weight models will solve this. If you only think about capabilities, yes they are catching up. Funniest part for me was that I used an open weight model and found 4 different zero days in 4 java libraries (they are all now fixed) and chained them to bypass validation of particular checks for digital signatures as my first finding (using LLMs) back in July. But, using open weights are either not allowed at every place or folks don't have hardware. We need powerful hardware to be able to defend. A lot of decisions have to made in various levels of our societies to make this happen. And I don't think we will not see much progress so easily.

On the other hand attackers using $25 and access to same capabilities to attack. Nation state level actors are now many more times efficient due to both brain power and money they can spend.

I hope the pace of finding new bugs will come down a bit in 2 years, but not sure how many of us will not be burnt out by then.

Note: many of you may ask me about technical details of the findings or what I am using specifically. That would require multiple other posts for me to explain, but you can just start poking with whatever you have. For example today morning's finding to another big project was using just Pi. No special sauce. Just poking and providing input to the model to guide it. But if I just go by numbers, then OpenAI models helped me the most in finding vulnerabiities and then to write exploits to demonstate to the maintainers. I am missing the capabilties to do proper pentesting though.

Community Connection Part One - IndiaFOSS 2026

Posted by Akashdeep Dhar on 2026-11-05 18:30:00 UTC
Community Connection Part One - IndiaFOSS 2026

We took some time to interact with the booth visitors at the IndiaFOSS 2026 conference's Red Hat Community Booth. While representing Fedora Project on the event grounds and handing out special swags, we were the conduits for the community's sentiments both as users and contributors to free and open source software projects like that of ours.

09:36am IST

Community Connection Part One - IndiaFOSS 2026
Manifest A
  1. Zorin OS vs. Fedora Linux
    Both use GNOME and yet Zorin OS offers a more Windows-like experience out of the box, while Fedora Linux provides a comparatively stock GNOME experience.
  2. Software Freshness
    Zorin benefits from Ubuntu's stability, but its software packages can be considerably older as compared to Fedora Linux where updates arrive much faster after testing.
  3. Fedora's Positioning
    The distribution bridges the contentious gap between beginner friendly distributions and faster moving ones, by balancing software freshness and overall stability.
  4. Raspberry Pi
    Fedora support ARM64, and various other architectures, including Raspberry Pi, but the releases can take longer to arrive sometimes due to the closed kernel sources.
  5. Experimentation Encouraged
    Fedora Linux is worth trying on any hardware for general purpose users but there is no need to replace whatever works if it already meets your requirements.
  6. Foundational Freedom
    Users should explore GNU/Linux distributions based on curiosity and learning rather than simply switching for the sake of it to face workflow problems.
  7. Distribution Movements
    Fedora Linux is a natural intermediate step before experimenting with more advanced GNU/Linux distributions like Arch Linux, Gentoo Linux and others.
  8. Experimental Education
    College students should consider experimenting with GNU/Linux distributions to learn the internal parts without risking their everyday systems in the process.
  9. Generative Enhancements
    Generative systems should be treated as a tool that enhances human capabilities rather than a replacement for human involvement in software development.
  10. Usage Responsibility
    Generated codebase require proper requirements gathering, human oversight and deep auditing to ensure that the result does not lead to poor outcomes.
  11. Learning Fundamentals
    Beginners should avoid excessive dependence on AI tooling, in order to help long-term capabilities and build strong fundamentals with basic documentation.
  12. Dependent Consumerism
    Free services can create dependency with providers potentially introducing restrictions with enshittification, so users should remain mindful of privacy concerns.
  13. Privacy Engagements
    In Fedora Project community, we value meaningful conversations and useful feedback over collecting emails in exchange for our promotional merchandise.
  14. Getting Started
    Documentation writing and quality assurance are excellent beginner starting points, as they help with bridging the gap between users and contributors.
  15. Advanced Contributions
    They can gradually move towards issue tracking, design creation, codebase writing and community management, as they grow familiar with the ecosystem.
  16. Container Security
    Podman comes bundled with Fedora Linux with the support for rootless execution of container payloads along with first class SELinux support.

10:00am IST

Community Connection Part One - IndiaFOSS 2026
Manifest B
  1. Ubuntu Linux vs. Fedora Linux
    Fedora Linux releases every six months while Ubuntu LTS prioritizes five year support and hence, the former delivers newer software much faster.
  2. Upstream First
    Fedora Linux aims to ship upstream updates within a shorter timeframe, often around a week after release, whereas Ubuntu paces behind for stability.
  3. Innovation Focus
    Fedora Linux distinguishes itself with adopting emerging technologies and leading the pack before they become mainstream across other distributions.
  4. Controversial Standards
    Systemd adoption was controversial at its time, but it soon found its way into major contemporary GNU/Linux distribution shortly after our example.
  5. Enterprise Security
    Using SELinux, Fedora Linux provides strong system-level protection, with Podman for lightweight rootless container execution against Docker.
  6. Staying Current
    Newer development tools with Fedora Linux releases help users and builders to cater for the stakeholders of today and tomorrow, and not of yesterday.

10:08am IST

Community Connection Part One - IndiaFOSS 2026
Manifest C
  1. Leading Edge
    Fedora Linux prioritizes delivering recent software updates while maintaining usability and stability of the general GNU/Linux distribution experience.
  2. Balancing Updates
    Fedora Linux aims to deliver updates relatively quickly, typically within a week of its upstream release, while holding back broken updates until fixed.
  3. Community Maintenance
    With a heavy reliance on voluntary developers and community maintainers, Fedora Linux attempts shipping updates as quickly as possible.
  4. Security Updates
    CVE addressing security patches are prioritized and pushed as soon as they are ready to be shipped to minimize the vulnerability exposure period.
  5. Quality Assurance
    An integrated update management system allows community members to test proposed updates before wider GNU/Linux distribution adoption ensues.
  6. Getting Involved
    Contributors can help test updates without from virtual machines and live environment without replacing their existing operating systems here.

10:16am IST

Community Connection Part One - IndiaFOSS 2026
Manifest D
  1. Educational Institutions
    Fedora Linux is adopted in St. Joseph Engineering College, Mangalore across their computer systems, for student development and general purpose.
  2. Contribution Pathways
    One need not be a programmer to contribute to Fedora Project, when they can do so through designing, documentation, testing, triaging and other ways.
  3. Packaging Technologies
    Flatpak's fully open-source nature and support for federated infrastructure is preferred over Snap's centralized software serving approach by the folks.
  4. Upstream Innovation
    Fedora Linux introduces technologies such as Pipewire and Wayland that eventually greatly influence other GNU/Linux distributions down the road.
  5. Enterprise Contributions
    Fedora Linux serves as the upstream foundation for CentOS Stream and ultimately, Red Hat Enterprise Linux so the contributors have the agency.
  6. Career Opportunities
    Students are encouraged to explore opportunities through Red Hat's career portal and learn about various roles within the organization communities.

10:26am IST

Community Connection Part One - IndiaFOSS 2026
Manifest E
  1. Agent Security
    How do we identify compromised polluted autonomous agents within a swarm of AI agents operating towards a shared initially provided goal?
  2. Ring Architecture
    How elevated memory access privileges could help understand the potential fault when malicious activity reaches the deeper memory layers?
  3. Without Logging
    Identifying malicious autonomous agents without execution footprints can be quite the challenge with the entire ecosystem being treated as a black box.
  4. Compromise Detection
    Determining memory access history, and isolating affected regions could help prevent further compromise, which was also in Anthropic's research.

10:48am IST

Community Connection Part One - IndiaFOSS 2026
Manifest F
  1. CentOS Evolution
    From having limited upstream contribution to having unlimited midstream exposure, CentOS Stream helped evolve the entire ecosystem.
  2. Midstream Bridge
    CentOS Stream helps bridge Fedora Linux and Red Hat Enterprise Linux by being an intermediate platform for development and security.

10:56am IST

Community Connection Part One - IndiaFOSS 2026
Manifest G
  1. Personal Experience
    Using Fedora Linux first as daily drivers motivates people to contribute back whenever they face issues or identify opportunities in their tools.
  2. Giving Back
    Support received by Fedora Project motivates people to contribute in whatever manner they can, while solving real world problem statements.
  3. General Affordability
    In various government schools, free and open source software can make technology accessible to students' and teachers' existing devices.
  4. GNU/Linux Entertainment
    Various people still depend on Microsoft Windows for graphic drivers and video games particularly from vendors like AMD and/or NVIDIA.
  5. Community Driven
    Communities collaborate to address security issues and software bugs that have been identified by users who have faced similar incidents.
  6. Starting Small
    People should not feel pressured to become core maintainers immediately when they could start small with fellow contributors to rely on.

11:20am IST

Community Connection Part One - IndiaFOSS 2026
Manifest H
  1. StratOS Linux
    Using Bedrock Linux to integrate components from multiple alternatives to allow users to combine packages, kernels, components in here.
  2. Kernel integration
    Fedora Linux's official kernel was demonstrated to be integrated with custom dotfiles and SwayFX environment to include DNF installer.

11:26am IST

Community Connection Part One - IndiaFOSS 2026
Manifest I
  1. Battleship Gaming
    Gridlock, a battleship inspired videogame written purely in Rust and GTK4 UI with minimal memory footprint was demonstrated live.
  2. Development Environment
    They mentioned how Fedora Linux enabled them to build on the most recent codebase and toolkit, with just how fast we ship the updates.

11:34am IST

Community Connection Part One - IndiaFOSS 2026
Manifest J
  1. Open Background
    With humble start from beginner alternatives to moving into NixOS from the first year of the college education, NixOS was used for four years.
  2. Blue Experience
    After initial experiments with Manjaro Linux, Fedora Linux outgrew the popularity for its mature ecosystem and maintenance practices it has.
  3. NixOS Adoption
    Finally settling into NixOS after years of distrohopping, it was realized that the NixOS workflow suits them the best with Fedora Linux after it.
  4. Declarative Configuration
    Like NixOS, Fedora Linux's Atomic Variants also support declarative configuration, thus providing them alternatives for trying it again.
  5. Contribution Potential
    Interest was expressed in helping Fedora Linux evolve more on system configuration drawing inspiration from contemporary alternatives.
  6. Proposed Pathways
    With an encouragement to document ideas, identifying issues and opening discussions through the active Fedora Atomic forums, they departed.

Test syslog-ng before the 4.13 release

Posted by Peter Czanik on 2026-11-05 12:44:44 UTC

Version 4.13 of syslog-ng is expected to be released in the coming weeks. There are fixes and enhancements even in the core of syslog-ng. Testing of the latest nightly builds is much appreciated.

Thousands of automatic tests check each source code change before they are merged. Still, nothing can replace some manual testing with real-world configurations. Syslog-ng runs on a wide variety of systems, from RHEL 8 to Fedora Rawhide, FreeBSD, MacOS and others. It supports everything from simple file destinations to various network destinations, including not just syslog, but also OpenTelemetry or ElasticSearch. No automatic testing can fully cover all these variations.

I collected below just some of the highlights:

  • JSON Key Ordering Control
  • gELF Format Fixes
  • AWS CloudWatch Logs HLC Destination
  • Exponential Reconnect Backoff with Jitter
  • PKCS#12 Password Support
  • Debug Macro Storage Control

Read more at https://www.syslog-ng.com/community/b/blog/posts/test-syslog-ng-before-the-4-13-release

syslog-ng logo

Passkeys work in Miniflux now

Posted by Tomasz Torcz on 2026-11-04 09:51:54 UTC

Few months ago, a collegue had a question for me. He started uneasy, apologizing that he does not want to neither age-profile nor offend me in any capacity. But I seemed like a person who would know. He continued with the question: what RSS reader do I use?

Before reporting him to HR, I said I've been using Google Reader until recently. But as it was promoted to Google Cementery, I've migrated to Netvibes, which also bit the dust. Now I use Miniflux, BTW.

Miniflux is very nice, with one exception: Passkeys support was broken. It required a login-name entry before attempting a Passkey login. As I have Miniflux connected to the home SSO, there was no login entry to use.

It was fixed in v2.3.5! Now Passkey login works as expected. Smooth!

Nb. I also realised, that I have not used my physical security keys for months, thanks to Passkeys everywhere.

Day Two - IndiaFOSS 2026

Posted by Akashdeep Dhar on 2026-11-03 18:30:00 UTC

Theme

Experience

While I had enough respite to prepare for the first day of IndiaFOSS 2026, I could not say the same for 27th September 2026. After returning to SRS Springs And Spa Hotel late the previous night, I found myself horrifically awakened by the noise of running water coming from the bathroom. Creeping cautiously towards the source of the sound while trying to shake off my headache, I was relieved when I realized that the room had not been intruded upon by anyone. It was the Jet Spray Faucet Device that had suffered a leak due to the change in water pressure, and that was where the noise was coming from. I was facing a mixed bag of emotions as I rang up the reception desk at around 0700am Indian Standard Time. I was glad that I had been jolted awake by the noise, as I did not have an alarm set for the morning, but I also had to waste some time dealing with the plumbing issue in the room before I could begin preparing for the day.

I did not realize how quickly my mind moved from finding something to use as a weapon against a potential intruder to gathering the necessary supplies for setting up the Red Hat Community Booth. Keeping myself immensely occupied helped in spades to shake off the sudden shock, and since Samyak Jain had tapped out of the 0930am Indian Standard Time booth presence, it was down to me alone to get things going. Deferring the cleanup of the leakage until after I was gone, I left for breakfast at around 0830am Indian Standard Time to be greeted by a (comparatively better) assortment of morning munchies. Grouped with Aaloo Bonda, Chholey Bhature, French Toasts, and Medu Vada, the menu selection was a whole lot more pronounced than the day before. I ordered myself an Uber ride at around 0900am Indian Standard Time, and within the next fifteen minutes or so, I found myself at the NIMHANS Convention Center Bengaluru.

Since it was Sunday, there was no flagship Bengaluru traffic to battle through, and along with me, Jaison Raju also happened to be the first one at the Red Hat Community Booth. I checked in with the likes of Rajan Shah and Deepesh Nair, who planned on coming later that day, before setting up the swags and laptops at the booth. I knew that I had to pace myself while addressing the booth visitors on that day, given how I had a numb voice and dry throat from the day before. The medicine intake allowed me to push through the pain, and I was more determined than ever to exhaust the inventory of Ceramic Branded Coffee Mugs and Round Magnet Pin Combos by the end of the day. For a change, I also brought my microphone to record our conversations with consenting community booth visitors. As an underlying principle, we were more interested in the feedback than in the contact details of the folks interacting with us.

Thankfully, we had a slower-moving community crowd on that day, which allowed us to stand our ground until our representational backup from the Ansible team and Tekton team arrived at around 1100am Indian Standard Time. Sudhir Dharanendraiah and Samyak came about half an hour later to help Jaison and me with the visitor interactions. Just like the day before, the swag offerings from Fedora Project ended up being indeed great conversation starters, not just for our community but also for those surrounding us. We also came upon some familiar faces from our community, like Muneer S., who used to contribute to Fedora Project at that time. Offloading conversations to Samyak and regularly keeping hydrating myself allowed us to keep going until lunchtime. Chats related to CentOS Stream's midstream value, the utility of generative tooling, and the open source software careers were, more or less, the stars of our presence on that day.

Right before we headed for lunch at around 0130pm Indian Standard Time, we met with Saumilli Dutta, whom we had met at DevConf.IN 2026 and GNOME Asia 2024. After meeting some more familiar faces from the Maintainer Summit and taking another round of group photographs, we headed for the lunch break, where we ran into Shivani Bhardwaj after having previously met her during FOSSAsia 2026. Finishing off our catch-up chats and okayish meals, I took the time to explore the venue offerings before heading back to our community booth. With Deepesh heading back much sooner, we were helped by Veer Kumar Patil with his professional lossless recording instrument. Using designated mics for the interviewer and interviewee allowed us to cut through the venue noise and retain a great deal of what was actually conveyed so that it could be transcribed accurately using generative tooling, once we were back.

After a visit from our FOSSUnited friend, Ansh Arora, we were also joined by the legal ambassadors of the Digital Personal Data Protection Act, Mrinmayee Nagarsenkar, Biju Nair and Dakshana AM, whom we felicitated with the Ceramic Branded Coffee Mugs. We had immense respect for what that they had been doing, and they also provided us valuable feedback as general-purpose computer users. With nothing significant planned for the evening, we cross-promoted our swag at the FOSSUnited helpdesk community booth who appreciated our swag supplies. At around 0530pm Indian Standard Time, it was about time for us to pack things up at our community booth, with us finally managing to finish off the offerings inventory. Connecting with Ramakrishna Yekulla, Shivraj Patil, and Gaurav Kamathe at the coffee stand, Samyak and I kept looking for an Uber ride back to the hotel to finally complete this event as a grand success.

🎲 📝 Redis version 8.12

Posted by Remi Collet on 2026-11-03 16:07:00 UTC

RPMs of Redis version 8.12 are available in the remi-modular repository for Fedora ≥ 43 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

⚠️ Warning: this is a pre-release version not ready for production usage.

1. Installation

Packages are available in the redis:remi-8.8 module stream.

1.1. Using dnf4 on Enterprise Linux

# dnf install https://rpms.remirepo.net/enterprise/remi-release-$(rpm -E %rhel).rpm
# dnf module switch-to redis:remi-8.12/common

1.2. Using dnf5 on Fedora

# dnf install https://rpms.remirepo.net/fedora/remi-release-$(rpm -E %fedora).rpm
# dnf module reset  redis
# dnf module enable redis:remi-8.12
# dnf install redis --allowerasing

You may have to remove the valkey-compat-redis compatibility package.

2. Modules

Some optional modules are also available:

These packages are weak dependencies of Redis, so they are installed by default (if install_weak_deps is not disabled in the dnf configuration).

The modules are automatically loaded after installation and service (re)start.

The modules are not available for Enterprise Linux 8.

3. Statistics

redis

redis-bloom

redis-json

redis-timeseries

What’s New for Fedora Atomic Desktops in Fedora Linux 45

Posted by Fedora Magazine on 2026-11-03 14:28:00 UTC

Fedora 45 is now available! 🎉 So let’s see what this new release for the Fedora Atomic Desktops variants includes for Silverblue, Kinoite, Sway Atomic, Budgie Atomic and COSMIC Atomic.

Changes for all Atomic Desktops

Completed the migration to the new Fedora forge

Everything related to the Atomic Desktops now resides in the atomic-desktops organization.

The only remaining repo on GitLab.com/fedora is the one used to build the unofficial bootable container images (gitlab.com/fedora/ostree/ci-test). The migration of this repo will occur in the future, as well.

Anaconda Web UI

The Atomic Desktops installer ISOs now use the new Anaconda WebUI. This follows the same change that occurred for Fedora Workstation 42 and Fedora 43 Spins.

This also enables remote installation of a system using a Web browser on another machine over HTTPS.

See the Fedora Change pages for the switch to the WebUI and for Web based remote installations.

Installer images (ISO) and disk images built by Image Builder

The installer images (ISO) are now built by Image Builder. While there should not be any immediate visible changes, this will help us move to the bootable container images in the future.

This also enables us to offer pre-installed disk images for Silverblue and Kinoite. Those images are currently in preview and only those variants are covered for now. They are the only ones with a first boot experience from a disk image.

See the Fedora Change page for further information.

General Fedora changes worth noting

The following changes are part of the general set of changes that come with Fedora Linux 45 and are worth noting for Atomic Desktops users:

What’s new in Silverblue

Fedora Silverblue comes with the latest GNOME 51 release.

For more details about the changes alongside GNOME 51, see What’s new in Fedora Workstation 45 on the Fedora Magazine.

What’s new in Kinoite

Fedora Kinoite ships with Plasma 6.7, Frameworks 6.31 and Gear 26.08.

Plasma 6.8 is expected to land right after the release.

See also What’s new in Fedora KDE Plasma Desktop 45 on the Fedora Magazine.

What’s new in Sway Atomic

Fedora Sway Atomic comes with the latest 1.12 Sway release.

What’s new in Budgie Atomic

Fedora Budgie Atomic comes with the brand new version 10.10.3 of Budgie Desktop: New Favorites in Budgie Menu, re-introduced Keyboard applet with Wayland support, massive improvements to our desktop view, primary monitor selection, and more! See the 10.10.3 Budgie release announcement.

What’s new in COSMIC Atomic

Fedora COSMIC Atomic comes with the 1.10.0 release of the COSMIC desktop.

Universal Blue, Bluefin, Bazzite, Aurora and secureblue

Our friends in the Universal Blue project (Bazzite, Bluefin, Aurora) have prepared the update to Fedora 45. Look for upcoming announcements in their Discourse.

As always, I heavily recommend checking them out, especially if you feel like some things are missing from the Fedora Atomic Desktops and you depend on them (NVIDIA drivers, extra media codec, out of tree kernel drivers, etc.).

If you have an interest in more security focused variants, I recommend taking a look at the secureblue project.

What’s next

Roadmap to Bootable Containers and bootc / CoreOS / Atomic unification

A lot of work is happening to make the transition to Bootable Containers as smooth as possible for our existing users. You can look at the roadmap for this transition at atomic-desktops#26.

Most of the progress in this release cycle was (again) focused on getting our bootable container images ready for general consumption in Fedora. A part of this work is being able to build them reliably in the Fedora Infra.

The people involved in the bootc, CoreOS and other Atomic variants are working on this effort as part of the new Atomic SIG. See atomic#137 and the project board.

Making it easier to derive images into Fedora Remix images

Work is in progress to make it easier to create derived container images from the Fedora Atomic Desktops images, notably in order to comply with the logo and branding policy.

Once this is ready, we may start publishing “Fedora Remix” branded container images of the Fedora Atomic Desktops. Those images will not include official Fedora branding and will thus be better suited for projects that want to layer their changes on top.

See atomic-desktops#125 and atomic-desktops#132.

Helping us with a few nasty bugs

If you have an interest in contributing to Fedora Atomic Desktops, here are some bugs that we will have to fix in the short term. We would greatly appreciate help with the following issues from the ticket tracker:

  • Fixing root mount options (atomic-desktops#72): This is a long standing and mostly invisible bug that impacts performance.
  • Moving away from nss-altfiles (atomic-desktops#108): This is another long standing source of issues that new users regularly face.

Where to reach us

We are looking for contributors to help us make the Fedora Atomic Desktops the best experience for Fedora users. The following are Matrix rooms that may be of interest to potential contributors:

Migrating away from unmaintained NetworkManager VPN plugins (vpnc and fortisslvpn)

Posted by Fedora Magazine on 2026-11-03 14:00:00 UTC

Two legacy NetworkManager VPN plugins—NetworkManager-vpnc and NetworkManager-fortisslvpn—are retiring and will be obsolete, starting in Fedora Linux 45. This is part of ongoing system maintenance and security cleanup.

If you use Virtual Private Networks (VPNs) to connect to remote workplace or enterprise networks, take note of this upcoming change in NetworkManager package availability.

This article contains information about what you need to know. It covers why these plugins are being retired, how this affects your current setup, and how to migrate your VPN connections to actively supported alternatives.

Why retire these plugins?

Both NetworkManager-vpnc and NetworkManager-fortisslvpn are unmaintained.  Furthermore, the published issues allow LPE through malicious VPN profiles as well as legacy privilege-handling bugs in older VPN helper scripts, which pose security risks to local systems. Further information is available in this blog post.

To ensure Fedora Linux users remain secure and backed by active upstream maintainers, the Fedora Engineering and Steering Committee (FESCo) and NetworkManager maintainers agreed to retire these unmaintained plugins in favor of modern, secure alternatives already available in Fedora repositories.

Overview of changes and migration paths

Retired PluginProtocol / Network TypeMigration TargetStatus & Recommendation
NetworkManager-fortisslvpnFortinet SSLVPNNetworkManager-openconnectopenconnect supports the older PPP-based Fortinet protocols natively and is actively maintained.
NetworkManager-vpncCisco IPsec (IKEv1)NetworkManager-libreswanlibreswan handles the same IKEv1 protocol family and is directly maintained by the NetworkManager team.

Step-by-Step Migration Guide

1. Fortinet SSLVPN Users (fortisslvpn → openconnect)

If you currently rely on Fortinet SSLVPN tunnels, switch to the NetworkManager-openconnect plugin.

  1. Install the OpenConnect NetworkManager plugin:
    Bash
    sudo dnf install NetworkManager-openconnect

  2. Open Settings → Network (or KDE System Settings → Connections).
  3. Click + to add a new connection and select Multi-protocol VPN client (openconnect).
  4. Set the protocol dropdown to Fortinet SSL VPN, input your gateway address and authentication details, and save the profile.
  5. Once verified, remove the legacy package:
    Bash
    sudo dnf remove NetworkManager-fortisslvpn

2. Cisco IPsec / IKEv1 Users (vpnc → libreswan)

If you use legacy Cisco IPsec VPN tunnels, migrate your connections to NetworkManager-libreswan.

  1. Install the Libreswan NetworkManager plugin:
    Bash
    sudo dnf install NetworkManager-libreswan

  2. You may need to create file /etc/ipsec.d/ikev1.conf with this content:
    config setup
    ikev1-policy=accept

    This enables the deprecated IKEv1 protocol. Then restart ipsec.service. Note that the ipsec.service must be running, or the activation will fail.
  3. In your desktop network settings, add a new IPsec based VPN connection and select Type=IKEv1.
  4. Enter your gateway IP/domain, the group name enclosed in square brackets (e.g ‘[group]’), group password (pre-shared key), and user credentials corresponding to your previous vpnc configuration. You might have to tune IKE/ESP proposals, DH/PFS settings and routing requirements, which can be obtained from the gateway’s configuration and old vpnc logs.
  5. Test the connection, then remove the legacy package:
    Bash
    sudo dnf remove NetworkManager-vpnc

What happens during upgrades?

  • Fedora 43 & 44: Current installations retain their installed plugins so active connections will not abruptly break. However, there will be no further feature or security updates issued for vpnc or fortisslvpn.
  • Fedora 45+: The legacy packages are officially obsoleted by NetworkManager. An upgrade to Fedora 45 automatically removes NetworkManager-vpnc and NetworkManager-fortisslvpn, if they are installed.

We strongly encourage all users relying on these VPN types to test and migrate their connection profiles to openconnect or libreswan as soon as possible!

How to Rebase to Fedora Linux 45 on Silverblue

Posted by Fedora Magazine on 2026-11-03 14:00:00 UTC

Fedora Silverblue is an operating system for your desktop built on Fedora Linux. It’s excellent for daily use, development, and container-based workflows. It offers numerous advantages such as being able to roll back in case of any problems. If you want to rebase to Fedora Linux 45 on your Fedora Silverblue system, this article tells you how. It not only shows you what to do, but also how to revert things if something unforeseen happens.

Update your existing system

Prior to actually doing the rebase to Fedora Linux 45, you should apply any pending updates. Enter the following in the terminal:

$ rpm-ostree update

or install updates through GNOME Software and reboot.

Note

rpm-ostree is the underlying atomic technology that all the Fedora Atomic Desktops use. The techniques described here for Silverblue will apply to all of them with proper modifications for the appropriate desktop.

Rebasing using GNOME Software

GNOME Software shows you that there is new version of Fedora Linux available on the Updates screen.

First thing to do is download the new image, so select the Download button. This will take some time. When it is done you will see that the update is ready to install.

Select the Restart & Upgrade button. This step will take only a few moments and the computer will restart when the update has completed. After the restart you will end up in a new and shiny release of Fedora Linux 45. Easy, isn’t it?

Rebasing using terminal

If you prefer to do everything in a terminal, then this part of the guide is for you.

Rebasing to Fedora Linux 45 using the terminal is easy. First, check if the 45 branch is available:

$ ostree remote refs fedora

You should see the following in the output:

fedora:fedora/45/x86_64/silverblue

If you want to pin the current deployment (meaning that this deployment will stay as an option in GRUB until you remove it), you can do this by running this command:

# 0 is entry position in rpm-ostree status
$ sudo ostree admin pin 0

To remove the pinned deployment use the following command:

# 2 is entry position in rpm-ostree status 
$ sudo ostree admin pin --unpin 2

Next, rebase your system to the Fedora Linux 45 branch.

$ rpm-ostree rebase fedora:fedora/45/x86_64/silverblue

Finally, the last thing to do is restart your computer and boot to Fedora Linux 45.

How to roll back

If anything bad happens (for instance, if you can’t boot to Fedora Linux 45 at all) it’s easy to go back. At boot time, pick the entry in the GRUB menu for the version prior to Fedora Linux 45 and your system will start in that previous version rather than Fedora Linux 45. If you don’t see the GRUB menu, try to press ESC during boot. To make the change to the previous version permanent, use the following command:

$ rpm-ostree rollback

That’s it. Now you know how to rebase Fedora Silverblue to Fedora Linux 45 and roll back. So why not do it today?

FAQ

Because there are similar questions in comments for each blog about rebasing to newer version of Silverblue I will try to answer them in this section.

Question: Can I skip versions during a rebase of Fedora Linux? For example from Fedora Silverblue 42 to Fedora Silverblue 45?

Answer: Although it could sometimes be possible to skip versions during rebase, it is not recommended. You should always update to one version prior (42->43->44->45 for example) to avoid unnecessary errors.

Question: I have rpm-fusion layered and I get errors during rebase. How should I do the rebase?

Answer: If you have rpm-fusion layered on your Silverblue installation, you should do the following before rebase:

$ rpm-ostree update --uninstall rpmfusion-free-release --uninstall rpmfusion-nonfree-release --install rpmfusion-free-release --install rpmfusion-nonfree-release

After doing this you can follow the guide in this blog post.

Question: Could this guide be used for other ostree editions (Fedora Atomic Desktops) as well like Kinoite, Sericea (Sway Atomic), Onyx (Budgie Atomic),…?

Yes, you can follow the Rebasing using the terminal part of this guide for every Fedora Atomic Desktop. Just use the corresponding branch. For example, for Kinoite use fedora:fedora/45/x86_64/kinoite

What's New in Fedora Workstation 45

Posted by Fedora Magazine on 2026-11-03 14:00:00 UTC

Fedora Workstation features the latest six months of meticulous polish, under-the-hood responsiveness, and security hardening for F45, based on GNOME 51. Whether you are multitasking across monitors, managing daily appointments, or organizing large sets of files, GNOME 51 brings thoughtful refinements to your daily workflow on Fedora Workstation.

Silky-Smooth Responsiveness: Reworked Frame Scheduling

One standout improvement in GNOME 51 is a reworked frame scheduling and frame delivery system in Mutter. Animations, window snapping, and desktop transitions now hold a rock-steady frame rate even when the CPU and GPU are under heavy compile or gaming loads.

In tandem with this, GNOME streamlined its graphics pipeline by retiring legacy NVIDIA proprietary interfaces in favor of the standard GBM memory management path. This makes Wayland sessions cleaner, faster, and more uniform across all hardware.

Everyday App Polish

Files (Nautilus) Gets Quality-of-Life Upgrades

Files has picked up several subtle but indispensable touches:

  • Drag-and-Drop Counter Badge: When selecting and dragging multiple files, a small badge now shows the exact count of items you're moving.
  • Non-Blocking Operations: Large or slow directory reloads no longer freeze the interface, resulting in a snappier file management experience.
  • Notification Grouping: Grouping status and operation notifications together now keeps your notification tray tidy.

Calendar Rebuilt for Speed

Calendar feels faster than ever. The entire view-rendering engine was overhauled under the hood. This dramatically cut down the lag when scrolling through dense schedules in Month View. Reorganization within the event editor now presents a cleaner Notes section and native recognition of modern video conference links.

Revamped File Previewer

The quick-look File Previewer received a top-to-bottom redesign built on modern GTK 4 and libadwaita. It now seamlessly matches your desktop theme, respects Dark Style, handles fractional display scaling crisper than before, and properly previews high-resolution images at their actual native size.

Deeper Security: Next-Generation Secret Storage with oo7

Security underpins everything in Fedora Workstation. GNOME 51 introduces oo7, a modern Secret Service provider written from scratch to safely store application passwords, API tokens, and credentials.

Fedora Workstation is replacing legacy keyring daemons with a compartmentalized, sandboxed service. This provides even stronger defense against rogue applications attempting to peek at cached user credentials.

Accessibility and Navigation Upgrades

  • Keyboard-Driven Screenshots: You can now adjust screenshot selection boxes entirely with your arrow keys (
    Alt
    to move the selection,
    Shift
    /
    Ctrl
    for coarse/fine resizing, and
    R
    to reset).
  • Extended Reduced Motion: Toggling the Reduced Motion accessibility option now softens animations across more core widgets and Shell elements than ever before.
  • Reorganized Settings: The About (System Details) panel now includes a direct button to view the release notes for your running GNOME version, alongside a revamped fingerprint enrollment flow.

Upgrade or Try Fedora Workstation

If you’re already running Fedora, upgrading through GNOME Software or via the terminal with

dnf system-upgrade
will bring you right into GNOME 51. For clean installs, check out the Fedora Workstation live media at getfedora.org.

Share your favorite new feature or thoughts on the release over at the Fedora Discussion forum!

Disclaimer: Google Gemini, using the GNOME 51 release notes, assisted in the creation of this article. It was reviewed by humans before publishing. No apparent hallucinations were noted, however ,some content was not included.

Please read the GNOME 51 release notes for even more cool features that you can enjoy on Fedora Workstation as part of the F45 release.

What’s New in Fedora KDE Plasma Desktop 45

Posted by Fedora Magazine on 2026-11-03 14:00:00 UTC

KDE Plasma 6.8 was released on KDE's 30 year anniversary and we are proud to have it be the star of Fedora KDE Plasma Desktop Edition 45.

The Fedora KDE Plasma Desktop Edition is well suited for many needs. It combines the reliable and trusted Fedora Linux base with the KDE Plasma Desktop environment. It provides a selection of KDE applications that are simple by default, but powerful when needed.

KDE Plasma 6.8

KDE developers continue to release new features, fix bugs and fine-tune the desktop experience to improve on the now well-established foundation of Plasma 6. There have been two KDE Plasma releases since our last Fedora KDE Plasma Desktop Edition shipped. Some of the new features and updates include:

New Features

  • Per-screen virtual desktops: After 21 years per-screen virtual desktops have finally arrived!
  • Test your microphone volume: Stop wondering if it’s your microphone or an app that’s misbehaving.
  • Press-and-hold for special characters: With Plasma’s virtual keyboard enabled, press and hold a key to type special characters related to it.
  • Light/dark mode toggle: A quick toggle in the system tray to switch between light and dark Global Themes immediately.
  • “Background Apps” in the System Tray: The system tray now shows apps using the newer “Background Apps” system, which is more common for apps using the Flatpak package format.

Updated Features

  • Better Accessibility: a new “dwell clicker” feature can send a mouse click when the pointer stops moving. Designed especially for users with mobility issues.
  • Remote Desktop: Much better performance and quality, bi-directional clipboard synchronization, exclusive mode and overall polish to the experience.
  • Printing: Now the System Tray icon for printers shows the number of active jobs in a little badge.
  • Faster virtual desktop switching in the Overview: When you press "Meta + W" to open the Overview screen, Plasma now lets you switch virtual desktops simply by scrolling or pressing the "Page Up" or "Page Down" keys.
  • Easier to compare different time zones: The Digital Clock widget lets you add multiple time zones and quickly compare them.

Theming

  • Oxygen: For KDE’s 30th anniversary the Oxygen theme is back and brought up to par.
  • Breeze: The default Breeze theme also continues to evolve, now featuring rounded list and grid view highlights for many applications, and visible click effects for menu items.
  • Union: Plasma’s all-new Union theming system streamlines theming by making it possible to style Plasma, QtQuick apps, and QtWidgets apps all with a single set of easy-to-write CSS.

And More ...

There is so much new stuff since our last Fedora KDE Plasma Desktop Edition was released. Check out the full release announcements for Plasma 6.7 and Plasma 6.8.

Fedora Linux 45 general updates

Some broader changes in Fedora Linux also directly impact Fedora KDE Plasma Desktop Edition, notably:

  • Updated Podman: Podman 6 includes new features, but also significant API and CLI breaking changes. Depending on how you use Podman, this change may significantly affect you. The Podman 6 change proposal has information on what is affected.
  • NetworkManager VPN: NetworkManager-vpnc and NetworkManager-fortisslvpn are not in Fedora 45. If you already have them installed and are updating to Fedora 45, NetworkManager will obsolete and remove them. Users still using them should migrate their connection profiles to openconnect or libreswan.
  • Lazarus with multiple widget sets: The lazarus-ide now comes with a Qt6 option in lazarus-ide-qt6.
  • Updated IBus: IBus now supports the ISO latch and shift states of XKB key-maps in Wayland desktop environments like KDE, Sway, Hyprland, COSMIC.
  • DRM Panic Frontend: The DRM Panic Frontend provides users with a user-friendly interface for understanding kernel panic information and facilitates bug reports.

Wrap-up

The Fedora KDE SIG hopes that you’ll find Fedora KDE Plasma Desktop 45 to be a wonderful experience. When you’re ready to try it, click here for download links and verification instructions. If you would like to learn more, check out the Fedora KDE Plasma Desktop website.

Announcing Fedora Linux 45

Posted by Fedora Magazine on 2026-11-03 14:00:00 UTC

The Fedora Project is pleased to announce the release of Fedora Linux 45!

Whether you use Fedora on your desktop, server, edge device, or cloud instance, Fedora Linux 45 brings polished desktop upgrades, powerful new installer features, and updated toolchains.

Every Fedora release is a major community effort - thank you to everyone in our community who helped build, test, and package this release!

Upgrade

If you are already running Fedora Linux, upgrading to the new release is simple. Our user documentation shows you exactly how to start enjoying F45 easily.

Or, start fresh

Looking for a clean install or setting up a new device? Head over to getfedora.org to grab installation media for our flagship Editions:

  • Fedora Workstation
  • Fedora KDE Plasma Desktop
  • Fedora Server
  • Fedora Cloud
  • Fedora CoreOS & Fedora IoT

You can also explore our Atomic Desktops (including Silverblue, Kinoite, and Sericea) or choose from alternate desktop options via Fedora Spins (such as Cinnamon, Xfce, MATE, or COSMIC).

What’s new in Fedora Linux 45?

We have a lot of excellent content under the hood in this release. Below is only a snapshot of them. Take a spin through our release notes for individual changes, and details on each change. 

One of the biggest highlights in Fedora Linux 45 is integrated support for Stratis storage right inside the Anaconda installer.

Stratis brings modern enterprise storage features to local storage while wrapping device-mapper, XFS, and LUKS in an easy-to-use interface. These features include thin provisioning (over-provisioning), storage pooling, dynamic filesystem sizing, snapshots, and encryption.

  • GUI Installs (Web UI & Cockpit Storage): When performing custom partitioning during installation, you can launch the Cockpit storage module directly from Anaconda. From there, you can build Stratis pools across one or more physical drives and create dynamic / and /home filesystems on demand.
  • Automated Installs (Kickstart): For system administrators and automated deployments, Anaconda now supports --type=stratis with autopart, alongside dedicated stratispool and stratisfs kickstart commands.

Read more details about this really cool change in this article.

Desktop Highlights & Ecosystem Updates

  • Latest Desktop Environments: Updated desktop stacks across GNOME, KDE Plasma, and community spins bring improved performance, refined Wayland support, and better fractional scaling. 
  • Developer Toolchains: Updated development tools and runtime libraries ensure you have access to the latest language features, compiler optimizations, and core system utilities.
  • System & Kernel Enhancements: Powered by recent Linux kernel releases, Fedora 45 includes broad hardware support, improved power management for laptops, and enhanced container performance.

If you encounter any bugs or unexpected behavior after upgrading or installing, help is close at hand:

  • Visit the Ask Fedora discussion forum to ask questions and find answers.
  • Check the Common Issues section on Ask Fedora to see known issues and workarounds tracked during the release cycle.

Important: Two legacy NetworkManager VPN plugins—NetworkManager-vpnc and NetworkManager-fortisslvpn—are retiring and will be obsolete, starting in Fedora Linux 45. Please read this article for information on what you need to do to migrate your VPN connections to supported alternatives.

Let's keep the conversation going

We’d love to hear how Fedora Linux 45 works for you! Share your thoughts, post your desktop setups, or say hi to fellow community members over on Fedora Discussion.

Enjoy Fedora Linux 45!

Fedora Copr outage - updating servers

Posted by Fedora Infrastructure Status on 2026-11-03 09:00:00 UTC

There will be a Fedora Copr outage while we upgrade infrastructure machines to the latest Copr packages.

The build queue processing will be stopped during the outage, and the Frontend/Web-UI will be down most of the time (no new tasks accepted). The DNF packages and repositories (hosted on copr-backend …

Gestion d’eBooks : Komga et KOInsight remplacés par Tome !

Posted by Guillaume Kulakowski on 2026-11-02 19:29:00 UTC
Retour d'expérience après deux ans de lecture numérique : pourquoi j'ai décidé de remplacer Komga par Tome pour gérer mes ePubs, conserver mon arborescence de fichiers, profiter de stats poussées et m'intégrer proprement avec KOReader.