Latest Fedora update broke Google Chrome and some extensions UI

Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.2.15-300.fc38.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz
Memory: 15.5 GiB of RAM
Graphics Processor: NV136

I applied all updates available last night 5/27/2023 and something broke the UI in Google Chrome (latest release) and browser extension Raindrop.io. Removing and reinstalling didn’t fix the issue, rebooting and doing all that also had no effect.

Firefox works, and I installed MS Edge and that UI works, however, the raindrop.io browser extension still has UI problems.

I understand that Chrome is Google’s problem and raindrop is theirs, however, if the latest microcode or other fedora patches has impacted UI changes, you should know about it and address it.

Can you describe this more specially? No UI appears? An empty window? Rendered, but nonfunctional? Or some other glitch?

1 Like

Here it is

2 Likes

@sparcher @mattdm
Yes, precisely. Elements of the UI vanish, don’t render, or just glitch out.

Hi @mattdm a screenshot was just posted here by @sparcher which shows the exact problem, parts of the Google Chrome UI and his extension just vanish or glitch out. Firefox, Chromium (not fully tested) and MS Edge do not appear to have this issue, however, the raindrop extension, regardless of which browser it’s installed on, does and we can see from @sparcher screenshot, so do other extensions. Not all my browser extensions are impacted, so far (for me) it’s just my raindrop extension.

I am having the same issue with just using Chrome. Elements are not drawn correctly. Even browsing this Fedoraproject.org site has issues where just scrolling the page things are not painted correctly. If I lauch Chrome and go to the address bar and type in an address, the left half of the dropdown box is not drawn and only half the box is populated.
Something is broken.

1 Like

The workaround for me was to disable Hardware Acceleration in Chrome Settings.

Screenshot_20230528_075345

2 Likes
[archer@DELLV ~]$ google-chrome --disable-gpu
MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete
libva error: /usr/lib64/dri/iHD_drv_video.so init failed
failed to open /usr/lib64/dri/hybrid_drv_video.so
INFO: Created TensorFlow Lite XNNPACK delegate for CPU.

works
but errors present

Chrome not rendering text after mesa driver update - #2 by vgaetera

2 Likes

Thanks that fixed it, after last update a few minutes ago I got the same exact issue.

People talk crap from Windows updates but Fedora is on a completely different level, several updates per day and always something gets broken :slight_smile:

Not exactly true.
I very seldom see problems and have been using fedora since Fedora Core 1 was released.

maybe its recent then? Iam using it for about 2 weeks, it is always getting updates. The breaking part mea culpa I try to make it do more than I should and most times don’t really know what Iam doing.

Not to get into a war or anything, but I’ve been using Fedora Workstation for 2-weeks, been using Linux for 20 years overall and supporting large data infrastructures for 30 years.

I’ve experienced exactly 3 problems since I’ve been using it.

  1. Chrome problem after update.
  2. Bluetooth connection issues with my Bose Headset
  3. KSystemLog issues that apparently date back to 2013

I’m not sure how you can claim that you “seldom see problems” when I’ve experienced three issues that caused me to delete a browser and install and configure less desirable browsers (the time spent troubleshooting), how incredibly frustrating the bluetooth issue is which there’s no fix for (for some reason) and the other random weirdness, all in the span of two weeks.

And I’m certain other issues will pop up in the near term. I’ve had to fresh install Fedora Desktop three times due to nvidia modules hosing the system before I got this “stable” version running.

Every distro has issues, it’s free after all. Having said that, overall, I’m really enjoying Fedora given the bumps in the road and I’m looking forward to it getting better.

For whatever it is worth: I would love it if we had the ability to put out updates more frequently if need be, but our current infrastructure pushes batches of updates daily.

Please remember that Fedora is an integrator — we package literally thousands of independent upstream software projects and make them available to you. These comprise both what you might think of as the “core” operating system and other applications and utilities you can install.

When these projects have updates, our packagers — largely volunteers — make those available to you, as quickly as possible. These often are security fixes, or solve serious problems.

I don’t know what’s wrong with with Chrome. Chrome is not open source software, so it’s not really involved in our effort to bring all this amazing community-built software to the world. I’m glad it generally works, and I hope Google fixes whatever the problem is soon.

3 Likes

That about the updates I just found it funny, whenever I watch videos claiming how Linux is so much better than windows they always speak about the updates and fedora as so much more. But at least I don’t think they are forced in anyway that’s better.

I had a similar or even identical experience, taking into account the cases reported here about updating Google’s Chrome browser.

When opening Chrome it appeared in the upper right corner that the browser was out of date.

So I selected upgrade and the Fedora OS asked for my password to proceed with the upgrade.

As it was the first time this password request happened, I decided to uninstall it.

Note: without installing the update, the browser stopped working.

Now, reading this post I decided to download it to perform a new installation.

After the download completed, I right-clicked on the Install Program option.

The Programs window opened and shortly after a Fedora dialog box appeared asking: wait or force quit?

I opted to force quit and deleted the downloaded file and downloaded it again.

On this second attempt, the Programs window opened normally and the blue ‘install’ button appeared.

The installation was successful and I’m back to using Chrome along with Firefox, which is the native browser.

Thank you for your attention.

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

2 Likes

That worked here, where I run Wayland on Geforce 108Ti using the default Fedora driver, NV132.

Thanks!

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.

Kernel: 6.2.15-300.fc38.x86_64
iGPU: Iris Xe 96EU (i9-12900HK)
dGPU: NVIDIA RTX 3060Ti mobile
NVIDIA driver: 525.116.04
intel-gpu-firmware-20230515-150
xorg-x11-drv-intel-2.99.917-55.20210115
oneVPL-intel-gpu-23.1.3-2

This is what I was able to see in journalctl:

May 29 19:22:23 google-chrome.desktop[4458]: // Vertex SKSL
May 29 19:22:23 google-chrome.desktop[4458]: #extension GL_NV_shader_noperspective_interpolation: require
May 29 19:22:23 google-chrome.desktop[4458]: uniform float4 sk_RTAdjust;in float2 position;in float coverage;in float2 localCoord;in float4 texSubset;noperspective out float2 vloc>
May 29 19:22:23 google-chrome.desktop[4458]: float2 position = position.xy;vlocalCoord_S0 = localCoord;vtexSubset_S0 = texSubset;vcoverage_S0 = coverage;sk_Position = position.xy0>
May 29 19:22:23 google-chrome.desktop[4458]: // Fragment SKSL
May 29 19:22:23 google-chrome.desktop[4458]: #extension GL_NV_shader_noperspective_interpolation: require
May 29 19:22:23 google-chrome.desktop[4458]: uniform sampler2D uTextureSampler_0_S0;
May 29 19:22:23 google-chrome.desktop[4458]: noperspective in float2 vlocalCoord_S0;flat in float4 vtexSubset_S0;noperspective in float vcoverage_S0;void main() {// Stage 0, QuadP>
May 29 19:22:23 google-chrome.desktop[4458]: half4 outputColor_S0 = half4(1);float2 texCoord;texCoord = vlocalCoord_S0;float4 subset;subset = vtexSubset_S0;texCoord = clamp(texCoo>
May 29 19:22:23 google-chrome.desktop[4458]: sk_FragColor = outputColor_S0 * outputCoverage_S0;}}
May 29 19:22:23 google-chrome.desktop[4458]: // Vertex GLSL
May 29 19:22:23 google-chrome.desktop[4458]: #version 300 es
May 29 19:22:23 google-chrome.desktop[4458]: #extension GL_NV_shader_noperspective_interpolation : require
May 29 19:22:23 google-chrome.desktop[4458]: precision mediump float;
May 29 19:22:23 google-chrome.desktop[4458]: precision mediump sampler2D;
May 29 19:22:23 google-chrome.desktop[4458]: uniform highp vec4 sk_RTAdjust;
May 29 19:22:23 google-chrome.desktop[4458]: in highp vec2 position;
May 29 19:22:23 google-chrome.desktop[4458]: in highp float coverage;
May 29 19:22:23 google-chrome.desktop[4458]: in highp vec2 localCoord;
May 29 19:22:23 google-chrome.desktop[4458]: in highp vec4 texSubset;
May 29 19:22:23 google-chrome.desktop[4458]: noperspective out highp vec2 vlocalCoord_S0;
May 29 19:22:23 google-chrome.desktop[4458]: flat out highp vec4 vtexSubset_S0;
May 29 19:22:23 google-chrome.desktop[4458]: noperspective out highp float vcoverage_S0;
May 29 19:22:23 google-chrome.desktop[4458]: void main() {
May 29 19:22:23 google-chrome.desktop[4458]:     highp vec2 position = position;
May 29 19:22:23 google-chrome.desktop[4458]:     vlocalCoord_S0 = localCoord;
May 29 19:22:23 google-chrome.desktop[4458]:     vtexSubset_S0 = texSubset;
May 29 19:22:23 google-chrome.desktop[4458]:     vcoverage_S0 = coverage;
May 29 19:22:23 google-chrome.desktop[4458]:     gl_Position = vec4(position, 0.0, 1.0);
May 29 19:22:23 google-chrome.desktop[4458]:     gl_Position = vec4(gl_Position.xy * sk_RTAdjust.xz + gl_Position.ww * sk_RTAdjust.yw, 0.0, gl_Position.w);
May 29 19:22:23 google-chrome.desktop[4458]: }
May 29 19:22:23 google-chrome.desktop[4458]: // Fragment GLSL
May 29 19:22:23 google-chrome.desktop[4458]: #version 300 es
May 29 19:22:23 google-chrome.desktop[4458]: #extension GL_NV_shader_noperspective_interpolation : require
May 29 19:22:23 google-chrome.desktop[4458]: precision mediump float;
May 29 19:22:23 google-chrome.desktop[4458]: precision mediump sampler2D;
May 29 19:22:23 google-chrome.desktop[4458]: out mediump vec4 sk_FragColor;
May 29 19:22:23 google-chrome.desktop[4458]: uniform sampler2D uTextureSampler_0_S0;
May 29 19:22:23 google-chrome.desktop[4458]: noperspective in highp vec2 vlocalCoord_S0;
May 29 19:22:23 google-chrome.desktop[4458]: flat in highp vec4 vtexSubset_S0;
May 29 19:22:23 google-chrome.desktop[4458]: noperspective in highp float vcoverage_S0;
May 29 19:22:23 google-chrome.desktop[4458]: void main() {
May 29 19:22:23 google-chrome.desktop[4458]:     mediump vec4 outputColor_S0 = vec4(1.0);
May 29 19:22:23 google-chrome.desktop[4458]:     highp vec2 texCoord;
May 29 19:22:23 google-chrome.desktop[4458]:     texCoord = vlocalCoord_S0;
May 29 19:22:23 google-chrome.desktop[4458]:     highp vec4 subset;
May 29 19:22:23 google-chrome.desktop[4458]:     subset = vtexSubset_S0;
May 29 19:22:23 google-chrome.desktop[4458]:     texCoord = clamp(texCoord, subset.xy, subset.zw);
May 29 19:22:23 google-chrome.desktop[4458]:     outputColor_S0 = texture(uTextureSampler_0_S0, texCoord, -0.5);
May 29 19:22:23 google-chrome.desktop[4458]:     highp float coverage = vcoverage_S0;
May 29 19:22:23 google-chrome.desktop[4458]:     mediump vec4 outputCoverage_S0 = vec4(coverage);
May 29 19:22:23 google-chrome.desktop[4458]:     {
May 29 19:22:23 google-chrome.desktop[4458]:         sk_FragColor = outputColor_S0 * outputCoverage_S0;
May 29 19:22:23 google-chrome.desktop[4458]:     }
May 29 19:22:23 google-chrome.desktop[4458]: }
May 29 19:22:23 google-chrome.desktop[4458]: Errors:
May 29 19:22:23 google-chrome.desktop[4458]: link failed but did not provide an info log
May 29 19:22:23 google-chrome.desktop[4458]: [5644:5644:0529/192223.270176:ERROR:shared_context_state.cc(77)] Skia shader compilation error

I found a workaround through this Chromium bug report that pointed to this Arch Linux thread:

cd ~/.config/google-chrome/
rm -rf 'Your Profile Directory'/GPUCache

Things are working again for me. I even reinstalled the NVIDIA driver and it’s all fine.

2 Likes