How to Install Visual Studio Code on LMDE 5 “Elsie”
If you’ve just installed Linux Mint Debian Edition 5 and want a slick editor that actually works without pulling your hair out, this guide will get VS Code up and running in a few minutes. I’ll walk through the official .deb route, cover the quirks that show up on “Elsie,” and give you a quick fallback if the repo method decides to throw a tantrum.
Why the .deb package is your best bet
LMDE 5 uses Debian 12‑based packages, so the standard VS Code .deb installer fits right in. The alternative Snap or flatpak builds add extra layers that can bite you with slower start‑up times and bigger disk footprints—nothing a seasoned PC tinkerer needs.
Step 1: Grab the latest .deb from Microsoft
Open a terminal and run:
wget -qO- https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > microsoft.gpg
sudo install -o root -g root -m 644 microsoft.gpg /usr/share/keyrings/
What’s happening?
The first command pulls Microsoft’s signing key and converts it to a format the Debian package manager trusts. The second line drops that key into /usr/share/keyrings/ where apt can verify future downloads.
Now add the repository:
echo "deb [arch=amd64 signed-by=/usr/share/keyrings/microsoft.gpg] https://packages.microsoft.com/repos/code stable main" | sudo tee /etc/apt/sources.list.d/vscode.list > /dev/null
Why this matters:
Hard‑coding the repo prevents apt from trying to pull a mismatched package for ARM or an older distribution, which is exactly what tripped me up after the last LMDE point release.
Step 2: Update apt and install
sudo apt update
sudo apt install code
A quick apt update refreshes the package index so it sees the new Microsoft source. The code meta‑package pulls in all required dependencies, including libasound2, which LMDE sometimes leaves out of a minimal install.
Got an error about missing libraries?
Run:
sudo apt --fix-broken install
That tells apt to fetch any stray bits it missed the first time—something I’ve seen when the installer is interrupted by a sudden power flicker.
Step 3: Verify the launch
You should now see “Visual Studio Code” in your menu. Give it a spin:
code --version
If you get something like 1.85.2 back, you’re good to go. If the command complains about missing shared objects (libX11.so.6, etc.), install them manually:
sudo apt install libx11-6 libgtk-3-0
I ran into that exact scenario after a kernel upgrade; LMDE’s rolling updates sometimes leave old library symlinks dangling.
Optional: Keep VS Code up‑to‑date automatically
Because we added the official repo, apt upgrade will pull newer Code releases alongside your system updates. No need to chase down tarballs every month.
If you prefer a more hands‑off approach, enable unattended upgrades:
sudo dpkg-reconfigure --priority=low unattended-upgrades
Now your editor will stay fresh without you having to remember to run apt update manually.
When the .deb method refuses to cooperate
On rare occasions the Microsoft repo may be temporarily down or blocked by a corporate firewall. In that case, grab the latest .deb directly:
- Visit
https://code.visualstudio.com/Download
in your browser. - Choose “Linux – Debian 64‑bit.”
- Save the file, then install with sudo dpkg -i code_*.deb.
- Run sudo apt -f install to fix any missing dependencies.
It’s a bit more manual but works when the automated route stalls.
That’s it—VS Code should now be humming on your LMDE 5 “Elsie” desktop. If you run into a weird dependency loop, remember that the Debian community forums are full of folks who’ve wrestled with the same quirks.
Happy coding, and enjoy the fact that your editor finally respects your keyboard shortcuts!
