microsoft source appears to disable itself after installing vscode update even though it's still enabled

i originally thought this was an issue with the vscode deb but it seems to be an issue with mintsources, see microsoft/vscode#264431 (comment)

Steps to Reproduce

install the .deb from https://code.visualstudio.com/insiders/
enable the checkbox to add the microsoft apt repo during installation (i did this with linux mint's installer, not sure what that looks like in the CLI)
open "software sources" and check "additional repositories" and ensure the microsoft repo is enabled (might need to enable it initially, i don't remember):
wait for an update to vscode-insiders, then install it with linux mint's update manager
navigate back to software sources and see that the microsoft repo has disabled itself:

system info

Linux Mint 22.2 Cinnamon
mintsources 2.3.4

Yea this keeps happening to me as well. Not sure why it keeps auto disabling

I can reproduce the issue.
However it seems to be purely cosmetic, the repository works fine.

I'm also experiencing this issue. Mintsources 2.3.4

However it seems to be purely cosmetic, the repository works fine.

i noticed that too, although a recent update seems to have removed the repo entirely?

However it seems to be purely cosmetic, the repository works fine.

i noticed that too, although a recent update seems to have removed the repo entirely?

Is it still in your /etc/apt/sources.list.d directory?

Does it still come up when you do apt update?

i already added it back sorry, if it happens again i will check

Yea looks like everything still updates fine through the update manager even after it gets auto-disabled in sources (without needing to re-enable it or anything)

However it seems to be purely cosmetic, the repository works fine.

i noticed that too, although a recent update seems to have removed the repo entirely?

Is it still in your /etc/apt/sources.list.d directory?

Does it still come up when you do apt update?

ok it happened again, and it's not present in either of those

I have same issue

Any update on this? It keeps happening to me too with Docker and Microsoft repositories.

as a workaround i switched to vscodium instead

I had a look at what is going on with this last week and submitted my findings at pop-os/repolib#92 .

To contextualize the findings from an end-user's perspective, mintsources uses repolib for loading and parsing of the source files (both the legacy .list and the new .sources). There seems to be a bug in the repolib's .sources, also known as Deb822 format, parsing, such that it sees the sources without any Enabled field as disabled. But according to the specification, absence of Enabled field should be interpreted as enabled. This is why when mintsources is opened, the repositories appear as disabled. When a user manually clicks to enable it, mintsources overwrites the source file using repolib when adds Enabled: yes.

### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be lost.
Types: deb
URIs: https://packages.microsoft.com/repos/code
Suites: stable
Components: main
Architectures: amd64
Signed-By: /usr/share/keyrings/microsoft.gpg
X-Repolib-ID: vscode
X-Repolib-Name: vscode
Enabled: yes

But as evident from the comment at the top of the file, the file is managed by the package manager. Updates from the repository will overwrite the changes, which results in removing the Enabled field (as in the original version), and when mintsources is opened, it shows the repository as disabled.

This is a problem in the mintsources source management UI only. The underlying apt package manager parses the sources fine. So, even though mintsources shows the repository as disabled, when mintsources calls apt for updates, it will do the right thing.

As a user, unless there's an explicit Enabled: no in the .sources file, everything should be fine. System updates will also fetch the updates these repositories. Please have a look for the .sources files under /etc/apt/sources.list.d/ to make sure they aren't actually disabled. Once the repolib's interpretation issue is fixed and mint packages receive a new version of repolib, this issue will resolve automatically.

@darkowlzz

Very interesting. Thanks for looking into this @darkowlzz!

I had a look at what is going on with this last week and submitted my findings at pop-os/repolib#92 .

You can send the PR here too if they are unresponsive in the upstream repo, Mint could patch it downstream too.

I'm also having this issue. It's good to see that this is cosmetic, but it's still a bit annoying. Are there any plans to fix this? Does anyone more knowledgeable than me know what'd be involved in doing that?

Should be fixed by linuxmint/repolib@8dd08a3

Navigation Menu

Repository navigation

microsoft source appears to disable itself after installing vscode update even though it's still enabled #264

Steps to Reproduce

system info

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

microsoft source appears to disable itself after installing vscode update even though it's still enabled #264

Description

Steps to Reproduce

system info

Activity

IsaacCodes commented on Oct 5, 2025

spamegg1 commented on Oct 6, 2025

naheller commented on Oct 6, 2025

DetachHead commented on Oct 8, 2025

spamegg1 commented on Oct 8, 2025

DetachHead commented on Oct 8, 2025

IsaacCodes commented on Oct 15, 2025

DetachHead commented on Oct 25, 2025

EvgenyAfanasev commented on Nov 24, 2025

MasterTJ123 commented on Apr 8, 2026

DetachHead commented on Apr 8, 2026

darkowlzz commented on Apr 8, 2026

naheller commented on Apr 9, 2026

anaximeno commented on Jun 1, 2026

Lightning11wins commented on Jun 10, 2026

mtwebster commented on Sep 23, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions