It's a snap problem, not actually a VS Code issue. Just another reason why snap is bad.
this post was submitted on 04 Feb 2026
147 points (97.4% liked)
Technology
80267 readers
3463 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
I like that the article excerpt clearly says that it’s simply about files not being removed when the trash bin is emptied, and it’s a problem specific to the Canonical snap system.. Yet every single other comment in here rants about Microsoft spyware. Not many people read beyond the headline, lol.
So you're saying it's Canonical spyware?
No, he's saying that canonical's snap sucks
Friendly reminder that VSCodium exists, and nobody should be using Microslop's spyware version anyway.
Team Jetbrains!
Friendly reminder, that Emacs exists.
Hostile reminder that vi exists.
And vim/nvim.
Helix crew, where we at
#nano4life
JED checking in from out wherever Voyager is at the moment (sorry about the lag)
Been using zed lately. Pretty similar ui, wildly different performance.
I've been using sed recently to edit my lines. Quite cumbersome but it gets the work done.
VSCodium would have the same Electron caching issues though, wouldn’t it?
That'd be relevant if it were the issue and not specifically snap related.
The only ~~difference~~ downside really is the occasional extension that needs a manual install.
I've been trying out VSIX Manager for my extensions so that I can keep track of which ones I want to install on each machine. This can make it easier to install the weird extensions that you can't install otherwise
Not the only downside - some MS developed extensions, e.g. their Python integration, have to be patched to work with VSCodium: https://github.com/VSCodium/vscodium/discussions/1641
Yeah, they really added DRM.
The only difference really is the occasional extension that needs a manual install.
Well, that and the lack of telemetry and "phoning home" to Redmond. And that's a big one.
Whoops, I meant to say "only downside". Edited it
There are lots of positive differences
Oh nice, I didn’t know, thank you!
I tried open vss I think it's called on arch and I have trouble using it to remotely access configs on my home server via the SSH extension. I got fed up with it and installed the MS version from yay. I resent it but it works.
I think the open version might not have the ms extension store configured. There should be a separate AUR package for that. At least there is for VSCodium. Alternately you can just grab the VSIX for the extensions you want from the MS version and install them on the open one. Personally I don't know what open vss is so I use codium.
I got it working on vscodium, i'll try using that. thanks!
Awesome, great to hear that!
Funny how it's only a problem when using the Snap distribution.
My favorite fun fact about VSCode is it stores all its cache files in $XDG_CONFIG_HOME.
Yay, it uses the XDG dirs... Wait, no, not like that.
Microsoft managing to make even their Linux software not achieve basic functions like...deleting files.
It's a snaps issue. Guessing you didn't read past the headline.
ROCKEY
HORROR
Wha???? A Microsoft product?!?! Nooooo.... c'mon
If you are on Linux, use a real editor like Vim or Emacs and not... THAT
Helix, baby
I have tried it... its not bad
Help, how do I get out?!????!
^/s^
There IS no leaving. If you are IN, you STAY IN.