I update my desktop machine every few days, normally using the Gnome
software tool from the updates tab. This is a fast i7 with a good SSD
and 32GB of memory, and it normally boots to login in about 5 seconds.
As an aside, for some weird reason way beyond what makes sense on a
machine with an inode-based filesystem, the Gnome software tool has a
problem where it almost always wants to reboot to apply the changes.
That's an inconvenience that I assume that the Gnome people are fixing
some day. I don;t know if there is a bug tracking that more minor issue.
However, there is a more serious issue. Starting with Fedora 31, there
are really good odds that the reboot does a grub hard stop with a
message about a corrupt compressed file. I have to reboot manually
several times, and eventually it comes up just as if nothing was wrong.
This says to me that there is something either incorrectly async in the
updater, or there is a missing state check in the update reboot
sequence. Is anyone else having this issue?
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
