@jordangarrison I saw recently that Arch chromium package got rebuilt with some patch to fix it.
In my case is working without any issue. The patches mention X11, so maybe it's working for me because I'm using Ozone/Wayland. Anyways, seems to be an upstream chromium issue.
Thanks for posting the issue on GitHub, sadly it looks like it hasn't been backported to current Chromium version and I don't think Brave will apply it. So you can either:
- Enable Ozone Wayland
- Install the previous version (If you don't know how I can help you with that)
- Install maybe the nightly or brave (Not -bin) version with the patches applied I would say.
Anyways, the users of this package are awesome and they usually notify me really quick of new updates in case I miss them, so if Chromium fixes it, and Brave releases a new update based on fixed Chromium I will update the package ASAP.
Pinned Comments
alerque commented on 2021-11-27 03:11 (UTC)
@ant0n et all, lets keep the comments here about packaging issues, general Brave usage issues should go in another forum to not clutter up this comment space. I'm deleting comments that have no relation to packaging. Grey areas like crashes that could be blamed on Arch can stay until proven otherwise, but things like how to configure Brave to handle popups or site X or whatever just don't belong here. Thanks for understanding.