Note that I cannot load the Brave internal page, about.
$ rpm -qi brave-browser
Name : brave-browser
Version : 1.51.110
Release : 1
Architecture: x86_64
Install Date: Thu 04 May 2023 06:33:09 AM EDT
Group : Applications/Internet
Size : 337183452
License : Multiple, see https://brave.com/
Signature : RSA/SHA512, Wed 03 May 2023 04:47:04 PM EDT, Key ID a8580bdc82d3dc6c
Source RPM : brave-browser-1.51.110-1.src.rpm
Build Date : Wed 03 May 2023 04:22:15 AM EDT
Build Host : lion.king
Relocations : /opt
Packager : Brave Software <[email protected]>
Vendor : Brave Software, Inc.
URL : https://brave.com/
Summary : Brave Web Browser
Description :
The web browser from Brave
Browse faster by blocking ads and trackers that violate your privacy and cost you time and money.
Here’s a snippet of out running Brave from the command-line:
$ brave-browser 2>&1 | grep -A3 Errors
Errors:
link failed but did not provide an info log
[12846:1:0505/140011.195296:ERROR:grcontext_for_gles2_interface.cc(61)] Skia shader compilation error
------------------------
--
Errors:
link failed but did not provide an info log
[12846:1:0505/140011.197925:ERROR:grcontext_for_gles2_interface.cc(61)] Skia shader compilation error
------------------------
--
Errors:
link failed but did not provide an info log
[12723:12723:0505/140011.683880:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented
[12760:12760:0505/140014.328861:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
--
Errors:
link failed but did not provide an info log
[12903:10:0505/140014.376282:ERROR:grcontext_for_gles2_interface.cc(61)] Skia shader compilation error
------------------------
--
Errors:
link failed but did not provide an info log
@tcayi,
Did this issue just start for you (that is, were you using Brave normally before this) or did you just install the browser and are seeing this behavior when trying to run it?
The issue did just start, yes. I had been using Brave for a few days without issue.
Nothing changed on the system related to Brave or desktop environment configuration, but it’s possible that an update to the OS broke something. Here’s what the package manager reveals:
$ sudo dnf history | head -n6
ID | Command line | Date and time | Action(s) | Altered
--------------------------------------------------------------------------------------------------------------------------------------------------------------
688 | -y install usbutils | 2023-05-05 14:31 | Install | 1
687 | -y install android-tools | 2023-05-05 14:13 | Install | 1
686 | | 2023-05-05 09:56 | Upgrade | 32 EE
685 | -y autoremove | 2023-05-04 21:32 | Removed | 1
$ sudo dnf history info 686
Transaction ID : 686
Begin time : Fri 05 May 2023 09:56:27 AM EDT
Begin rpmdb : 8181dc3d8031b9b58cfb569ae9795f855ac9e7f260a7c49a6bb6e6ebbe7605d1
End time : Fri 05 May 2023 09:56:40 AM EDT (13 seconds)
End rpmdb : 11aed87849c9dfa04416f506fa8b77889cd741a6bc9d9bc03e5d1e5e8f922825
User : System <unset>
Return-Code : Success
Releasever : 38
Command Line :
Comment :
Packages Altered:
Upgrade annobin-docs-12.10-1.fc38.noarch @updates
Upgraded annobin-docs-12.02-1.fc38.noarch @@System
Upgrade annobin-plugin-gcc-12.10-1.fc38.x86_64 @updates
Upgraded annobin-plugin-gcc-12.02-1.fc38.x86_64 @@System
Upgrade clang-16.0.2-1.fc38.x86_64 @updates
Upgraded clang-16.0.1-1.fc38.x86_64 @@System
Upgrade clang-devel-16.0.2-1.fc38.x86_64 @updates
Upgraded clang-devel-16.0.1-1.fc38.x86_64 @@System
Upgrade clang-libs-16.0.2-1.fc38.x86_64 @updates
Upgraded clang-libs-16.0.1-1.fc38.x86_64 @@System
Upgrade clang-resource-filesystem-16.0.2-1.fc38.x86_64 @updates
Upgraded clang-resource-filesystem-16.0.1-1.fc38.x86_64 @@System
Upgrade clang-tools-extra-16.0.2-1.fc38.x86_64 @updates
Upgraded clang-tools-extra-16.0.1-1.fc38.x86_64 @@System
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 compiler-rt-16.0.2-1.fc38.x86_64 @updates
Upgraded compiler-rt-16.0.1-1.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-minimal-13.1-4.fc38.x86_64 @updates
Upgraded gdb-minimal-13.1-3.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 libXft-2.3.8-2.fc38.x86_64 @updates
Upgraded libXft-2.3.6-2.fc38.x86_64 @@System
Upgrade libcurl-8.0.1-1.fc38.x86_64 @updates
Upgraded libcurl-7.87.0-8.fc38.x86_64 @@System
Upgrade libcurl-devel-8.0.1-1.fc38.x86_64 @updates
Upgraded libcurl-devel-7.87.0-8.fc38.x86_64 @@System
Upgrade libomp-16.0.2-1.fc38.x86_64 @updates
Upgraded libomp-16.0.1-1.fc38.x86_64 @@System
Upgrade libomp-devel-16.0.2-1.fc38.x86_64 @updates
Upgraded libomp-devel-16.0.1-1.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-16.0.2-1.fc38.x86_64 @updates
Upgraded llvm-16.0.1-1.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 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-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 qgnomeplatform-qt5-0.9.0-14.fc38.x86_64 @updates
Upgraded qgnomeplatform-qt5-0.9.0-13.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
Scriptlet output:
1 warning: file 7c5350fde3da78a5bc0caf011a367d1cceff4a: remove failed: No such file or directory
2 warning: file 39f59c69cb0103008b3f9f3fd237eaf9a63d09: remove failed: No such file or directory
3 warning: file 8d0df2f37dcc9a5a8d20e54ce2d16f950cd4be: remove failed: No such file or directory
4 warning: file 61edcd67222cef4c4e99efd34dd91e5c879fd2: remove failed: No such file or directory
5 warning: file 00bbc73f777b670a8ef40665fcd04ed7c8f707: remove failed: No such file or directory
6 warning: file 6c56b7c1b2695a81cf080ccf5cd58ff7fb09fc: remove failed: No such file or directory
7 warning: file 89aefc076026bd436da128fe82e8dc266648a2: remove failed: No such file or directory
The change to the mesa packages seem worthy of suspicion.