| Bug ID | 104201 |
|---|---|
| Summary | [Vega10, regression] Night Light in GNOME is applied only to = one monitor on Vega 64 |
| Product | DRI |
| Version | DRI git |
| Hardware | All |
| OS | All |
| Status | NEW |
| Severity | major |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | vedran@miletic.net |
I'm using amd-staging-drm-next c55469bdd90b83bd31b40dd1eca5e50= 678731ac1 on 43:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] [1002:687f] (rev c1) I have three AOC 1080p monitors connected over DP; xrandr gives Screen 0: minimum 320 x 200, current 5760 x 1080, maximum 8192 x 8192 XWAYLAND0 connected 1920x1080+3840+0 (normal left inverted right x axis y a= xis) 600mm x 340mm 1920x1080 59.96*+ XWAYLAND1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 600mm x 340mm 1920x1080 59.96*+ XWAYLAND2 connected 1920x1080+1920+0 (normal left inverted right x axis y a= xis) 600mm x 340mm 1920x1080 59.96*+ Night Light in GNOME is applied only to the leftmost monitor, and if I do a= VT switch, then it's only applied to the one in the middle. This used to work correctly months ago.
This seems to no longer be the case in 4.15.7 (I should note, = after a clean reinstall of Fedora for an unrelated reason), did anything change?
Our display code in 4.15 would mostly be older than the versio= n of amd-staging-drm-next that you tested earlier. Would you be able to give amd-staging-drm-next a spin again and see if it's still an issue there? We've had some changes in our color programming recen= tly. Note, though, that there's a different bug currently, described by https://bugs.freedesktop.org/show_= bug.cgi?id=3D105083#c11.
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | MOVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/268.