| Git Clone URL: | https://aur.archlinux.org/brave-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | brave-bin |
| Description: | Web browser that blocks ads and trackers by default (binary release) |
| Upstream URL: | https://brave.com |
| Keywords: | brave browser |
| Licenses: | BSD, MPL2, custom:chromium |
| Conflicts: | brave |
| Provides: | brave, brave-browser |
| Submitter: | toropisco |
| Maintainer: | brave |
| Last Packager: | brave |
| Votes: | 878 |
| Popularity: | 14.57 |
| First Submitted: | 2016-04-06 13:16 (UTC) |
| Last Updated: | 2025-06-03 18:55 (UTC) |
Has Brave just started crashing for anyone else within the past day or two?
I just updated my system packages, and I'm trying to figure out if one of those is negatively impacting Brave. It doesn't always crash, but eventually it starts crashing every time after startup.
@mr91, I have been receiving updates normally. We should soon receive the update.
Is this package still mantained?
@alerque, I'm experiencing a bug where minimizing and restoring the Brave window decreases in size. This occurs when the window is not maximized. I use KDE + Wayland. Do you experience this problem?
Reproduce the bug:
- Keep the Brave window active without being maximized
- Click the minimize button in the window
- Then I clicked on the Brave icon in the taskbar
@LinuxSquare Probably your download was corrupted and the sha265 avoided installing a corrupted zip :D
Hi @OscarJ It seems like something went wrong with my build-process. When building, it failed because it couldn't validate the source. Which lead me to compare the source myself by downloading and checking it manually. Since they were different I commented. However, when re-cloning the package and building it, it seems to be working. No idea what went wrong on my side. So it's all okay :)
Hi @LinuxSquare. SHA256 checksum for brave-browser-1.65.132-linux-amd64.zip is b5a5486b983a88c479d09fbd3a1723c8a37b71baa8a0a321d23861bd6443b1f7. What do you mean exactly?
Hm, it seems like the sha256sums have changed: When I download the x86_64 version and run a sha256sum, I get: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 Instead of: b5a5486b983a88c479d09fbd3a1723c8a37b71baa8a0a321d23861bd6443b1f7
Did Brave change something? Because when I take a look at the diff, the sha256sum indeed got updated.
This is posted as an aid to reduce frustration ('ll delete this when the fix is in).
There is current a bug in chrome/kde/qt? that gets triggered when using wayland and copying text in brave. https://community.brave.com/t/brave-crashes-while-selecting-or-dragging-page-element-on-fedora-kde/545980
It looks like chromium bug: https://issues.chromium.org/issues/336449364
which is caused by a kde (or qt) bug: https://bugs.kde.org/show_bug.cgi?id=482142
in any case, the chromium devs agree it should not stop responding to mouse clicks and have produced a test fix: https://chromium.googlesource.com/chromium/src/+/876fbd5552c8fb9d4889ba0371e4d7e3bfa9af84^!/
Hopefully the fix will get merged by brave, chromium and/or kde/qt fix the missing events soon. Cause its a real PITA.
Problem with Wayland can be fixed by creating a file ~/.config/brave-flags.conf with content --ozone-platform=wayland -- refer to https://github.com/flathub/com.brave.Browser/issues/576
Pinned Comments
brave commented on 2025-04-25 13:00 (UTC)