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.

-- Rex

On Thu, Jul 8, 2021 at 2:36 PM Jonathan Ryshpan <> 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 <>

	Dance, as if nobody's watching,
	Love, as if you've never been hurt,
	Sing, as if no one can hear you,
	Work, as if you don't need the money,
	Live, as if heaven is on earth.
	-- Rumi
kde mailing list --
To unsubscribe send an email to
Fedora Code of Conduct:
List Guidelines:
List Archives:
Do not reply to spam on the list, report it: