Since version 1:1.51.110-1 brave does not talk to KDE passwordmanager (kwallet). It complains about "cannot connect to password manager") and so it is. This affects brave-dev-bin starting with 1.51, too. Downgrade to 1.50 gives working passwordmanagement again. Any ideas what can be changed?
Search Criteria
Package Details: brave-bin 1:1.66.118-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: | 776 |
| Popularity: | 16.70 |
| First Submitted: | 2016-04-06 13:16 (UTC) |
| Last Updated: | 2024-05-31 16:34 (UTC) |
Dependencies (8)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR, gtk3-classic-xfceAUR)
- 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-noto-fonts-simpleAUR, 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-karlaAUR, 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-autoAUR, 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-plemoljpAUR, ttf-juiseeAUR, ttf-xo-fontsAUR, noto-fonts-liteAUR, ttf-paratypeAUR, 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-plemoljp-binAUR, apple-fontsAUR, ttf-dejavu-emojilessAUR, ttf-ms-win11-autoAUR, noto-fonts-variable-liteAUR, ttf-noto-sans-vfAUR, ttf-noto-serif-vfAUR, ttf-noto-sans-mono-vfAUR, gnu-free-fonts, noto-fonts, ttf-bitstream-vera, ttf-croscore, ttf-dejavu, ttf-droid, ttf-ibm-plex, ttf-input, ttf-liberation, ttf-mona-sans)
- cups (cups-gitAUR, cups-gssapiAUR) (optional) – Printer support
- libgnome-keyring (optional) – Enable GNOME keyring support
- libnotify (libnotify-gitAUR) (optional) – Native notification support
Required by (6)
- brave-extension-bitwarden-git (requires brave)
- 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)
df8oe commented on 2023-05-04 16:47 (UTC)
alosarjos commented on 2023-04-21 05:21 (UTC)
@DHouck It was an issue in Chromium AFAIK
DHouck commented on 2023-04-21 01:41 (UTC)
By “broken upstream”, do you mean the SIGILLs Iʼm getting? I donʼt want to downgrade past a security update, do you know if itʼs upstream using something like -march=native or if the non-bin package is also broken?
alosarjos commented on 2023-04-20 16:20 (UTC)
If you are getting issues for now you can either:
Install the pkg you probably have on your pacman cache
Do a makepkg -si with previous version PKGBUILD file
Not sure if downgrading packages is something on AUR...
EinfxchFinn commented on 2023-04-20 16:17 (UTC)
Can this update be reverted until Brave is usable again?
https://github.com/brave/brave-browser/issues/29894 https://github.com/brave/brave-browser/issues/29893 https://github.com/brave/brave-browser/issues/19801
tocic commented on 2023-04-20 05:24 (UTC)
Just a note to consider this upstream issue before upgrading to 1:1.50.121 (the need to reload pages for GitHub and GitLab).
danisztls commented on 2023-04-19 23:34 (UTC)
With 1.50.121 the profile launcher opened as a blank screen. Downgrading to 1.50.119 solved it.
KrishenK commented on 2023-03-26 17:07 (UTC) (edited on 2023-03-26 17:08 (UTC) by KrishenK)
I have installed brave and when I want to go to the “Sources” tab in the DevTools it shows an error (on the shell, not on the DevTools' console) :
"Uncaught (in promise) TypeError: Invalid resource type name "undefined"", source: devtools://devtools/bundled/panels/sources/sources.js (1)
There is something wrong with my brave, or it is a common issue ?
alosarjos commented on 2023-03-04 07:19 (UTC)
@subuwm I would suggest reporting an issue on their GitHub
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.