Opened 16 years ago
Closed 16 years ago
Last modified 13 years ago
#8286 closed Bug Report - General (duplicate)
Program Guide DST offset is using GMT and not Local timezone on day of change
| Reported by: | Owned by: | Isaac Richards | |
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | MythTV - Mythfilldatabase | Version: | 0.23rc1 |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
It appears that the MythTV Program Guide is using some additional logic to align the EPG data around DST changes but is using GMT rather than local time as the base.
This is particularly noticeable in NZ where the schedule was off by an hour until 3pm NZST or 3am GMT today.
I have been able to reproduce this problem under MythBuntu 9.10 with MythTV 0.22.0+fixes22594, and MythBuntu 10.04 Beta and their MythTV 0.23 build.
To reproduce from a clean install, install Mythbuntu selecting NZ as your region and then set the local clock back to 9am on Sunday 4th April 2010.
Create a dummy Video Source with no grabber, and set the XMLTV offset to AUTO.
Create a channel with xmltvid 1036.dvb.guide.
Then import the attached XMLTV EPG data. All programs prior to 3pm are incorrectly loaded into the guide. For example Herbie Fully Loaded should start at 1:40pm and has been scheduled for 2:40pm. After 3pm the DST offset is correct.
I have confirmed that this issue wasn't present on an older Knoppmyth environment running MythTV 0.20 with the same EPG data.
Attachments (1)
Change History (6)
by , 16 years ago
| Attachment: | 1036.dvb.guide.xml.gz added |
|---|
comment:1 by , 16 years ago
comment:2 by , 16 years ago
| Milestone: | 0.23 → unknown |
|---|
Please see the tickethowto, don't set milestones.
comment:5 by , 13 years ago
| Component: | MythTV - General → MythTV - Mythfilldatabase |
|---|---|
| Type: | defect → Bug Report - General |
In fact, no, this won't have been fixed in 0.27. The bug is in the xmltv grabber, it's specifying a constant +1200 offset across the DST transition instead of switching to +1300/+1100

This bug has also been reported in Launchpad under