Cursor is now affected by redshift gamma ramps
Brief summary of the problem:
After updating the kernel, under X11, the cursor is now noticeably affected by gamma ramps as applied by redshift. This behaviour was introduced by drm/amd/display: don't enable DRM CRTC degamma property for DCE (0e444a4de6b3).
At first I thought this occurred because hardware cursors were no longer being used, but comparing drm_info with and without the commit reverted, assuming I'm understanding it correctly, it seems that they are now used with that commit.
It's really difficult to tell by looking at a screen if it was applied before, but maybe after this change, the gamma ramps are now somehow applied multiple times, intensifying the effect.
When the cursor is moved to the display attached to the card driven by nouveau, it always remains unaffected.
Hardware description:
- GPU:
*-display
description: VGA compatible controller
product: Bonaire XTX [Radeon R7 260X/360] [1002:6658]
vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
physical id: 0
bus info: pci@0000:08:00.0
version: 00
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
configuration: driver=amdgpu latency=0
resources: irq:33 memory:d0000000-dfffffff memory:ef000000-ef7fffff ioport:c800(size=256) memory:feac0000-feafffff memory:c0000-dffff
*-display
description: VGA compatible controller
product: G86 [GeForce 8400 GS] [10DE:422]
vendor: NVIDIA Corporation [10DE]
physical id: 0
bus info: pci@0000:07:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
configuration: driver=nouveau latency=0
resources: irq:30 memory:fd000000-fdffffff memory:b0000000-bfffffff memory:fa000000-fbffffff ioport:bc00(size=128) memory:fe9e0000-fe9fffff
System information:
- Distro name and Version: Ubuntu 20.04.5 LTS
- Kernel version: torvalds/linux.git (b6bb9676f2165d518b35ba3bea5f1fcfc0d969bf)
- Custom kernel: custom config
- Mesa: 22.3.1 - kisak-mesa
How to reproduce the issue:
Run a recent kernel (after the commit that introduced this behaviour) and enable redshift. For example, to force a visible change redshift -t 4000K:4600K
.
Attached files:
Screenshots/video files
Log files
- drm_info with the commit reverted: drm_info_reverted.txt
- drm_info without revert: drm_info_not_reverted.txt