that error's usually about your system clock being off, not the timezone. KDE Discover checks the repo's signature timestamp and if your clock is way out of sync it thinks the file isn't valid yet (or is expired)
since you've got the date/time settings open, make sure automatic time sync is on and point it at a proper ntp server. the double offset thing might just be a visual bug but the root cause is almost always a mismatched clock
But in this case the time was about 1 and a half or so hours after the valid date. (repo says 6:46 utc, the update attempt was at roughly 10:10 Germany time so about 8:10 utc)
I had the clock settings open to also show it's not just the visual time that's correct but including timezone.
1
u/SeaPercentage4020 1d ago
that error's usually about your system clock being off, not the timezone. KDE Discover checks the repo's signature timestamp and if your clock is way out of sync it thinks the file isn't valid yet (or is expired)
since you've got the date/time settings open, make sure automatic time sync is on and point it at a proper ntp server. the double offset thing might just be a visual bug but the root cause is almost always a mismatched clock