Apologies if this question has already been asked, but what's the purpose for the brave-bin.sh file included in this package? It doesn't seem to get installed onto the system. Is this file there just for reference or should it be removed?
Search Criteria
Package Details: brave-bin 1:1.73.91-1
Package Actions
| 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: | alerque (alosarjos) |
| Last Packager: | alosarjos |
| Votes: | 820 |
| Popularity: | 16.85 |
| First Submitted: | 2016-04-06 13:16 (UTC) |
| Last Updated: | 2024-11-20 18:19 (UTC) |
Dependencies (8)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libxss
- nss (nss-hgAUR)
- ttf-font (neuropol-ttfAUR, ttf-win7-fontsAUR, ttf-ms-win8AUR, ttf-ms-win8-arabicAUR, ttf-ms-win8-hebrewAUR, ttf-ms-win8-seaAUR, ttf-ms-win8-indicAUR, ttf-ms-win8-japaneseAUR, ttf-ms-win8-koreanAUR, ttf-ms-win8-zh_cnAUR, ttf-ms-win8-zh_twAUR, ttf-ms-win8-thaiAUR, ttf-ms-win8-otherAUR, ttf-kidsAUR, ttf-liberation-sans-narrowAUR, ttf-cavafy-scriptAUR, ttf-ms-fontsAUR, ttf-dejavu-ibAUR, ttf-zeldaAUR, ttf-oxygenAUR, ttf-oxygen-gfAUR, ttf-share-gfAUR, ttf-gostAUR, otf-inconsolata-dzAUR, ttf-d2codingAUR, ttf-agaveAUR, ttf-caracteresAUR, ttf-cuprumAUR, ttf-autour-oneAUR, ttf-impallari-milongaAUR, ttf-impallari-miltonianAUR, ttf-clarity-cityAUR, ttf-ms-win10AUR, ttf-ms-win10-japaneseAUR, ttf-ms-win10-koreanAUR, ttf-ms-win10-seaAUR, ttf-ms-win10-thaiAUR, ttf-ms-win10-zh_cnAUR, ttf-ms-win10-zh_twAUR, ttf-ms-win10-otherAUR, ttf-win10AUR, ttf-ms-win10-cdnAUR, ttf-bmonoAUR, ttf-pt-astra-factAUR, ttf-weblysleekuiAUR, ttf-pt-astra-sansAUR, ttf-pt-astra-serifAUR, ttf-pt-sansAUR, ttf-pt-serifAUR, ttf-pt-monoAUR, ttf-pt-root_uiAUR, ttf-xo-fontsAUR, noto-fonts-liteAUR, ttf-paratypeAUR, ttf-plemoljp-binAUR, ttf-dejavu-emojilessAUR, noto-fonts-variable-liteAUR, ttf-lucida-fontsAUR, ttf-plemoljpAUR, ttf-juiseeAUR, ttf-ms-win10-autoAUR, ttf-karlaAUR, noto-fonts-latin-greek-cyrillicAUR, apple-fontsAUR, ttf-noto-sans-vfAUR, ttf-noto-serif-vfAUR, ttf-noto-sans-mono-vfAUR, ttf-ms-win11AUR, ttf-ms-win11-japaneseAUR, ttf-ms-win11-koreanAUR, ttf-ms-win11-seaAUR, ttf-ms-win11-thaiAUR, ttf-ms-win11-zh_cnAUR, ttf-ms-win11-zh_twAUR, ttf-ms-win11-otherAUR, ttf-ms-win11-autoAUR, gnu-free-fonts, noto-fonts, ttf-bitstream-vera, ttf-croscore, ttf-dejavu, ttf-droid, ttf-ibm-plex, ttf-input, ttf-input-nerd, ttf-liberation)
- cups (cups-gitAUR, cups-gssapiAUR) (optional) – Printer support
- libgnome-keyring (optional) – Enable GNOME keyring support
- libnotify (libnotify-gitAUR) (optional) – Native notification support
Required by (10)
- brave-extension-bitwarden-git (requires brave) (optional)
- chromium-material-icons-for-github-bin (requires brave) (optional)
- chromium-vencord (requires brave) (optional)
- chromium-vencord-bin (requires brave) (optional)
- chromium-vencord-git (requires brave) (optional)
- ice-ssb-git (requires brave) (optional)
- mermaid-cli-brave (requires brave)
- mermaid-cli-brave (requires brave) (make)
- nfauthenticationkey (requires brave) (optional)
- profile-sync-daemon-brave (requires brave) (optional)
Sources (4)
urbenlegend commented on 2022-03-06 12:46 (UTC)
alosarjos commented on 2022-02-27 10:57 (UTC)
@zerophase @Archanfel80HUN If the issues you are having are not related to packaging I would prefer if you can move the discussion to the Brave Github since it will probably be a Brave issue (Not a packaging issue) and the reporting it to the Brave developers will be more usefull.
Archanfel80HUN commented on 2022-02-25 11:10 (UTC) (edited on 2022-02-25 14:50 (UTC) by Archanfel80HUN)
@zerophase i have 32Gig ram, its not a ram issue, its a brave issue. Workaround, run brave in a terminal or from a terminal window. It will not crash. Really strange.
update: brave nightly, current version 1.38.1 does not have any crash issue.
zerophase commented on 2022-02-24 03:15 (UTC)
@archanfel80HUN Have you found a stable version? I've gone back to 1.33 and the behavior persists. There definitely might be an issue with Brave. But, me having ram instability complicates it with how heavy Chromium is on ram.
Archanfel80HUN commented on 2022-02-23 21:12 (UTC)
@zerophase Same issue here, crashing after start, restart for a second or third time its fine.
alosarjos commented on 2022-02-23 20:32 (UTC)
@zerophase Hmm, all I do for now at least is keep updating the version to help @alerque. If it's crashing it sounds more like a Brave issue rather than a packaging itself. I would try reporting it on their GitHub.
zerophase commented on 2022-02-22 18:23 (UTC)
@alosarjos believe my crashes are from having a stick of ram or two go bad. Going to be a bit before I can test, as my current water cooling setup prevents me from removing all of the ram for testing. I do have crash dumps that might help, if this is not from ram.
zerophase commented on 2022-02-21 02:45 (UTC) (edited on 2022-02-21 02:48 (UTC) by zerophase)
@alosarjos I'm using Cinnamon. Don't believe I have any custom flags, and on X11. I do have a coredump in journalctl. This eventually goes away after restarting the browser a bunch.
alosarjos commented on 2022-02-18 15:13 (UTC)
@zerophase @txhx38 I haven't noticed any issue on my install. Can you provide more info on you config? (Desktop Environment, Custom Flags, X11/Wayland, Ozone...)
txhx38 commented on 2022-02-18 05:19 (UTC)
@zerophase Yes. For me it's not crashing but freezing sometimes since a week.
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.