SUMMARY *** Hello, dear KDE developers! I will make a reservation at once that this problem is not observed on the wayland, but occurs in x11. And maybe I chose the wrong kde component. The problem is that if night color mode is activated, it turns on for a moment when you log in (on a black background at the entrance you can see that the cursor glows with warm light), and after the desktop appears, this mode does not paint the screen warm light. If you manually turn off and turn on the night color, the screen is painted warm. *** STEPS TO REPRODUCE 1. Choose x11 on login screen 2. Turn on night color always 3. Reboot pc and login with x11 again OBSERVED RESULT Night color is active in menu but not working EXPECTED RESULT Night color working SOFTWARE/OS VERSIONS Linux/KDE Plasma: fedora 35 (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Hello, I can't reproduce your issue. When I restart my system with Night light active, it will activate as expected. Maybe are you expecting Night light mode in the Login Screen? I'm not sure if login screen windows support Night light mode. My system is: Kubuntu 21.10 Plasma version 5.23.5 x11 Could you please try updating your system to 5.23.5 Regards
waiting for user to try with 5.23.5
(In reply to galdera from comment #1) > Hello, > I can't reproduce your issue. When I restart my system with Night light > active, it will activate as expected. > Maybe are you expecting Night light mode in the Login Screen? > I'm not sure if login screen windows support Night light mode. > My system is: > Kubuntu 21.10 > Plasma version 5.23.5 > x11 > Could you please try updating your system to 5.23.5 > Regards Hello there! Thanks for the answer. As you can see, I use fedora 35 with kde plasma 5.23.4. Maybe it is not plasma fault, but x11, I don't know. It need reproduced on fedora. And I not expect night mode on login screen. But thanks for your info. Glad to hear Ubuntu is not affected
(In reply to galdera from comment #2) > waiting for user to try with 5.23.5
(In reply to galdera from comment #2) > waiting for user to try with 5.23.5 On stable fedora 35 is 5.23.4. Need I change to testing my repos, right?
I think so but I would recommend to wait until Fedora updates the stable repo. regards
(In reply to galdera from comment #6) > I think so but I would recommend to wait > until Fedora updates the stable repo. > regards Okay, thanks for the answer. I'll try to do it on a test PC or on a main one. In any case, I'll write here when I have news.
(In reply to galdera from comment #2) > waiting for user to try with 5.23.5 I update fedora from test repos. Also kde plasma updated to 5.23.5 version. The issue is still there... No have issue with fresh install fedora 35 with kde plasma 5.22.x
Hello Tony, thanks for testing it. Unfortunately I can not reproduce this issue on my system. Using Kubuntu 21,10 5.23.5, night color works as expected in x11. I just need to activated once and it enables automatically depending on the day time. Is set to "sunset to sunrise at current location". Right now is off because the day time but if I "set to "always on" it will warm up the colors automatically. Once I set back "current location is set back off. When I reboot my system works fine, I don't need to activate again.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
*** This bug has been marked as a duplicate of bug 428854 ***