glib2 2.65.2 has a bug which can cause a "Numerical result out of range" error when accessing certain filesystems. This affects a wide range of apps - e.g. just about any GNOME or GTK+ app - as they use glib2 for filesystem access. The bug is known to affect read-only filesystems and CIFS shares, but may well affect other filesystems too.
There is already a fix for this upstream and I've backported it in glib2-2.65.2-3 , but as Fedora 33 is now frozen, we need a freeze exception to get this into Beta. So, filing this bug and proposing as a freeze exception. I will create an update and mark it as fixing this bug next. Obviously, this is a very visible bug if you have affected filesystems and will be present on lives so cannot be fully fixed with a post-release update.
FEDORA-2020-fc47702b29 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-fc47702b29
FEDORA-2020-fc47702b29 has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-fc47702b29`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-fc47702b29
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Accepted as a Beta freeze exception:
FEDORA-2020-fc47702b29 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.