Re: update not working correctly
On 12/7/19 9:09 PM, Tim via users wrote: The notion of only rebooting when you really need it has gone right out the window, to be replaced by the Windows-centric thinking that it's easier just to reboot rather than assess whether it's really necessary. Non-technical users don't need to run into weird issues when they do an update and they don't have the understanding to know what caused them or whether rebooting is necessary. For those that do have the technical understanding, there are easy ways to update without rebooting. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: update not working correctly
On Sat, 2019-12-07 at 09:14 -0500, John Mellor wrote: > 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 wouldn't believe that. There's been a hell of a lot of advocacy (that I don't agree with) that you should always reboot after updates. The notion of only rebooting when you really need it has gone right out the window, to be replaced by the Windows-centric thinking that it's easier just to reboot rather than assess whether it's really necessary. -- uname -rsvp Linux 3.10.0-1062.9.1.el7.x86_64 #1 SMP Fri Dec 6 15:49:49 UTC 2019 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: update not working correctly
On Sat, 2019-12-07 at 09:14 -0500, John Mellor wrote: > 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. Last I heard that was a design choice so I wouldn't expect it to be "fixed". I use KDE and it doesn't affect me, but you can always update from the command line using dnf and avoid this. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
update not working correctly
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@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
