You need to get to know:
- brave://flags
- brave://gpu
- graphics card
- graphics settings
According to Brave Search (using Answer with AI):
This issue is a known rendering regression in Brave Browser 1.83.x (and later versions) on Linux systems using Wayland , particularly with KDE Plasma . When hardware acceleration is enabled, the cursor may appear white, invisible, or washed out due to conflicts with the WaylandWpColorManagerV1 protocol or HDR color space handling.
To resolve the white cursor or washed-out display issues, apply one of the following workarounds:
- Disable Hardware Acceleration : Go to Settings > System and toggle off Use graphics acceleration when available . This is the most reliable fix but may impact performance.
- Launch with Specific Flags : Start Brave with the following command-line arguments to bypass the problematic color management feature:
brave-browser --disable-features=WaylandWpColorManagerV1
- Force sRGB Color Profile : If the previous flag alone does not work, add the color profile flag to force standard color rendering:
brave-browser --disable-features=WaylandWpColorManagerV1 --force-color-profile=sRGB
- Use X11 Session : Switching from a Wayland session to an X11 session in your display manager often resolves these color management conflicts entirely.
This behavior is linked to upstream Chromium changes in Wayland color management and has been reported as a bug in both Brave and other Chromium-based browsers like Chrome and Vivaldi.
White cursor issue reported March 30, 2026:
‘Text Cursor (I-beam) turns white completely over white screen’
See related issues.