You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I've been trying to debug this for some time now and haven't come up with much yet, so I thought I'd report this here seeing as it is a common bug between cage and cagebreak:
Some time back, the gamma control protocol was implemented for cage which is why I expected that gammastep -o -O 1000 would allow me to set the color temperature. However, for some reason which is unknown to me it seems that this command produces no effect whatsoever in either cage or cagebreak. Running it under sway does produce the desired fact and adding wlr_gamma_control_manager_v1_create to tinywl allows one to set the gamma values there too. That's pretty much all I've been able to figure out about this bug exept that it is probably not a rendering bug. Do you have any idea what might be causing this behaviour?
cheers,
project-repo
The text was updated successfully, but these errors were encountered:
OK, so I was able to figure out what the problem was and as it seems, this is a wlroots bug: Setting the redshift is broken only when scanning out a fullscreen view. The reason I was first unable to reproduce this in sway was that it does not display windows fullscreen by default meaning that it was not scanning out the views while cage and cagebreak were.
I will report this to the wlroots developers, feel free to close this issue if you like.
cheers,
project-repo
Hi,
I've been trying to debug this for some time now and haven't come up with much yet, so I thought I'd report this here seeing as it is a common bug between
cage
andcagebreak
:Some time back, the gamma control protocol was implemented for cage which is why I expected that
gammastep -o -O 1000
would allow me to set the color temperature. However, for some reason which is unknown to me it seems that this command produces no effect whatsoever in eithercage
orcagebreak
. Running it undersway
does produce the desired fact and addingwlr_gamma_control_manager_v1_create
totinywl
allows one to set the gamma values there too. That's pretty much all I've been able to figure out about this bug exept that it is probably not a rendering bug. Do you have any idea what might be causing this behaviour?cheers,
project-repo
The text was updated successfully, but these errors were encountered: