The brave-keyring is a mandatory ('hard') dependency as seen by apt-cacheįor starters, I won't use an ubuntu repo on my debian install. Is the issue reproducible on the latest version of Chrome? Noĭebian testing 圆4 and the installation/upgrade is done from the deb file provided from github (because there is no repo for debian).

Does the issue resolve itself when disabling Brave Rewards? No.

Does the issue resolve itself when disabling Brave Shields? No.

Can you reproduce this issue with the nightly channel? No.

Can you reproduce this issue with the dev channel? No.

Can you reproduce this issue with the beta channel? No,.

Can you reproduce this issue with the current release? Yes, if you are on a debian based distro.

The requested info from brave://version is not available because the browser can not be installed.

The installation should complete successfully. Įrrors were encountered while processing: Processing triggers for man-db (2.8.5-2). Processing triggers for desktop-file-utils (0.23-4). Processing triggers for mime-support (3.62). ĭpkg: dependency problems prevent configuration of brave-browser:īrave-browser depends on brave-keyring however:ĭpkg: error processing package brave-browser (-install):ĭependency problems - leaving unconfigured 116920 files and directories currently installed.)

Profile Path - /home/redacteduser/.var/app/com.brave.$ sudo dpkg -i Downloads/brave-browser_0.66.99_b.

Command Line - /app/brave/brave -disable-features=WebAssemblyTrapHandler,DesktopPWAsRunOnOsLogin -no-default-browser-check -disable-domain-reliability -enable-dom-distiller -origin-trial-public-key=bYUKPJoPnCxeNvu72j4EmPuK7tr1PAC7SHh8ld9Mw3E=,fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU= -sync-url= -lso-url= -variations-server-url= -variations-insecure-server-url= -disable-features=DesktopPWAsRunOnOsLogin,WebAssemblyTrapHandler -flag-switches-begin -ozone-platform-hint=auto -flag-switches-end -component-updater=url-source= -ozone-platform=wayland.

Instaling brave 1.58.137