Problems with Fedora 32 and 33


I am new to fedora but not to Linux. I have been using ubuntu for a while then decided to try fedora 32.
I have faced some problems that I did not face when using ubuntu

  1. It takes more time to boot or to shut down may be more than 2 minutes.
  2. The fan sound is always high.
    3)Fedora 32 was working fine then I upgraded to 33 by downloading it, some problems started to arise like, it hangs or the wifi or hotspot does not work or even I can not open the terminal. So how would I remove fedora 33 from Fedora 32. knowing that in the grub menu it showed me 2 version of Fedora 33 and one version of Fedora 32.
    My laptop is HP Pavillion notebook and it is dual boot.
    Thanks in advance.

If you are referring to the grub menu at boot that display is not 2 versions of F33 and one version of F32. You only have one OS installed and grub allows you to select the kernel version to use at boot time.

You did not say if you have done a “dnf upgrade” since the system was upgraded from 32 to 33 nor have you told us which kernel versions are available and giving the problems. If you have not done a new upgrade then please do so now and let us know if the situation changes.
No, you cannot downgrade the OS back to 32 without doing a new install.

1 Like

PackageKit is so buggy that it’s maintainer is giving -EWONTFIX: 1354074 – Possible big memory leak in packagekit
Even its original author leave it in “hard maintenance mode”: PackageKit is dead, long live, well, something else – Technical Blog of Richard Hughes
You should automatically shut this down after 60 seconds by editing its configuration file

#In /etc/PackageKit/PackageKit.conf
# Shut down the daemon after this many seconds idle. 0 means don't shutdown.

Usually packagekit will not be working when I shutdown my machine, but I occasionally found it working, so I have to wait 60 seconds of inactivity (observed by pressing Esc (or anything like F2) when I shutdown and see a bunch of systemd service status [OK]).

As for the fan sound is always high, you may want to check out which program is using so much cpu. If you found it’s a setroubleshootd daemon, you may be affected by You want to downgrade flatpak (dnf downgrade flatpak (flatpak should have hard version dependency on flatpak-selinux) or remove it and install a lower version one), or send -SIGSTOP to stop setroubleshootd using too much cpu (sudo pkill -SIGSTOP setroubleshootd)

I don’t know how to downgrade to fedora 32. This is surely not supported by fedora, and I guess dnf commands can do it, but is pretty tricky.

I only encountered slow shutdown by packgekit. Boot is pretty quick on my machine.
When you boot or shutdown, you can press any key like Esc or F2 to find what is slowing down to show systemd boot/shutdown logs.
Alternatively, you can use journalctl. It logs everything, including boot/shutdown logs, so you can use something like journalctl --since 2021-01-10 or journalctl --boot=-1 to logs since 2021-01-10 or logs during the last entire boot-shutdown cycle.
As for boot (but not shutdown) you can use the command systemd-analyze blame or systemd-analyze critical-chain gdm.service later to find out daemons that slowed booting process.