-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ubuntu - "List of sources not found" error when installing release build #2120
Comments
Beta can be installed with these instructions: https://aavo.in/steps-how-to-install-brave-browser-in-ubuntu-18-10-cosmic-cuttlefish/ |
Just tested and works for me, can you please attach the output of the following commands?
|
By appending to the list each time you're not removing the other malformed entries. Once you run this command one time you don't need to do it again. Remove all but the last line of the file |
That '-a' has to be taken out from tee in the docs. |
☝️ This solved the issue on my end |
Have a user still reporting the same error after removing the |
Setting missing milestone to 0.59.x and missing |
Verification passed on
|
Description
I have users reporting that they're unable to install release or beta via terminal instructions. When testing, I was also unable to install and received the following errors:
This was tested on a fresh install of both Ubuntu and Brave browser. Note that the errors are thrown after entering the
sudo apt update
command.@diracdeltas @mbacchi @mihaiplesa
Steps to Reproduce
Actual result:
As screenshot above indicates, errors are thrown after
sudo apt update
is entered in the terminalExpected result:
Brave should install
Reproduces how often:
Every time
Brave version (brave://version info)
Release/Beta/Dev
Reproducible on current release:
Yes
Website problems only:
Additional Information
Here is one user report, will dig for others if they would be useful to have:
https://www.reddit.com/r/brave_browser/comments/9wrtzf/installation_of_brave_release_channel_in_ubuntu/
The text was updated successfully, but these errors were encountered: