| Summary: | night color time offset | ||
|---|---|---|---|
| Product: | [Unmaintained] kdeplasma-addons | Reporter: | David Chmelik <dchmelik> |
| Component: | Night Color Control | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | kwin-bugs-null, nate, vlad.zahorodnii |
| Priority: | NOR | ||
| Version First Reported In: | 5.19.4 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
David Chmelik
2020-11-02 07:44:19 UTC
Seems like it's confused about your timezone or something. What is your system timezone set to? And have you set your clock timezone to display something different? My system time zone is set to US Pacific Time (PT: PST, PDT) I have never set my KDE clock time zone because originally it was fine (said PDT.) Now (after daylight saving time stopped) the clock reset its label/zone to UTC (and won't let me change back, as mentioned in another bug) except is still actually showing PST time fine. However this night colour problem was happening weeks/months before the clock reset its labelled zone. The offset time isn't a problem in 5.20.2, anyway (just I don't know when my operating system will get a KDE upgrade.) Oh I bet this is the same problem as your general timezones-with-freebsd issue. *** This bug has been marked as a duplicate of bug 428591 *** It's not a duplicate, as was happening on FreeBSD and Slackware when my time zones were normal: showing PDT and labelled PDT. Oops, sorry. After KDE finally accepted my time zone (after several error messages & failures) this is currently not a problem... but would be if KDE was using my PC's internal clock time that's correct for my time zone (PT) but KDE automatically chose the wrong time zone and it didn't let me change (UTC, which is what had happened)... now it does. Maybe this was a duplicate then... Yes, I suspected as much. :) *** This bug has been marked as a duplicate of bug 428591 *** |