https://bugs.kde.org/show_bug.cgi?id=475400
--- Comment #6 from b...@mogwai.be --- I've thoroughly reviewed the code, and the only possible explanation that would explain the symptoms would be that either networkmanager or the connectivity dbus service is saying that you're not connected to the network or on a portaled or very limited network connection. The code of Kasts did indeed change to also include an additional connectivity check for downloads (because of refactoring for the upcoming qt6 version). Only if your system responds by saying that you are not connected (or limited), then it is indeed impossible to actually get into the download routine no matter what the state of the metered settings. This is because the problem is actually not the connection being metered, but because Kasts thinks it's offline. So, that means: - The error reporting needs to be updated to actually report that the problem is connectivity instead of the metered status. - The code should probably take into account the fact that it can receive a completely wrong status of the connectivity. One possible solution is to remove the connectivity checks altogether, but that will lead to downloads and refreshes hanging until timeout. One additional thing that would really help: if you know how to do it, could you check what NetworkManager or dbus "org.freedesktop.portal.NetworkMonitor" is reporting as value for the "connectivity" property? (And while you're at it, you might as well doublecheck the "metered" property as well, but that shouldn't be the problem.) -- You are receiving this mail because: You are watching all bug changes.
