Lots of flickering under Wayland on Nvidia #446
Labels
No labels
bug
completed
documentation
duplicate
enhancement
good first issue
hacktoberfest-accepted
help wanted
information
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Thorium_Archive/thorium#446
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Details
Problem
I am experiencing a lot of flickering (often windows behind the browser momentarily popping up over the browser window). This especially happens when watching videos on YouTube, although it occassionally happens elsewhere, particularly when popping up dialogs (e.g., saving a file). Also, dropdown menus initially appear blank, but if I move the mouse down over them, the menu text appears.
These issues are not occurring with Chromium 119.0.6045.159,
Additional Notes
The problem seems to have gotten noticeably worse since upgrading my nvidia drivers to 29.02. This may be a weird interaction between Thorium, Wayland/Gnome and the Nvidia driver.
Similar issues on Fedora (Nobara) 38. I see similar issues with the Microsoft Edge browser for linux, but likewise, the browsers are functional.
I'm no expert, but this issue reminds me of a problem with the chromium engine. Have you try to enable Wayland support in
chrome://flags
on the browser ?Steps
This may not just be a linux issue, it might be something with nvidia itself. I've had a similar issue for a while now where everything flickers. I'm on Win 11, and just resorted to running thorium via AMD iGPU
I am unsure what the NVidia control panel has for options on linux, but on windows following the suggestion mentioned in this AVX2 build issue worked to fix it on Win11 https://github.com/Alex313031/Thorium-Win-AVX2/issues/112
I suspect MFAA being enabled might be the cause as I had everything else they suggested already set