On 8 Jul 2021, at 22:32, Jonathan Ryshpan <jonrysh@pacbell.net> wrote:

I'm still don't understand.  It's easy to see why one reboot is necessary, but why two?

I found that if I update from a logged in KDE session there was a good
chance that after dnf competed the update the desk top would stop working.
I could not log out or request a reboot.

This is why the first reboot is needed.

The 2nd reboot is needed after the kernel is installed.


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.

On Thu, Jul 8, 2021 at 2:36 PM Jonathan Ryshpan <jonrysh@pacbell.net> wrote:
When Discover reports an upgrade with system implications (say a new kernel) and the user allows the upgrade (by clicking the appropriate button):
  1. Discover downloads the files for the upgrade
  2. Discover requests a reboot.  After the user allows the reboot
  3. Discover reboots the system
  4. Discover installs the new kernel (or whatever)
  5. 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.org
To unsubscribe send an email to kde-leave@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/kde@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure