I’ve been using Linux since spring 2002.
Yes, for 21 years.
And only once had intend to return to the windows - in the fall of 2002.
But I stayed with Linux.
And I don’t regret it at all.
P.S.
my wife is a linux-woman
my daughter is a linux-girl
my grandson is a linux-kid
I’m having the same issue today after rebooting with new updates.
I thought it was NVIDIA so I updated the driver, same issue.
I uninstalled the NVIDIA driver (and didn’t install nouveau so using the iGPU), same issue.
Now without NVIDIA at all and having disabled GPU usage in Chrome (chrome://flags → Disable GPU rasterization disabled GPU in settings), things are a bit more stable, but the screen still blinks sometimes.
The issue is that things that use Electron are still broken (eg. Zoom, Slack, etc)
E.g.: in Zoom I can’t click the “View” button sometimes. It doesn’t draw on the screen anymore and it was working before the reboot. It’s hard to pinpoint what’s the issue.
Curiosity is good, but Linux systems are giving you much more opportunity to shoot yourself in foot. That’s because they are “open to the bone”, and give you freedom to tinker however you like. It takes time and effort to get to some level of proficiency. It’s good to learn basics, and not to explore too many new things at once (it messes your head). Btw. updates are good thing. Learn how to use dnf system as soon as possible.
I wish you as much great time with Fedora as I had for last 23 years (started with Red Hat before Fedora became Fedora).
It looks like you updated and later downloaded chrome from google’s website and not from google’s repo with chrome for fedora. Or, did I misunderstood?
I had the same thing, the problem with Chrome was fixed by disabling hardware acceleration in Chrome. The symptoms looked like a combination of improper rendering, where images were displayed as garbage, as if non-image files were being displayed as images, and Javascript animations were simply removing the animated item from the page, permanently, as if the elements were removed from the DOM. (They were not removed, just removed from rendering)
@sparcher Have you experienced this problem with Opera as well? I guess it makes sense, theoretically it affects everything Chromium-based (if GPU acceleration is enabled there).
I had some other software that also used chrome that presented the same issues. the fixes here are only partial not 100% working just a quick workaround the issues should remain on many parts.
I did not check much more because I need chrome to work so I just left fedora in stand by for a while
I just ran a general update and this issue is now fixed. Chrome was updated, as was Fedora, so I have no clue where the fix came from. If you were involved in creating the fix, thank you!
I’ve stumbled over this issue this morning with Slack and Vivaldi, which is quite late regarding the time the issue is known. Deleting any CPUcache directories found in ~/.config/vivaldi and .config/Slack/ fixed the issue, though. But: Any ideas why this happened so late to me?