SUMMARY Usually after restart, screen start as blue, without NC, then after 20-30 sec, NC applies and it's ok. But sometimes after restart NC fails to load entirely. The icon (lamp) is there, says it's ON, but the screen is blue (no NC). The workaround is to click on the icon two times to turn both the screen yellow and to return NC to ON. Software: Latest KDE, Arch linux, Nvidia drivers 455.38. Also color corrected displays, two monitors.
Can confirm. This also happens after KWin is restarted.
Experiencing this also in Fedora 33 (Plasma 5.20) The Plasma splash screen shows briefly the night colour correction but then reverts to normal. Once the desktop appears I need to click two times on the widget icon to get the correction applied.
For some reason this bug is even more active than before. Happens every 2nd or 3rd restart. It used to be like 1 out of 5. Operating System: Arch Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 Kernel Version: 5.9.8-arch1-1 OS Type: 64-bit Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31,4 GiB of RAM Graphics Processor: GeForce GTX 1060 6GB/PCIe/SSE2
*** Bug 430203 has been marked as a duplicate of this bug. ***
Any news on this, or some further info needed? This stopped working entirely for me. Before it was so-so, working every now and then, but now every time I reset the PC I have to manually apply the nightcolor layer. It just doesn't work. And I changed the GPU too, now I use AMD. So it's not GPU or video drivers related issue.
Maybe this helps to narrow it down - I'm experiencing this bug on Operating System: Fedora 33 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.2 Kernel Version: 5.9.15-200.fc33.x86_64 OS Type: 64-bit Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15,6 GiB of RAM Graphics Processor: Radeon RX 5500 XT whereas everything is working as expected on Operating System: Pop!_OS 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-7630-generic OS Type: 64-bit Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: Radeon RX 5500 XT
Similar issue here. After a restart, I can briefly see the screen color get warmer as the welcome screen is displayed, but it quickly reverts back to normal (before the desktop even appears). The lightbulb icon is ON, but night color needs to be switched off and on again (by clicking on the icon) to engage properly. Operating System: Fedora 33 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.2 Kernel Version: 5.9.16-200.fc33.x86_64 OS Type: 64-bit Processors: 8 x Intel Core i7-1065G7 Memory: 15,6 GiB of RAM Graphics Processor: Mesa Intel Iris Plus Graphics
(In reply to Clément Labadie from comment #7) > Similar issue here. > > After a restart, I can briefly see the screen color get warmer as the > welcome screen is displayed, but it quickly reverts back to normal (before > the desktop even appears). The lightbulb icon is ON, but night color needs > to be switched off and on again (by clicking on the icon) to engage properly. > > Operating System: Fedora 33 > KDE Plasma Version: 5.20.4 > KDE Frameworks Version: 5.75.0 > Qt Version: 5.15.2 > Kernel Version: 5.9.16-200.fc33.x86_64 > OS Type: 64-bit > Processors: 8 x Intel Core i7-1065G7 > Memory: 15,6 GiB of RAM > Graphics Processor: Mesa Intel Iris Plus Graphics Exactly, the KDE sign at the login is yellowish, but as soon as desktop is displayed it's blue/normal and very rarely switches back to yellow again. In my case, this never worked good (I started using KDE ~2 months ago) but lately it's just almost always off.
I also experience this bug. When I start my computer before the night color switching time, it does not take night color settings: the screen color is normal. When the time arrives for night color to start changing, all of a sudden it takes the night color setting, colors change to warm and starts transitioning.
Also experiencing this. Operating System: Kubuntu 20.04 KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-051100-generic OS Type: 64-bit Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 PRO 4750U with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD RENOIR
I am also experiencing this problem. I have had this issue since I first used the KDE Plasma Desktop (5.19). Operating System: openSUSE Tumbleweed KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.11.12-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000
I'm having the same issue. Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-16-generic OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620
*** Bug 436612 has been marked as a duplicate of this bug. ***
Can confirm this bug is still present (5.23.5, Garuda Linux)
*** Bug 448943 has been marked as a duplicate of this bug. ***
I am not sure if this was mentioned elsewhere, but I believe to problem is caused by a conflict between Night Color and 'Gamma Settings'. Night Color has worked consistently well for me (Plasma 5.24.1) until I open the 'Display Configuration' KCM in System Settings. Doing so would immediately 'reset' the display, getting rid of Night Color's red tint (while Night Color is still enabled.) Maybe that's why Night Color would 'disappear' shortly after activating at login, 'Gamma Settings/Display Configuration' gets triggered and fiddles with the gamma values. I have tested in X11, not sure how the Wayland session handles that. Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-150300.59.49-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000
(In reply to Lemuel Simon from comment #16) > I am not sure if this was mentioned elsewhere, but I believe to problem is > caused by a conflict between Night Color and 'Gamma Settings'. Night Color > has worked consistently well for me (Plasma 5.24.1) until I open the > 'Display Configuration' KCM in System Settings. Doing so would immediately > 'reset' the display, getting rid of Night Color's red tint (while Night > Color is still enabled.) Maybe that's why Night Color would 'disappear' > shortly after activating at login, 'Gamma Settings/Display Configuration' > gets triggered and fiddles with the gamma values. > > I have tested in X11, not sure how the Wayland session handles that. > > Operating System: openSUSE Leap 15.3 > KDE Plasma Version: 5.24.1 > KDE Frameworks Version: 5.91.0 > Qt Version: 5.15.2 > Kernel Version: 5.3.18-150300.59.49-default (64-bit) > Graphics Platform: X11 > Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz > Memory: 7.6 GiB of RAM > Graphics Processor: Mesa DRI Intel® HD Graphics 4000 I'm wondering if this is related: https://bugs.kde.org/show_bug.cgi?id=413134
I'm also saw this issue, in my case it's been conflict with gnome-color-manager. NightColor is enabled and then disabled at start by the color manager with some problems with ICC profile. I have removed gnome-color-manager package and NightColor works fine now.
*** Bug 462126 has been marked as a duplicate of this bug. ***
Git commit 8d047336824037998c271a2adea426fd221b0505 by Vlad Zahorodnii. Committed on 01/12/2022 at 09:56. Pushed by vladz into branch 'master'. plugins/nightcolor: Register its own service name In order to make monitoring Night Color appearing and disappearing robust, make Night Color register its own dbus service. M +6 -0 src/plugins/nightcolor/nightcolordbusinterface.cpp M +1 -1 src/plugins/nightcolor/nightcolordbusinterface.h https://invent.kde.org/plasma/kwin/commit/8d047336824037998c271a2adea426fd221b0505
Git commit 8234c4b5f9e03abba54761fb99bb700142f64d25 by Vlad Zahorodnii. Committed on 01/12/2022 at 09:58. Pushed by vladz into branch 'master'. applets/nightcolor: Use org.kde.NightColor service name M +1 -1 applets/nightcolor/plugin/inhibitor.cpp M +1 -1 applets/nightcolor/plugin/monitor.cpp https://invent.kde.org/plasma/kdeplasma-addons/commit/8234c4b5f9e03abba54761fb99bb700142f64d25
It seems this report was automatically closed (?) but the bug is still present in KDE 5.27.6.
The original issue was fixed, but a new one cropped up, which is now fixed in Plasma 5.27.8; See Bug 461657. If you're still encountering the issue in 5.27.8 (which will be released in about 6 weeks), please leave a comment in that bug report, but don't re-open it. Someone else will re-open it if your issue looks like the same thing. Thanks!
(In reply to Nate Graham from comment #23) > The original issue was fixed, but a new one cropped up, which is now fixed > in Plasma 5.27.8; See Bug 461657. If you're still encountering the issue in > 5.27.8 (which will be released in about 6 weeks), please leave a comment in > that bug report, but don't re-open it. Someone else will re-open it if your > issue looks like the same thing. Thanks! Hey, I am running 5.27.8 (Ubuntu 23.10) and experiencing the issue