Last update broke Nvidia drivers, unable to reinstall them

This topic is not entirely solved, but it’s not the same problem as the original one, so I don’t know if this conversation should stay here or have it’s own place…
In a nutshell, my bash command doesn’t update everything in my system, like Discover does.

dnf update && flatpak update returns

Last metadata expiration check: 2:37:31 ago on lun. 03 avril 2023 06:33:42.
Dependencies resolved.
Nothing to do.
Complete!

Looking for updates…
Nothing to do.

But Discover has some updates to do:

image

And here are the updated packages with the details (gathered clicking on “More Information”):

fakeroot-libs

Upgrade to new version 1.31-1.fc37
Release notes:

Update fakeroot to 1.31 (#2167522)

fakeroot

Upgrade to new version 1.31-1.fc37
Release notes:

Update fakeroot to 1.31 (#2167522)

libsemanage

Upgrade to new version 3.5-2.fc37
Release notes:

libsemanage: include more parameters in the module checksum

The check_ext_changes option currently assumes that as long as the module content is unchanged, it is safe to assume that the policy.linked file doesn’t need to be rebuilt. However, there are some additional parameters that can affect the content of this policy file, namely: * the disable_dontaudit and preserve_tunables flags * the target_platform and policyvers configuration values

Include these in the checksum so that the option works correctly when only some of these input values are changed versus the current state.

Fixes: 286a679fadc4 (“libsemanage: optionally rebuild policy when modules are changed externally”)

See also bug 2173959

openexr-libs

Upgrade to new version 3.1.6-1.fc37
Release notes:

See https://github.com/AcademySoftwareFoundation/openexr/blob/v3.1.6-rc/CHANGES.md#version-316-march-9-2023 for details.

publicsuffix-list-dafsa

Upgrade to new version 20230318-1.fc37
Release notes:

Update list to 20230318

python3-libsemanage

Upgrade to new version 3.5-2.fc37
Release notes:

libsemanage: include more parameters in the module checksum

The check_ext_changes option currently assumes that as long as the module content is unchanged, it is safe to assume that the policy.linked file doesn’t need to be rebuilt. However, there are some additional parameters that can affect the content of this policy file, namely: * the disable_dontaudit and preserve_tunables flags * the target_platform and policyvers configuration values

Include these in the checksum so that the option works correctly when only some of these input values are changed versus the current state.

Fixes: 286a679fadc4 (“libsemanage: optionally rebuild policy when modules are changed externally”)

See also bug 2173959

qpdf-libs

Upgrade to new version 10.6.3-5.fc37
Release notes:

Add bash and zsh completions files

tigervnc-license

Upgrade to new version 1.13.1-3.fc37
Release notes:

Fixes CVE-2023-1393: X.Org Server Overlay Window Use-After-Free Local Privilege Escalation Vulnerability

tigervnc-server-minimal

Upgrade to new version 1.13.1-3.fc37
Release notes:

Fixes CVE-2023-1393: X.Org Server Overlay Window Use-After-Free Local Privilege Escalation Vulnerability

So it seems "Fedora Linux 37 (KDE Plasma) is not updated by dnf nor by flatpak.
Can I complet my initial command so it would?

Instead of using dnf upgrade try dnf upgrade --refresh so it completely rebuilds the cache data before trying the update. That probably would pull in those updates from the repos.

There seems to be a similar command for the flatpak but I am unfamiliar with what it is.