I can’t say what the problem exactly is, but I have a possible workaround.
System Info:
OS => Fedora Linux 38
Kernel => 6.2.11-300.fc38.x86_64
Brave Browser Info (Crashing):
Version: 1.50.121-1
Workaround:
On fedora, we can just downgrade the brave-browser package.
With dnf --showdubplicates list brave-browser
we can look which packages are cached.
My output:
[root@thinkpadx395 ~]# dnf --showduplicates list brave-browser
vscodium-repo-rpm 1.1 kB/s | 866 B 00:00
Installed Packages
brave-browser.x86_64 1.50.121-1 @brave-browser-rpm-release_x86_64
Available Packages
brave-browser.x86_64 1.48.171-1 brave-browser-rpm-release_x86_64
brave-browser.x86_64 1.49.120-1 brave-browser-rpm-release_x86_64
brave-browser.x86_64 1.49.128-1 brave-browser-rpm-release_x86_64
brave-browser.x86_64 1.49.132-1 brave-browser-rpm-release_x86_64
brave-browser.x86_64 1.50.114-1 brave-browser-rpm-release_x86_64
brave-browser.x86_64 1.50.119-1 brave-browser-rpm-release_x86_64
brave-browser.x86_64 1.50.121-1 brave-browser-rpm-release_x86_64
The last entry is green on my side – this means it’s the one which is installed right now.
You can then install a package/upgrade earlier with dnf install brave-browser-1.50.119-1
in my case. The dnf
package manager tries then automatically to downgrade the brave-browser package.
Now brave-browser does work again, and we just need to wait until a fix is here.
For the next system upgrade via dnf
add dnf up --exclude=brave-browser
to your command. So every, package gets updated except brave-browser until we know the new update will work.
I hope I can help with this to bridge the wait time until a newer update is here.
Greets LxWulf