question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

http://dl.google.com/linux/chrome/deb/ automatically added to sources.list

See original GitHub issue

Description

Originally reported on community

When running sudo apt update I started wondering about multiple warnings on target packages being configured multiple times. I thought that I had accidentally added the Brave repository multiple times, but then I discovered /etc/apt/sources.list.d/brave-browser-dev.list with contents:

### THIS FILE IS AUTOMATICALLY CONFIGURED ###                                                                                                    
# You may comment out this entry, but any other modifications may be lost.                                                                       
deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main     

Steps to Reproduce

  1. Install Brave from terminal by adding sources
  2. Enter cat /etc/apt/sources.list/brave-browser.list in terminal
  3. Shows Google link automatically added to sources.list file

Actual result:

image

Expected result:

Should not add it

Reproduces how often:

100%

Brave version (about:brave info)

All

Reproducible on current release:

Yes for all brave release/beta/dev

Website problems only:

  • Does the issue resolve itself when disabling Brave Shields?
  • Is the issue reproducible on the latest version of Chrome?

Additional Information

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:4
  • Comments:20 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
fmariercommented, Dec 18, 2018

What is happening is that the .deb / .rpm packaging that comes with Chromium includes a cron job that runs once a day and adds the chromium repository (or re-adds it if it has been disabled). This happens at most 24 hours after installing the package and so it’s not immediately obvious after installation.

If you want to get rid of it, you need to remove the repository, but also the cronjob in /etc/cron.daily/ to prevent it from re-adding the repository. My pull request removes that cronjob so that the Chromium repo never gets added.

1reaction
Mikaelacommented, Oct 13, 2018

This issue also affects /etc/apt/sources.list.d/brave-browser-beta.list.

Read more comments on GitHub >

github_iconTop Results From Across the Web

0 - Ask Ubuntu
I am using ubuntu 18.04 LTS with Oracle VM virtual box in my Windows 10 system. After executing this command sudo apt-get update....
Read more >
r/chrome - Reddit
I have tried adding the sudo sed -i -e 's/deb http/deb [arch=amd64] http/' "/etc/apt/sources.list.d/google-chrome.list" sudo sed -i -e 's/deb ...
Read more >
Dockerfile - Case 1 works, case 2 fails - Stack Overflow
I believe the public keys for the mentioned repository changed recently, or something like that. Quick fix:.
Read more >
Google Linux Software Repositories
Google's Linux software packages will automatically configure the repository settings necessary to keep your Google Linux applications up-to-date.
Read more >
Rails professionals since 2007 - makandra cards
Linux: How To Fix Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release : chrome. Avatar. Henning Koch.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found