Really? Discover seems to insist on reboot for *every* update. Apper,
on the other hand certainly doesn't, even for system updates. I
understand they don't get applied until rebooting.
However, Discover seems to list lots of things as "system" which really
aren't. I've just got notification of a SkypeForLinux update and sure
enough, after I install it, Discover says a reboot is required. I
understand I don't have to do it, but surely better to exclude poor
information than simply to know, which not veryone will, that it can be
ignored.
Slightly annoyed of the UK
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.
-- Rex
On Thu, Jul 8, 2021 at 2:36 PM Jonathan Ryshpan <jonrysh(a)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)?
>
> _______________________________________________
> 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://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
>
https://pagure.io/fedora-infrastructure