On Thu, 2021-07-08 at 15:12 -0500, Rex Dieter wrote:
That's just how PackageKit offline updates are implemented (not specific to discover).
It is required, for example, to allow one to use newly installed kernels.
When Discover reports an upgrade with system implications (say a new kernel) and the user allows the upgrade (by clicking the appropriate button):
- Discover downloads the files for the upgrade
- Discover requests a reboot. After the user allows the reboot
- Discover reboots the system
- Discover installs the new kernel (or whatever)
- Discover reboots the system (again)
What is the reason for the additional reboot before installing the new kernel (step 3)?
--
Sincerely Jonathan Ryshpan <jonrysh@pacbell.net>
We are sorry, but the number you have dialed is
imaginary. Please rotate your phone 90 degrees
and try again.
_______________________________________________kde mailing list -- kde@lists.fedoraproject.orgTo unsubscribe send an email to kde-leave@lists.fedoraproject.orgFedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelinesList Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.orgDo not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure