Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Brave doesn't work on Fedora 38 #30179

Open
juchiast opened this issue May 6, 2023 · 24 comments
Open

Brave doesn't work on Fedora 38 #30179

juchiast opened this issue May 6, 2023 · 24 comments

Comments

@juchiast
Copy link

juchiast commented May 6, 2023

Description

UI does not render correctly (no text, flickering, ect.)
Logs have a lot of shader compilation errors:

[16275:16275:0506/135751.025985:ERROR:shared_context_state.cc(77)] Skia shader compilation error

Errors:
link failed but did not provide an info log

Steps to Reproduce

  1. Upgraded from Fedora 37 to Fedora 38
  2. brave-browser-1.51.110-1.x86_64
  3. Running on i3/X11

Actual result:

Screenshot from 2023-05-06 14-00-49

Brave version (brave://version info)

brave-browser-1.51.110-1.x86_64

@juchiast
Copy link
Author

juchiast commented May 6, 2023

Downgraded to brave-browser-1.50.125-1.x86_64 and it worked

@blutch112
Copy link

Same problem for me on Fedora 38 Gnome/Wayland.
The problem commissioned after the last update on system.
Modified packages:
Installer xcb-util-cursor-0.1.4-2.fc38.x86_64 @fedora
Upgrade colord-1.4.6-4.fc38.x86_64 @updates
Upgraded colord-1.4.6-2.fc37.x86_64 @@System
Upgrade colord-libs-1.4.6-4.fc38.x86_64 @updates
Upgraded colord-libs-1.4.6-2.fc37.x86_64 @@System
Upgrade container-selinux-2:2.211.1-1.fc38.noarch @updates
Upgraded container-selinux-2:2.209.0-1.fc38.noarch @@System
Upgrade coreutils-9.1-12.fc38.x86_64 @updates
Upgraded coreutils-9.1-11.fc38.x86_64 @@System
Upgrade coreutils-common-9.1-12.fc38.x86_64 @updates
Upgraded coreutils-common-9.1-11.fc38.x86_64 @@System
Upgrade curl-8.0.1-1.fc38.x86_64 @updates
Upgraded curl-7.87.0-8.fc38.x86_64 @@System
Upgrade gdb-13.1-4.fc38.x86_64 @updates
Upgraded gdb-13.1-3.fc38.x86_64 @@System
Upgrade gdb-headless-13.1-4.fc38.x86_64 @updates
Upgraded gdb-headless-13.1-3.fc38.x86_64 @@System
Upgrade gdm-1:44.0-1.fc38.x86_64 @updates
Upgraded gdm-1:43.0-7.fc38.x86_64 @@System
Upgrade gspell-1.12.1-1.fc38.x86_64 @updates
Upgraded gspell-1.12.0-3.fc38.x86_64 @@System
Upgrade langtable-0.0.62-1.fc38.noarch @updates
Upgraded langtable-0.0.61-3.fc38.noarch @@System
Upgrade libXft-2.3.8-2.fc38.x86_64 @updates
Upgraded libXft-2.3.6-2.fc38.x86_64 @@System
Upgrade libXi-1.8.1-1.fc38.x86_64 @updates
Upgraded libXi-1.8-4.fc38.x86_64 @@System
Upgrade libcurl-minimal-8.0.1-1.fc38.x86_64 @updates
Upgraded libcurl-minimal-7.87.0-8.fc38.x86_64 @@System
Upgrade libheif-1.15.2-1.fc38.x86_64 @updates
Upgraded libheif-1.15.1-2.fc38.x86_64 @@System
Upgrade libsoup3-3.4.2-2.fc38.x86_64 @updates
Upgraded libsoup3-3.4.0-2.fc38.x86_64 @@System
Upgrade llvm-libs-16.0.2-1.fc38.x86_64 @updates
Upgraded llvm-libs-16.0.1-1.fc38.x86_64 @@System
Upgrade mediawriter-5.0.6-2.fc38.x86_64 @updates
Upgraded mediawriter-5.0.6-1.fc38.x86_64 @@System
Upgrade mesa-dri-drivers-23.0.3-3.fc38.x86_64 @updates
Upgraded mesa-dri-drivers-23.0.3-1.fc38.x86_64 @@System
Upgrade mesa-filesystem-23.0.3-3.fc38.x86_64 @updates
Upgraded mesa-filesystem-23.0.3-1.fc38.x86_64 @@System
Upgrade mesa-libEGL-23.0.3-3.fc38.x86_64 @updates
Upgraded mesa-libEGL-23.0.3-1.fc38.x86_64 @@System
Upgrade mesa-libGL-23.0.3-3.fc38.x86_64 @updates
Upgraded mesa-libGL-23.0.3-1.fc38.x86_64 @@System
Upgrade mesa-libgbm-23.0.3-3.fc38.x86_64 @updates
Upgraded mesa-libgbm-23.0.3-1.fc38.x86_64 @@System
Upgrade mesa-libglapi-23.0.3-3.fc38.x86_64 @updates
Upgraded mesa-libglapi-23.0.3-1.fc38.x86_64 @@System
Upgrade mesa-libxatracker-23.0.3-3.fc38.x86_64 @updates
Upgraded mesa-libxatracker-23.0.3-1.fc38.x86_64 @@System
Upgrade mesa-va-drivers-23.0.3-3.fc38.x86_64 @updates
Upgraded mesa-va-drivers-23.0.3-1.fc38.x86_64 @@System
Upgrade mesa-vulkan-drivers-23.0.3-3.fc38.x86_64 @updates
Upgraded mesa-vulkan-drivers-23.0.3-1.fc38.x86_64 @@System
Upgrade mkpasswd-5.5.17-1.fc38.x86_64 @updates
Upgraded mkpasswd-5.5.16-1.fc38.x86_64 @@System
Upgrade python3-langtable-0.0.62-1.fc38.noarch @updates
Upgraded python3-langtable-0.0.61-3.fc38.noarch @@System
Upgrade qgnomeplatform-qt5-0.9.0-14.fc38.x86_64 @updates
Upgraded qgnomeplatform-qt5-0.9.0-13.fc38.x86_64 @@System
Upgrade qgnomeplatform-qt6-0.9.0-14.fc38.x86_64 @updates
Upgraded qgnomeplatform-qt6-0.9.0-13.fc38.x86_64 @@System
Upgrade qt6-qtbase-6.5.0-2.fc38.x86_64 @updates
Upgraded qt6-qtbase-6.4.3-2.fc38.x86_64 @@System
Upgrade qt6-qtbase-common-6.5.0-2.fc38.noarch @updates
Upgraded qt6-qtbase-common-6.4.3-2.fc38.noarch @@System
Upgrade qt6-qtbase-gui-6.5.0-2.fc38.x86_64 @updates
Upgraded qt6-qtbase-gui-6.4.3-2.fc38.x86_64 @@System
Upgrade qt6-qtdeclarative-6.5.0-1.fc38.x86_64 @updates
Upgraded qt6-qtdeclarative-6.4.3-1.fc38.x86_64 @@System
Upgrade qt6-qtsvg-6.5.0-1.fc38.x86_64 @updates
Upgraded qt6-qtsvg-6.4.3-1.fc38.x86_64 @@System
Upgrade qt6-qtwayland-6.5.0-1.fc38.x86_64 @updates
Upgraded qt6-qtwayland-6.4.3-1.fc38.x86_64 @@System
Upgrade whois-5.5.17-1.fc38.x86_64 @updates
Upgraded whois-5.5.16-1.fc38.x86_64 @@System
Upgrade whois-nls-5.5.17-1.fc38.noarch @updates
Upgraded whois-nls-5.5.16-1.fc38.noarch @@System

@blutch112
Copy link

Join console errors:
logbrave.log

@kboddya
Copy link

kboddya commented May 6, 2023

I think that is a problem in Chromium 113 because in chrome with this version I'm the same mistake, with Version 112 and 114 it missing

@supernes
Copy link

supernes commented May 6, 2023

Manually enabling Vulkan from brave://flags fixes 99% of issues on my setup (Fedora 37, Mesa 23.0.3, GNOME on Wayland). Only issue so far is a black bar on the YouTube UI, otherwise usable.

@coyoterj
Copy link

coyoterj commented May 6, 2023

Same problem.
Fedora 38 Linux 6.2.14-300.fc38.x86_64
Brave 113.1.51.110

@rlengland
Copy link

rlengland commented May 7, 2023

Concur on this problem. Essentially a white window with a few blackline artifacts occasionally
Linux foyle 6.2.14-300.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Mon May 1 00:55:28 UTC 2023 x86_64 GNU/Linux
Downgraded to Brave Version 1.50.125 Chromium: 112.0.5615.165 (Official Build) (64-bit) and it works

@buhosiliscodirococo
Copy link

Man, I was putting in overtime at work because I couldn't use Brave-Browser for days. And already in a few days this has problems again? What happen? I loved the browser initially, but lately it's becoming a nuisance, if this persists I'll go back to Firefox, I've used it all my life and no problem.

Fedora 38
Kernel: 6.2.14-300.fc38.x86_64
Captura desde 2023-05-07 12-59-22

Previously I solved it by downgrading and now I will have to do it again. I was updating using "--exclude=brave-browser" but that is not a solution...

@blutch112
Copy link

while waiting for the resolution of the problem, the flatpak version of brave works perfectly with the latest version.

@ggttttggggtt
Copy link

I was able to fix this by clearing Brave's cache and session. I'm not sure how you would do it manually, but I used bleachbit to do it, which is in Fedora's repos.

@coyoterj
Copy link

coyoterj commented May 8, 2023

Now, I updated Brave to version 113.1.51.110 and it's working for me.

@rillian
Copy link

rillian commented May 8, 2023

FWIW I had the same problem. Clearing the cache can be a work around; for me a fresh profile works fine. You can also disable "use hardware accelleration when available" in brave://settings/system

If you can't get that to render so you can click on it, launching from the command line as brave-browser --disable-gpu is similar. This resolved the issue for me.

@rillian
Copy link

rillian commented May 8, 2023

Further debugging info:

I'm on Gnome+Wayland rather than xorg. Effects seem to be the same except I can't take screenshots of the results. :)

For me at least, launching on the command line, there are continuous GLSL compiler errors. similar to the report above. These are also collected at the bottom of the brave://gpu page. The errors don't show up with a clean profile; probably some setting difference triggers a different path.

[32657:32657:0508/152152.223100:ERROR:shared_context_state.cc(77)] Skia shader compilation error
------------------------
// Vertex SKSL
#extension GL_NV_shader_noperspective_interpolation: require
uniform float4 sk_RTAdjust;in float2 position;in float2 localCoord;noperspective out float2 vlocalCoord_S0;void main() {// Primitive Processor QuadPerEdgeAAGeometryProcessor
vlocalCoord_S0 = localCoord;sk_Position = position.xy01;}
// Fragment SKSL
#extension GL_NV_shader_noperspective_interpolation: require
uniform float4 uinnerRect_S1;uniform half2 uradiusPlusHalf_S1;uniform sampler2D uTextureSampler_0_S0;
noperspective in float2 vlocalCoord_S0;half4 CircularRRect_S1(half4 _input) {
float2 dxy0 = uinnerRect_S1.LT - sk_FragCoord.xy;float dx1 = sk_FragCoord.x - uinnerRect_S1.R;float2 dxy = max(float2(max(dxy0.x, dx1), dxy0.y), 0.0);half bottomAlpha = half(saturate(uinnerRect_S1.B - sk_FragCoord.y));half alpha = bottomAlpha * half(saturate(uradiusPlusHalf_S1.x - length(dxy)));return _input * alpha;}

void main() {// Stage 0, QuadPerEdgeAAGeometryProcessor
half4 outputColor_S0 = half4(1);float2 texCoord;texCoord = vlocalCoord_S0;outputColor_S0 = (blend_modulate(sample(uTextureSampler_0_S0, texCoord), half4(1)));const half4 outputCoverage_S0 = half4(1);half4 output_S1;output_S1 = CircularRRect_S1(outputCoverage_S0);{ // Xfer Processor: Porter Duff
sk_FragColor = outputColor_S0 * output_S1;}}
// Vertex GLSL
#version 300 es

#extension GL_NV_shader_noperspective_interpolation : require
precision mediump float;
precision mediump sampler2D;
uniform highp vec4 sk_RTAdjust;
in highp vec2 position;
in highp vec2 localCoord;
noperspective out highp vec2 vlocalCoord_S0;
void main() {
    vlocalCoord_S0 = localCoord;
    gl_Position = vec4(position, 0.0, 1.0);
    gl_Position = vec4(gl_Position.xy * sk_RTAdjust.xz + gl_Position.ww * sk_RTAdjust.yw, 0.0, gl_Position.w);
}

// Fragment GLSL
#version 300 es

#extension GL_NV_shader_noperspective_interpolation : require
uniform highp vec2 u_skRTFlip;
precision mediump float;
precision mediump sampler2D;
out mediump vec4 sk_FragColor;
uniform highp vec4 uinnerRect_S1;
uniform mediump vec2 uradiusPlusHalf_S1;
uniform sampler2D uTextureSampler_0_S0;
noperspective in highp vec2 vlocalCoord_S0;
void main() {
highp     vec4 sk_FragCoord = vec4(gl_FragCoord.x, u_skRTFlip.x + u_skRTFlip.y * gl_FragCoord.y, gl_FragCoord.z, gl_FragCoord.w);
    mediump vec4 outputColor_S0 = vec4(1.0);
    highp vec2 texCoord;
    texCoord = vlocalCoord_S0;
    outputColor_S0 = texture(uTextureSampler_0_S0, texCoord, -0.5);
    mediump vec4 output_S1;
    highp vec2 _0_dxy0 = uinnerRect_S1.xy - sk_FragCoord.xy;
    highp float _1_dx1 = sk_FragCoord.x - uinnerRect_S1.z;
    highp vec2 _2_dxy = max(vec2(max(_0_dxy0.x, _1_dx1), _0_dxy0.y), 0.0);
    mediump float _3_bottomAlpha = clamp(uinnerRect_S1.w - sk_FragCoord.y, 0.0, 1.0);
    mediump float _4_alpha = _3_bottomAlpha * clamp(uradiusPlusHalf_S1.x - length(_2_dxy), 0.0, 1.0);
    output_S1 = vec4(_4_alpha);
    {
        sk_FragColor = outputColor_S0 * output_S1;
    }
}


Errors:
link failed but did not provide an info log

@caymard
Copy link

caymard commented May 9, 2023

Downgrade to brave-browser-1.50.125-1.x86_64 worked also for me.

@rillian
Copy link

rillian commented May 9, 2023

Can confirm enabling vulkan fixes almost all of the rendering issues, with the notable exception of video in brave talk.

@kGAr6Naaes
Copy link

Manually enabling Vulkan from brave://flags fixes 99% of issues on my setup (Fedora 37, Mesa 23.0.3, GNOME on Wayland). Only issue so far is a black bar on the YouTube UI, otherwise usable.

This worked for me too and I could even enable the "Enable GPU rasterization" flag but, for some reason, when I open a new tab I get "Error code: RESULT_CODE_KILLED_BAD_MESSAGE".

I still can type on the address bar.

Guess for now I can set New Tab to blank page.

@blutch112
Copy link

I confirm @rillian proposal. By deleting the profile in /home/$USER/.config/BraveSoftware/
Brave works with version 1.51.110

@coyoterj
Copy link

coyoterj commented May 9, 2023

2 days ago, I updated Brave to version 113.1.51.110 and it's working for me.

@kGAr6Naaes
Copy link

I confirm @rillian proposal. By deleting the profile in /home/$USER/.config/BraveSoftware/ Brave works with version 1.51.110

It's a drastic solution but it worked (mostly because my profile was very new).

@rillian
Copy link

rillian commented May 17, 2023

2 days ago, I updated Brave to version 113.1.51.110 and it's working for me.

The rendering issues are also fixed for me in 1.52.100 Chromium: 113.0.5672.92 (Official Build) beta (64-bit) on an up-to-date Fedora 38 system, with the exception of video playback. Both talk.brave.com and youtube show blank green areas where the video should be. So it's better, but not completely addressed.

I continue to have no problems with fresh profiles.

@supernes
Copy link

You may not need to delete your entire profile or start from scratch, I think it's enough to just remove the shader caches.

I updated to 1.51.118, disabled Vulkan (which is still causing black bars on video), and deleted two folders: ShaderCache and GrShaderCache inside the profile folder (~/.config/BraveSoftware/Brave-Browser/). Now everything works just fine.

Thanks to @rillian for the hint.

@jaylittle
Copy link

So this problem went away for me on Fedora 38 after awhile, but it now appears to have returned after updating a few minutes ago. Anybody else?

@rillian
Copy link

rillian commented May 23, 2023

So this problem went away for me on Fedora 38 after awhile, but it now appears to have returned after updating a few minutes ago. Anybody else?

It hasn't re-occurred for me. Does the suggestion of rm -rf ~/.config/BraveSoftware/*/*ShaderCache make a difference?

With hardware acceleration enabled and vulkan disabled, everything has been working for me. The issues with video I mentioned above seem to have been caused by the vulkan flag.

@jaylittle
Copy link

jaylittle commented May 23, 2023

It hasn't re-occurred for me. Does the suggestion of rm -rf ~/.config/BraveSoftware/*/*ShaderCache make a difference?

Okay so for me I had to delete another folder.... deleting GrShaderCache and ShaderCache inside of ~/.config/BraveSoftware/BraveBrowser didn't help. I had to do this:

rm -rf ~/.config/BraveSoftware/Brave-Browser/Default/GPUCache

That's the one that resolved my issue. Credit where credit is due though, as I stole this from an Arch Forum Post.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests