On 8 Jul 2021, at 22:32, Jonathan Ryshpan <jonrysh(a)pacbell.net>
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
> 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(a)pacbell.net>
>> 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
Sincerely Jonathan Ryshpan <jonrysh(a)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(a)lists.fedoraproject.org
To unsubscribe send an email to kde-leave(a)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://firstname.lastname@example.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure