Description of the issue: Brave window invisible
How can this issue be reproduced?
Set Ozone Wayland in brave://flags
Relaunch
Brave does open, but the window is invisible/not drawn properly & moving other windows over Brave causes “visual smearing-artifacts”
Expected result: It still functioning, like before the update
Brave Version( check About Brave
): 1.65 I think. Latest Brave Stable & Beta from Flatpak, and the AUR.
Additional Information:
Arch Linux (up2date)
AMD CPU + GPU
KDE Plasma Wayland
Temporary workaround:
Downgrade to an older Flatpak version of Brave:
flatpak remote-info --log flathub com.brave.Browser
sudo flatpak update --commit=<commit_code> com.brave.Browser
(I picked 83ded5971e74194938a9b4590d88a19593d328113ecbfdc15a8e06bf761b0fbe
as commit_code, which is from 2024-04-03, but newer ones may also work. Just not the latest.)
1 Like
Same for me under Ubuntu 22.04.4 LTS.
I had to downgrade to Version 1.64.122 for the browser to work normally again.
sudo apt install brave-browser=1.64.122
1 Like
I encountered the same issue on the Flatpak version of Brave and found a fix :
opened 04:20PM - 18 Apr 24 UTC
For those who had previously set the chrome/brave OzonePlatform flag to Wayland,… Brave is likely refusing to launch since the last update. Here is how to fix it :
- Go to **~/.var/app/com.brave.Browser/config**
- Create a file named **brave-flags.conf** if it doesn't already exist.
- In brave-flags.conf, add the following line :
`--ozone-platform=wayland`
- Launch Brave, it should now work
- If it still doesn't work make sure Brave's flatpak has the Wayland permission (You can do that using Flatseal)
Hope this helps.
Just replace ~/.var/app/com.brave.Browser/config by ~/.config/ if you are running the non-flatpak version.
1 Like