Bug 510247

Summary: Wrong time displayed for other time zones
Product: [Plasma] plasmashell Reporter: Andrew Moore <andrewm.finewolf>
Component: Digital Clock widgetAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: filip.kendes1
Priority: NOR    
Version First Reported In: 6.4.5   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Time should be 7:30 PM (America/Toronto) and 11:30 PM (UTC) respectively

Description Andrew Moore 2025-10-04 23:35:48 UTC
Created attachment 185523 [details]
Time should be 7:30 PM (America/Toronto) and 11:30 PM (UTC) respectively

SUMMARY
The wrong time is displayed for UTC and America/Toronto after a DST switch for system timezone (Australia/Adelaide)

STEPS TO REPRODUCE
1. Set system timezone to Australia/Adelaide
2. Add UTC and America/Toronto as additional timezones

OBSERVED RESULT
The times for America/Toronto and UTC are off by -1 hour

EXPECTED RESULT
The proper times for America/Toronto and UTC are displayed

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2

ADDITIONAL INFORMATION
`TZ=America/Toronto date` returns the proper date/time.
Comment 1 Andrew Moore 2025-10-05 09:33:34 UTC
More information:

The DST transition for Australia/Adelaide happened today (Oct. 5).

It seems that, however, the DST transition of the system timezone is calculated in relation to the timezone being evaluated instead of the local system time. Since UTC and America/Toronto was still behind Oct 5, 2am, the time difference between the system timezone and the target timezone was badly calculated.

As soon as the timezone being evaluated passed Oct 5, 2am, then the time displayed was correct. THIS BEHAVIOUR IS WRONG, and leads to the wrong time being displayed.

That said, now all my clocks are displaying the right time.
Comment 2 Filip 2025-10-05 18:04:40 UTC
Looks like a duplicate of 483045

*** This bug has been marked as a duplicate of bug 483045 ***