Arch Linux User Repository

@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.

Has anyone else had right clicking / ctrl + v into Brave's search bar stop working recently?

UPDATE: Fixed itself after I caused Brave to crash, and restore itself.

Figured out how I broke the copying and pasting. I copied a link from a download box. Closed the box, and tried pasting it. Believe this is an upstream issue.

Just in case someone wants to fill a bug here. I'm testing 1.30.81 (Which is based on Chromium 94, which finally has the CSD fixed for Linux) but sadly this Brave version is still using an outdated UI component. But it's fixed on Nightly.

@jb.1234abcd I would suggest opening an issue on the Brave Github

brave-bin-1:1.29.80-1-x86_64.pkg.tar.zst

5.14.3-arch1-1

On Brave open these errors are logged (journalctl):

Sep 14 15:29:04 r61i chrome[40650]: [40650:40650:0914/152904.151908:WARNING:chrome_content_verifier_delegate.cc(212)] Corruption detected in extension eoceebklhjepohnakemchinmkdpbolgh installed at: /home/jb/.config/BraveSoftware/Brave-Browser/Greaselion/Temp/scoped_dirtVb0bH, from webstore: 0, corruption reason: 1, should be repaired: 1, extension location: kComponent

Sep 14 15:29:04 r61i chrome[40650]: [40650:40650:0914/152904.163976:WARNING:chrome_content_verifier_delegate.cc(212)] Corruption detected in extension bpkoijdaibakhfgahdfknbdcankhidoa installed at: /home/jb/.config/BraveSoftware/Brave-Browser/Greaselion/Temp/scoped_dirglbwx9, from webstore: 0, corruption reason: 1, should be repaired: 1, extension location: kComponent

Sep 14 15:29:04 r61i chrome[40650]: [40650:40650:0914/152904.164252:WARNING:chrome_content_verifier_delegate.cc(212)] Corruption detected in extension ldopphkgfhfchjcgfilekhkifaodmegm installed at: /home/jb/.config/BraveSoftware/Brave-Browser/Greaselion/Temp/scoped_dirWcPPFX, from webstore: 0, corruption reason: 1, should be repaired: 1, extension location: kComponent

Sep 14 15:29:04 r61i chrome[40650]: [40650:40650:0914/152904.182283:WARNING:chrome_content_verifier_delegate.cc(212)] Corruption detected in extension gajhkmnhhoadjcfchafgbekhgigglnkp installed at: /home/jb/.config/BraveSoftware/Brave-Browser/Greaselion/Temp/scoped_dirB3yGbZ, from webstore: 0, corruption reason: 1, should be repaired: 1, extension location: kComponent

Sep 14 15:29:04 r61i chrome[40650]: [40650:40650:0914/152904.182560:WARNING:chrome_content_verifier_delegate.cc(212)] Corruption detected in extension mjkjompjknhcipamakpfliebpggggpga installed at: /home/jb/.config/BraveSoftware/Brave-Browser/Greaselion/Temp/scoped_dirUjC7FV, from webstore: 0, corruption reason: 1, should be repaired: 1, extension location: kComponent

Sep 14 15:29:04 r61i chrome[40650]: [40650:40650:0914/152904.182739:WARNING:chrome_content_verifier_delegate.cc(212)] Corruption detected in extension feipjgjfhmnfhhmbkclfopokbcgnpnnd installed at: /home/jb/.config/BraveSoftware/Brave-Browser/Greaselion/Temp/scoped_dirKf5TAc, from webstore: 0, corruption reason: 1, should be repaired: 1, extension location: kComponent

Is anyone else having issues where Google sheets is rendering transparent font colors? It seems specific to this latest version, but I'm having trouble narrowing down exactly where this is happening in styling.

@alerque, I agree on you on this being more the second case than the first, but I guess following the chromium package should be the way (And thus, add them)?

Also, I see that the Chromium package has org.freedesktop.secrets as dependency which includes gnome-keyring, but being a freedesktop standard I'm not sure why it's not including the KDE variant (Looks to me to be that the optdepends that should be added)

@blennow Thanks for the further explanation. I get what you're talking about now.

Unfortunately I don't think this falls under a very good use for optdepends. It is kind of on the fuzzy boarder, but there is a difference between things that directly add additional functionality and things that just play nice together if they happen to both exist. I think this falls into the latter case.

@alosarjos I can confirm that when using XDG_CURRENT_DESKTOP=KDE brave will use kdialog and XDG_CURRENT_DESKTOP=GNOME will use GTK based dialogs.

This is further confirmed by brave support with the command line flag --password-store that supports kwallet. It will also automatically choose the best fitting package for the current environment.

I still really think these should be dependecies of the plasma-browser-integration package too but the maintainer did not.

I just checked the generated .deb brave provided on GitHub, and it does not have any optional dependencies on gnome-keyring or anything related. Are we sure these Gnome and KDE packages have any effect on Brave?

PD: Probably they are as dependencies of dependencies. But there is a brave-keyring package to installed. Anyway, if you say that installing those packages have some effects, I don't see why not update them.

@alerque If you don't see any issue too I could update them once I get home

@aleque Hi, I realize now what I wrote was very cryptic, sorry about that. I'm suggesting that kdialog and kwallet be added as optional dependencies like chromium has.

I previously opened a bug at plasma-browser-integration but it got closed as not a bug and the maintainer referred to the chromium package. I think this change would help discoverability to get integrated dialogs with KDE (I don't think there are integrations for other DE).

@Iwirada Yes that is what I have done and it works. Thanks for the suggestion.

Also, great job on getting the package updated so fast!