/usr/share/zoneinfo/Europe/Warsaw exists and is valid
There is no /etc/timezone file (which is normal on many minimal systems).
Therefore, tzdata and localtime symlinks appear properly configured.
The result is that script.tv.show.next.aired addon provide wrong time for episodes and also spam in kodi.log with repeating entries:
2026-02-21 11:02:25.069 T:2678 error <general>: Unable to obtain time zone bias!
2026-02-21 11:02:27.809 T:2678 error <general>: Unable to obtain time zone bias!
I’m just trying to help to fix this issue.
I don’t know where it is originating from but as I reported: comparing behavior how it is in Kodi 22 on Windows OS and how it is on CoreELEC 21 to me it looks like this issue with:
Why I’m asking for that?
Because I suspect it cause issue in Kodi add-on.
Why I suspect it cause issue in Kodi add-on?
Because in CoreELEC 21 with the same Kodi add-on there are no errors: error <general>: Unable to obtain time zone bias!
I would like to confirm that this issue is now fully understood and resolved.
When a TV show in the video database has: tvshow.c05 = ‘1969-12-31’
Kodi 22 logs the following message in kodi.log: error <general>: Unable to obtain time zone bias!
Important observations:
Kodi 21 → no error
Kodi 22 → logs timezone bias error
Same database (MyVideos131 for Kodi 21, MyVideos141 for Kodi 22)
Same hardware
Same timezone
This clearly indicates a regression in date/time or timezone bias handling introduced in Kodi 22.
The value 1969-12-31 was already present in the older MyVideos131 database (Kodi 21) and likely originated years ago during scraping when no premiere date was available.
Kodi 21 handled this value silently, while Kodi 22 does not.
After setting:
UPDATE tvshow
SET c05 = NULL
WHERE c05 = '1969-12-31';
the error no longer appears.
At the beginning of the investigation, I suspected the issue might be related to CoreELEC because of these log entries:
However, this turned out to be unrelated.
I apologize for the earlier false alarm and for any confusion it may have caused.
It took me around 10 hours of debugging to identify the real root cause.