Have a good night.
I imagine @Mattches will provide some guidance. If you feel like trying something in the mean time, you might try:
turning off hardware acceleration (use brave://settings/system in address bar to get to right section of settings directly) - it sounds silly, I’m sure, but it actually affects things that don’t seem related
reinstall with the standalone installer from the github release channel. Here are direct links to the 32-bit and 64-bit Windows installers:
I’m running Linux 5.2.9, Brave 0.68.131, and Chromium: 76.0.3809.100 (Official Build) unknown (64-bit). I have MetaMask and IPFS Companion installed
Edit: I just did a couple thing to try and remedy the situation, first I restored my wallet, then I tried reinstalling Brave, neither of these things helped at all. It is worth noting that I didn’t have to restore my wallet or reenter my passwords on any site when I reinstalled, so my distro may have just been acting weird and didn’t uninstall it properly. I’ll try again after I post this
Hmm. Your Brave version is 131 while the latest is 132. Even though the Mac and Windows users are reporting the behavior with 132, probably ought to update (if available) and try it again. If using brave://help doesn’t do an auto-update, then you’ll have to use your package manager or whatever Solus uses to update. I’ll look into creating a VM of Solus.
My Linux install of Brave 0.68.132 Chromium: 76.0.3809.132 (Official Build) (64-bit) works as expected with a new wallet and then also with a restoration of my wallet from my Nightly install.
@tiberius, you might try turning off hardware acceleration if it’s on. Also, could you run the commands shown below in my version information in a Terminal window to get additional version information from your install?
Version information:
Brave 0.68.132 Chromium: 76.0.3809.132 (Official Build) (64-bit).
From lsb_release -a: Linux Mint 19.2 Tina
From hostnamectl: above plus kernel 4.15.0-60-generic, Architecture x86-64
From cat /proc/version: kernel 4.15.0-generic (buildd@lgw01-amd64-030) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019
In case I didn’t transcribe that cat result right, here’s an image of it:
To recap, in case you need them, and I’m not positive all will work on your distro, the commands are (anything looking like a 1 is a lower case “L”):
lsb_release -a
hostnamectl
cat /proc/version
sudo Xorg -version
I think the issue everyone here is running to is already known and logged:
I know that this issue references Nightly specificially but the fix isn’t limited to Nightly builds. It seems that the fix has been uplifted to 0.69x releases, meaning that you should see it reflected in the next browser update.