This is my one main complaint about Fedora Linux.

  • Voytrekk@lemmy.world
    77·
    11 months ago

    Those updates in Discover are for flatpak, not dnf. You can verify that with flatpak update.

    As for discover wanting to restart to do their update, that’s a fedora thing for an extra level of safety while updating. You can read about it here.

    • Sentau@discuss.tchncs.de
      331·
      11 months ago

      As for discover wanting to restart to do their update, that’s a fedora thing for an extra level of safety while updating

      That shouldn’t trigger for flatpaks though. No risk of breaking the system while updating flatpaks

  • therealjcdenton@lemmy.zipEnglish
    61·
    11 months ago

    Discover checks knewstuff (global themes, plasmoids, etc.), Flatpaks, firmware and snaps, (which all have a relevant backend package something like (discover-backend-packagekit). Discover, well more like PackageKit, will let you know if a reboot is necessary if there’s something like a kernel update.

  • rtxn@lemmy.worldEnglish
    62·
    11 months ago

    If the kernel, initramfs, or a driver is updated, you have to reboot the computer to apply them (you can’t reload the kernel while it’s running). A user might not know or notice this, so GUI installers (and some CLI tools like pacman on Endeavour) often warn the user or sometimes force a reboot.

      • 520@kbin.social
        12·
        11 months ago

        I’ve never seen a distro force a reboot, Windows style. Only ever advise people to reboot.

        • lemmy_user_838586@lemmy.ml
          1·
          11 months ago

          Well, then I don’t understand the downvotes, lol. The person i replied to said sometimes a distro will force a reboot, I said that’s bad, and a bunch of people apparently disagree with that.

          • 520@kbin.social
            3·
            11 months ago

            So when people say ‘force a reboot’ there are two things it can mean:

            1. a reboot is required for updates to actually take effect. Linux sometimes does this for things like the kernel.

            2. the OS forces you to stop everything you are doing and reboots the machine. I have only ever seen Windows do this. Not Linux, not even MacOS.

            This might be where the confusion is coming in. @rtxn is referring to number 1 but the rest of us are referring to number 2

          • Markaos@lemmy.one
            1·
            11 months ago

            Those distros “force” you to reboot when you want to update (as opposed to allowing you to do the update on the running system). Think Windows 7 and earlier, that kind of forced reboots, back when people were fine with the way Windows did updates.

  • bruhduh@lemmy.world
    4·
    11 months ago

    I had reverse situation, discover said there’s none of apps i need or/and updates, while dnf was working flawlessly

    • Petar Kulić@mstdn.plus
      61·
      11 months ago

      @heartsofwar @UntouchedWagons
      I use Discover on Debian testing and Arch, never once did it force me to restart on Arch, but on Debian it would say it is recommended.
      I don’t think that’s forcing me to restart, so I guess Fedora does that differently. 🤔

      • drndramrndra@lemmygrad.ml
        3·
        11 months ago

        AFAIK no distro forces you to reboot, but they all require it for some updates to take effect. You can’t reload the kernel while the system is running.

        Fedora just makes that clearer to the user by only installing those updates when they’re going to be active - after a reboot. I think it also blocks new system updates until the current set is completely finished.

        You can disable offline updates in the system settings, but I think they’re a good idea, especially for the average user.

    • Pantherina@feddit.de
      1·
      11 months ago

      I agree that packagekit is annoying and I just have automatic updates in the background using flatpak update -y and rpm-ostree update.