Fedora Linux Triage

Fedora Linux Triage is an AI skill that assists system administrators and developers in diagnosing and resolving issues on Fedora Linux systems. It provides structured troubleshooting workflows for DNF package management problems, SELinux policy conflicts, firewalld configuration, service failures, and Flatpak application issues specific to the Fedora ecosystem and its rapid release cycle.

What Is This?

Overview

Fedora Linux Triage delivers systematic diagnostic procedures tailored to Fedora conventions and tooling. It understands DNF package management including modularity streams, SELinux enforcement and policy troubleshooting, firewalld zone management, systemd service administration, and Flatpak sandboxed application management. When presented with error messages or symptoms, the skill identifies root causes and provides resolution steps aligned with Fedora project guidelines and the upstream-first philosophy. This approach ensures that fixes remain compatible with future Fedora releases rather than introducing local workarounds that break during upgrades.

Who Should Use This

This skill serves developers using Fedora as their primary workstation, system administrators evaluating Fedora for server deployments, QA engineers testing software against the latest Fedora release, DevOps engineers maintaining Fedora-based container images, and users transitioning from other distributions to Fedora who encounter unfamiliar tooling or default security configurations.

Why Use It?

Problems It Solves

Fedora's frequent release cycle means system upgrades happen roughly every six months, each potentially introducing new package versions, configuration changes, and deprecated features. DNF module stream conflicts can block package installations, SELinux policy updates may deny previously allowed operations, and Flatpak permission changes can break application functionality after system updates. Without structured guidance, administrators often resort to disabling security features rather than addressing the underlying cause.

Core Highlights

The skill provides DNF-specific diagnostic commands for resolving dependency and module stream conflicts. It includes SELinux audit interpretation with targeted policy module generation, firewalld troubleshooting for zone and service configuration, and Flatpak permission analysis for sandboxed applications. Each workflow prioritizes investigation over immediate modification to prevent cascading issues.

How to Use It?

Basic Usage

dnf module list --installed
dnf module list package-name

sudo dnf module reset module-name

sudo dnf clean all
sudo dnf makecache
sudo dnf install package-name

sudo dnf repoquery --duplicates
sudo dnf remove --duplicates

Real-World Examples

sudo ausearch -m avc -ts recent

sudo ausearch -m avc -ts recent | audit2why

sudo setsebool -P httpd_can_network_connect on

sudo ausearch -m avc -ts recent | audit2allow -M myapp
sudo semodule -i myapp.pp

sudo restorecon -Rv /var/www/myapp/
sudo systemctl restart httpd

Advanced Tips

Use dnf history to identify which transaction introduced a problem and selectively undo specific transactions rather than rolling back the entire system. For example, running dnf history undo followed by the transaction ID reverses only the problematic change while preserving subsequent updates. Before major version upgrades, run dnf system-upgrade with the allow-erasing flag only after reviewing which packages will be removed. Monitor the Fedora Magazine and release notes for known issues before upgrading.

When to Use It?

Use Cases

Use Fedora Linux Triage when DNF reports unresolvable dependency conflicts during package installation, when SELinux blocks application behavior after a system update, when Flatpak applications lose permissions or fail to access required resources, or when system services fail to start after a Fedora version upgrade.

Related Topics

DNF package management, RPM package internals, SELinux policy administration, firewalld zone configuration, Flatpak and Flathub management, systemd service debugging, and Fedora system upgrade procedures all complement the troubleshooting workflows provided by this skill.

Important Notes

Requirements

Root or sudo access is required for most diagnostic and repair operations. The audit service must be running for SELinux denial analysis. Network access to Fedora repositories is needed for package operations. Familiarity with the command line and basic Linux concepts is expected. Users working in restricted environments should verify that outbound repository access is permitted before beginning package-related triage.

Usage Recommendations

Do: check Fedora release notes before performing system upgrades to prepare for known breaking changes. Use dnf history and transaction IDs to trace issues back to specific package operations. Test SELinux policy changes in permissive mode before enforcing them in production.

Don't: disable SELinux globally as a troubleshooting shortcut when a targeted boolean or policy module would resolve the issue. Mix packages from different Fedora releases without understanding the compatibility implications. Remove packages with the force flag without reviewing dependency chains.

Limitations

The skill covers current and recent Fedora releases. Third-party repository conflicts depend on the specific repository maintainer. Proprietary driver issues, particularly for NVIDIA GPUs, may require vendor-specific troubleshooting beyond standard Fedora triage. Hardware compatibility issues with very new hardware may need kernel parameter adjustments not covered in general triage workflows.