https://bugs.kde.org/show_bug.cgi?id=498002
--- Comment #2 from b...@mogwai.be --- The cause seems to be a race condition: for each action that requires network access, Kasts checks whether there is a fuctional network connection, whether it's a metered connection and whether it's allowed to download over a metered connection. Apparently, due to some internal change, Kasts gets told that there is no available network connection immediately after startup. This is the moment that it tries to do the automatic feed update, so it does not try to update the feeds. However, just a few seconds later (or even a fraction of a second), the network connection switches to "available". I have no clue why this is happening in the flatpak, but not in e.g. distro packages. Maybe it's due to the sandboxing? As a workaround, you can deselect "enable network connection checks" from Settings > Network. That should have it trigger the feed updates on startup. -- You are receiving this mail because: You are watching all bug changes.
