Bug 464189 - Sometimes when I activate the second monitor, the night color sets itself as temperature of the night
Summary: Sometimes when I activate the second monitor, the night color sets itself as ...
Status: REPORTED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_nightcolor (show other bugs)
Version: 5.26.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-12 11:40 UTC by Salvatore
Modified: 2023-02-23 13:13 UTC (History)
4 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 Salvatore 2023-01-12 11:40:38 UTC
SUMMARY

When I activate the second monitor via the monitor widget, the monitor often turns on blue light. To get it back to diurnal (AM) temperature, I have to go into the night color settings and change the daytime color temperature


STEPS TO REPRODUCE
1.  I activate the second monitor (on the left) via the Plasma panel widget
2.  The color of the screen changes temperature, it switches to that of the night even if it is not night
3.  To get it back to normal, I have to go into the night color settings and change the diurnal color temperature


EXPECTED RESULT

When I activate the second monitor, it doesn't change temperature

System info:

Operating System: Arch Linux
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.8
Kernel Version: 6.1.4-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics
Graphics Processor: AMD Radeon Graphics


ADDITIONAL INFORMATION

This has been happening to me since the option was added to change the diurnal color temperature as well

Currently my settings are:
sunset and sunrise at current location (Italy)
Diurnal Color Temperature: Cold (No filter)
Night color temperature: 3.100k
Comment 1 Nate Graham 2023-01-12 20:19:48 UTC
Same issue as Bug 453374; see the explanation there.

*** This bug has been marked as a duplicate of bug 453374 ***
Comment 2 Nate Graham 2023-01-12 20:20:43 UTC
Oops, sorry, that message was intended for a different bug report.
Comment 3 Salvatore 2023-01-13 09:08:58 UTC
I have additional information: This happens more often when I turn on the second monitor the first time after turning on the computer

I also have a video that I uploaded to Youtube. I couldn't upload it here because the file is 19mb and the limit here is 4mb, sorry if I can't post links

https://www.youtube.com/watch?v=wH5bCclUa9s
Comment 4 Vlad Zahorodnii 2023-01-13 13:04:22 UTC
Can you run

   qdbus org.kde.KWin /ColorCorrect org.freedesktop.DBus.Properties.GetAll org.kde.kwin.ColorCorrect && echo "currentTime: $(date +%s)"

before and after connecting second monitor?
Comment 5 Salvatore 2023-01-13 14:17:23 UTC
(In reply to Vlad Zahorodnii from comment #4)
> Can you run
> 
>    qdbus org.kde.KWin /ColorCorrect org.freedesktop.DBus.Properties.GetAll
> org.kde.kwin.ColorCorrect && echo "currentTime: $(date +%s)"
> 
> before and after connecting second monitor?

All right. It might take me a day or two to post this because, I don't know why, this thing doesn't happen every time I activate the monitor
Comment 6 Salvatore 2023-01-14 09:10:12 UTC
Before:

available: true
currentTemperature: 6500
enabled: true
inhibited: false
mode: 0
previousTransitionDateTime: 1673675800
previousTransitionDuration: 2850556
running: true
scheduledTransitionDateTime: 1673710887
scheduledTransitionDuration: 2850556
targetTemperature: 6500
currentTime: 1673687246

After:

available: true
currentTemperature: 6500
enabled: true
inhibited: false
mode: 0
previousTransitionDateTime: 1673675800
previousTransitionDuration: 2850556
running: true
scheduledTransitionDateTime: 1673710887
scheduledTransitionDuration: 2850556
targetTemperature: 6500
currentTime: 1673687257


Doesn't change anything, or am I wrong?
Comment 7 Vlad Zahorodnii 2023-01-17 09:40:04 UTC
No..

> After:
>
> available: true
> currentTemperature: 6500
> ...
> targetTemperature: 6500

That's when the screen is red, right?
Comment 8 Salvatore 2023-01-17 14:29:15 UTC
(In reply to Vlad Zahorodnii from comment #7)
> No..
> 
> > After:
> >
> > available: true
> > currentTemperature: 6500
> > ...
> > targetTemperature: 6500
> 
> That's when the screen is red, right?

Yes. I noticed another thing, the screen turns red when I activate the second monitor in the morning, if I activate it now the problem is not there. Tomorrow morning (Italian time) I'll try again to confirm. Now here it's 3:29 so that's not the problem
Comment 9 Bug Janitor Service 2023-02-01 05:03:26 UTC
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!
Comment 10 Salvatore 2023-02-13 16:57:00 UTC
How can I give more information?
Comment 11 Tony 2023-02-23 13:13:30 UTC
Can confirm this bug. Selecting "Extend to left/right" screen layout option turns on blue light on primary monitor if it was off, or turns it off if it already was on. Holding mouse button pressed on "Night color temperature" slider in order to preview temperature inside System Settings fixes issue.

Some system info
Operating System: EndeavourOS (Arch Linux)
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.12-1-lts (64-bit)
Graphics Platform: X11