I'm a very new Linux user running Fedora with KDE, as of a few weeks ago.
I have some super basic questions about updates through Discover.
Background: There are new updates available nearly every day. The list of updates can get very long and is a text-based list, including many undecipherable things. Unless I were to search for each and every one.
For example, today's update list includes the following entries:
cups
Upgrade to new version 1:2.4.16-7.fc43
Release notes:
fix cupsd endless loop on busy servers (fedora#2446938)
cups-client
Upgrade to new version 1:2.4.16-7.fc43
Release notes:
fix cupsd endless loop on busy servers (fedora#2446938)
cups-filesystem
Upgrade to new version 1:2.4.16-7.fc43
Release notes:
fix cupsd endless loop on busy servers (fedora#2446938)
libtasn1
Upgrade to new version 4.21.0-1.fc43
Release notes:
Update to 4.21.0; fixes CVE-2025-13151
vim-minimal
Upgrade to new version 2:9.2.148-1.fc43
Release notes:
patchlevel 148
Security fix for CVE-2026-32249
zlib-ng-compat
Upgrade to new version 2.3.3-2.fc43
Release notes:
Fix RISC-V build
Yes, I could look up what these are, but that seems impractical given that each day there are dozens of updates and I really don't want to spend the time on this.
So onto my questions:
-
Should I just run all these updates as they come up? Do you all run these updates as they pop up?
-
Are you all getting this many updates on Fedora or is it something specific to me and the apps I'm running? I installed Fedora as-is and installed maybe 10 additional applications. So I shouldn't have anything super custom. Computer is a 5 year old ASUS laptop with AMD.
-
Is there a way to de-select some updates if I don't want to run all of them?
-
Should I ignore daily updates and install them less frequently, say monthly? Meaning, I'm not super interested in being the glitch finder. If there's a bug in an update, I'd rather have somebody else find it first and have the update patched.
General Fedora feedback: the discover update app feels lacking here. As a new user, I expect more of a description about what each application/service is as well as a clickable link to read more about the app and the update.
I second this.
Since about 2002, I've had a growing number of machines (ent Linux, similar to fedora) who simply patch nightly via cron. I get mail on the changes. In 24 years of
yum-cronI've seen one error (busted deps on cobbler) and caused one error (too-old smb.conf during an update) and that's it.So, my fuck-up aside, the only issue I've seen with a yum-cron patching setup (in dev/test and homeland) in ~25 years is exactly one issue on boxes running a mainstream but not prevalent piece of software due to a packaging glitch. That's it.