Home Fedora Fedora fixes: Overcoming 25 common issues with ease

Fedora fixes: Overcoming 25 common issues with ease

Fedora users, rejoice! We've compiled fixes for 25 common hiccups you might encounter, ensuring a smoother and more efficient Fedora journey.

by John Horan
fix fedora issues

Fedora stands out for its commitment to delivering the latest features and technologies to its users. However, this cutting-edge approach can occasionally lead to complex issues that require a technical mindset and a willingness to engage with the command line.

So, I’ve compiled a handy guide to squash those common bugs that might be bugging you too. Let’s dive in and iron out those issues, adding a dash of personal anecdotes and solutions that have saved my day more times than I can count.

Troubleshooting Fedora: 15 common errors and their solutions

1. Dependency Hell

Ever found yourself in the abyss of dependency issues? You’re not alone. It’s like trying to solve a puzzle where the pieces keep changing shapes. Here’s a lifeline: use the dnf command with the --best --allowerasing flags. It finds the best available versions of packages and resolves conflicts by removing conflicting packages (but be careful—it can remove essential ones too).


sudo dnf install --best --allowerasing <package-name>

Typical output:

Dependencies resolved

Explanation of command: This command attempts to install a package while resolving dependencies optimally, even if it means erasing conflicting packages.

2. RPM Database Lock

That moment when you’re ready to install something and Fedora says, “Nope, I’m busy.” This is the RPM database lock. If a previous dnf process was interrupted, the database might remain locked. My go-to solution: remove the lock file with:

 sudo rm -f /var/lib/rpm/.rpm.lock

Typical output: No output, but the lock file will be removed.

Explanation of command: This command forcefully removes the RPM database lock file.

3. Failed System Upgrade

Upgrading should be exciting, not a rollercoaster of dread. If your system upgrade fails, try using the dnf system-upgrade download --releasever=YOUR_VERSION command, and don’t forget to replace YOUR_VERSION with the Fedora version you’re upgrading to.

sudo dnf system-upgrade download --releasever=35
sudo dnf system-upgrade reboot

Typical output:


Explanation of command: This command downloads the necessary packages for the upgrade and then initiates a system reboot to start the upgrade process.

4. Bootloader Woes

Staring at a blinking cursor instead of the login screen is downright scary. Reinstalling the GRUB2 bootloader often works wonders. You can do this by booting from a live media, chrooting into your system, and running grub2-install.

sudo grub2-install /dev/sda
sudo grub2-mkconfig -o /boot/grub2/grub.cfg

Typical output:

Installation finished. No error reported.

Explanation of command: This reinstalls GRUB2 on the specified device and generates a new configuration file.

5. Network Manager Not Running

A world without the internet is a lonely one, indeed. If the Network Manager plays hide and seek, bring it back with a simple systemctl start NetworkManager.

sudo systemctl start NetworkManager

Typical output: No output, but Network Manager will start.

6. SELinux Bringing You Down

SELinux is like that overprotective friend. Sometimes, it’s a bit too much. If it’s causing issues, check the audit logs with ausearch -m avc -ts recent. And remember, tweaking SELinux settings should be done cautiously.

ausearch -m avc -ts recent

Typical output:


Explanation of command: Lists recent SELinux access control messages from the audit log.

7. DNF Dragging Its Feet

A slow DNF can test your patience. Optimize it by setting fastestmirror=true and max_parallel_downloads=10 in the /etc/dnf/dnf.conf file. Trust me, it’s a game-changer.


Typical output: No immediate output, but DNF operations will use the fastest mirrors and allow up to ten parallel downloads, speeding up the process.

8. Software Repositories Conflicts

Multiple repositories can sometimes conflict, leading to package mayhem. The dnf repoquery --duplicates command is your detective, helping you find and eliminate the troublemakers.

sudo dnf repoquery --duplicates

Typical output:

package-name.x86_64 1:1.0-1 @repository-name

Explanation of command: Lists duplicate packages from repositories that can cause conflicts.

9. Orphaned Packages Lurking Around

Orphaned packages are like leftovers in your fridge—they just sit there. Clean them up with dnf remove $(dnf repoquery --extras --exclude=kernel*).

sudo dnf remove $(dnf repoquery --extras --exclude=kernel*)

Typical output:

 Dependencies resolved.

Explanation of command: This removes packages that were installed as dependencies but are no longer required by any installed packages.

10. GNOME Extensions Not Working

GNOME extensions can sometimes break after an update. I’ve found that reinstalling them from the GNOME Extensions website usually does the trick.

To reinstall GNOME extensions, you would typically use a web browser to visit the GNOME Extensions website, find the extension, and click the switch to reinstall.

11. Display Server Crashes

When the display server crashes, it feels like your screen has thrown a tantrum. Switch to a virtual terminal using Ctrl+Alt+F3 and restart the display manager with systemctl restart gdm.

sudo systemctl restart gdm

Typical output: No output, but the GDM (GNOME Display Manager) will restart.

12. DNF Transaction Check Error

This error is the equivalent of being cut in line. Solve it by removing the offending package with dnf remove and then proceed with your transaction.

sudo dnf remove <problematic-package>
sudo dnf install <desired-package>

Typical output:


Explanation of command: Removes the package causing the transaction check error, then proceeds with the intended installation.

13. File System Errors

File system errors can make your heart skip a beat. Running fsck on an unmounted file system can help you breathe easy again.

sudo umount /dev/sda1
sudo fsck /dev/sda1

Typical output:

Filesystem checked and all is well.

Explanation of command: Unmounts a filesystem and then runs a check on it to fix any errors.

14. Missing Firmware Warnings

These warnings pop up like uninvited guests. You can often ignore them, but if they cause issues, find and install the missing firmware packages.

sudo dnf install <firmware-package>

Typical output:


Explanation of command: Installs the missing firmware package needed by your system.

15. Flatpak Flakiness

Flatpak is fantastic until it’s not. If you encounter issues, try updating with flatpak update or reinstall the problematic application.

flatpak update

Typical output:

Updating: org.freedesktop.Platform/x86_64/19.08

Explanation of command: Updates all installed Flatpak applications to their latest versions.

16. Conflicts with Python Versions

Fedora loves Python, but sometimes version conflicts arise. My tip: use virtual environments with python -m venv to isolate your projects and avoid clashes.

python3 -m venv myprojectenv
source myprojectenv/bin/activate

Typical output:

 (myprojectenv) user@hostname:~/myproject$

Explanation of command: Creates a virtual environment for Python projects and activates it.

17. Package Installation Woes

Sometimes, a package just won’t install. If dnf install isn’t playing nice, try clearing the cache with dnf clean all and then dnf makecache.

sudo dnf clean all
sudo dnf makecache

Typical output:

Metadata cache created.

Explanation of command: Clears the DNF cache and recreates it to solve package installation issues.

18. The Case of the Missing Libraries

You run a program, and it complains about missing libraries. The fix? Search with dnf provides to find which package offers the needed library and install it.

sudo dnf provides *libmissing.so*
sudo dnf install <package-containing-library>

Typical output:

package-name.x86_64 : Package that contains libmissing.so

Explanation of command: Searches for the package that provides the missing library and installs it.

19. Default Applications Playing Hard to Get

Fedora might decide to open your files with bizarre default applications. Set them straight with the right-click “Open With” option and make your choice a default.

Use the file manager GUI to right-click a file, choose “Open With,” and set the default application.

20. Unresponsive System

If your Fedora becomes unresponsive, don’t panic. Try the REISUB keys sequence – it’s a safer way to reboot than hitting the reset button.

Use the REISUB key sequence (holding down Alt + SysRq and typing REISUB one key at a time) to safely reboot a frozen system.

21. Firewall Frustrations

Firewalls are crucial, but when they block your applications, it’s a headache. Learn to use firewall-cmd to manage your rules and open or close ports as needed.

sudo firewall-cmd --add-port=8080/tcp --permanent
sudo firewall-cmd --reload

Typical output:


Explanation of command: Opens TCP port 8080 and reloads the firewall to apply the changes.

22. Audio Issues

Silence isn’t always golden, especially when you want sound. Check alsamixer to ensure nothing is muted and use pulseaudio -k to reset the audio system.

pulseaudio -k

Typical output:

PulseAudio restarted.

Explanation of command: Checks the mixer settings and restarts the PulseAudio server.

23. Dual Boot Time Confusion

Dual-booting with Windows can lead to time confusion. Solve this by synchronizing the time with timedatectl set-local-rtc 1.

timedatectl set-local-rtc 1

Typical output:

RTC in local TZ: yes

Explanation of command: Sets the Real Time Clock to use the local timezone, which helps synchronize time between Fedora and Windows in a dual-boot setup.

24. Fedora Feeling Slow

Performance issues can creep up. Consider using the Stacer tool to monitor and optimize your system’s performance.

Stacer is not a command-line tool; it’s a GUI application. Download and install it from its website or repository, then use it to monitor and optimize your system.

25. Login Loop

Stuck in a login loop? It’s likely a permissions issue in your home directory. Chown your way out by ensuring your .Xauthority file is owned by your user.

sudo chown username:username .Xauthority

Typical output: No output, but this will fix ownership of the .Xauthority file.


In this guide, we have covered a range of obstacles that Fedora users may come across, such as dependency conflicts, bootloader issues, system performance problems, and network management. For each issue, we have provided precise command-line instructions to help users diagnose and fix these common snags. By following this technical walkthrough, users can improve their system administration skills, gain a deeper understanding of Fedora’s internal workings, and ensure their environment remains reliable and robust. This guide is not only a practical troubleshooting manual but also emphasizes the significance of being fluent in the command-line for effective management of a Fedora system.

You may also like

Leave a Comment



FOSS Linux is a leading resource for Linux enthusiasts and professionals alike. With a focus on providing the best Linux tutorials, open-source apps, news, and reviews written by team of expert authors. FOSS Linux is the go-to source for all things Linux.

Whether you’re a beginner or an experienced user, FOSS Linux has something for everyone.

Follow Us


©2016-2023 FOSS LINUX



“Linux” is the registered trademark by Linus Torvalds in the U.S. and other countries.