Bug 429053 - night color doesn't accept custom time
Summary: night color doesn't accept custom time
Status: RESOLVED DUPLICATE of bug 415028
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_nightcolor (show other bugs)
Version: 5.20.2
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-13 10:56 UTC by David Chmelik
Modified: 2021-09-09 15:50 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Chmelik 2020-11-13 10:56:21 UTC
SUMMARY
Night color doesn't accept custom time, and if you use 24hr, you have to start on the second digit, then can go back to the first digit.

STEPS TO REPRODUCE
1. Activate night color.
2. Put in a normal (or non-normal) night colour time like 19:15 to 06:00apply
3. Select apply

OBSERVED RESULT

You come back and it wasn't applied and is reset to deactivated.

EXPECTED RESULT

Use the custom time.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Slackware 14-current/5.20.2
(available in About System)
KDE Plasma Version: 5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 David Chmelik 2020-11-18 23:30:46 UTC
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.

I don't know how KDE defines time, but apparently you allow using the system clock (mine is never set to UTC) but a separate time zone (without recalculating/resetting the system clock) in which case this could still be a problem for people (no idea why they'd do that, as usually it's done in the OS if they set it to UTC like a server then set their time zone.)
Comment 2 David Edmundson 2021-09-09 15:50:19 UTC

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