Sources list changed without my knowledge

Support & Help Requests
, ,
1

So I have MS Edge installed through the MS Edge repo. I don't use Edge for anything more than compatibility testing,never for browsing.

Over the past week or so there have been two updates to Edge including one this morning.Looking in my sources list at something unrelated I noticed that the MS repo had been changed to the Google repo and I know I didn't do that.I purged the Google repo and re-added the MS repo and all is as it was.

I understand that Edge is built on Chromium/Chrome but I'm very curious as to how and why that change took place.

2 Likes
2

Same issue here, the MS Edge repository file changed to the Google repo.

You may edit the file and change to this line:

deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
3 Likes
3

Hi, @Norm24 & @radax05 & everyone else :slight_smile:

From what I've found, this issue / problem of the "Microsoft Edge" entry in the apt sources list being replaced by Google Chrome's one was/is a recent bug introduced by a recent update to "Microsoft Edge".

The most relevant page about this issue / bug seems to be the "Microsoft Edge Stable RPM - Breaking rpm .repo baseurl, from packages.microsoft.com to dl.google.com" - https://github.com/microsoft/linux-package-repositories/issues/310 - bug / issue in the "Issues" page of the "linux-package-repositories" Microsoft's repository in GitHub:

The most relevant comment so far, in that bug, seems to be the following:

https://github.com/microsoft/linux-package-repositories/issues/310#issuecomment-3930584789

I'm quoting that comment here, for easier reference:

kfarnung [ Kyle Farnung ]
3 days ago [ February 19, 2026 ] · edited by kfarnung
Member
Thanks for reporting the issue! The latest release of the microsoft-edge-stable package incorrectly configured the package source and lead to this issue. We have pulled the release and are in the process of shipping a fixed version. If you already installed 145.0.3800.58, a manual install of the next version will fix the package sources. We expect that version (145.0.3800.69 or higher) to be available soon.

In the meantime, the issue can be mitigated by fixing the package sources using these commands:

DEB:

### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be lost.
deb [arch=amd64] https://packages.microsoft.com/repos/edge stable main
EOF

RPM:

sudo tee /etc/yum.repos.d/microsoft-edge.repo > /dev/null <<'EOF'
[microsoft-edge]
name=microsoft-edge
baseurl=https://packages.microsoft.com/yumrepos/edge/
enabled=1
gpgcheck=1
gpgkey=https://packages.microsoft.com/keys/microsoft.asc
EOF

ETA: There's a daily cronjob that will attempt to fix the package sources and revert the mitigation. Once the new package is installed this should no longer be an issue. Thanks @FingerlessGlov3s!

I hope this helps :slight_smile:

4 Likes
4

Looks like MS fixed the issue with the latest update for MS Edge.

2 Likes