Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

VSCode hangs when opening files / folders

Open
#594 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
linux, vscode
Domain
desktop

Research direction

Start by reproducing the failure when opening files or folders with commit 1f083ce9ef21fa3d084f6f10cf136748a294f4f79257161f935c4b926ef7dfa5 on Fedora Silverblue 42.20250523.0, with the listed extensions disabled. Compare that behavior with commit e40702713b7a50093f3d0b74a987ad54316dc39a910fb12ae86ef08fde87a9a9; done means establishing whether the hang is caused by the VSCode Flatpak or the Silverblue environment.

Written by the indexing model from the issue text.

Description

Running commit 1f083ce9ef21fa3d084f6f10cf136748a294f4f79257161f935c4b926ef7dfa5 on Fedora Linux 42.20250523.0 (Silverblue), the flatpak was working but suddenly stopped opening folders / files. I had two locally installed extensions, ms-vscode-remote.remote-containers and vscodevim.vim, which even when disabled it fails to open files/folders. I also tried reverting to commit e40702713b7a50093f3d0b74a987ad54316dc39a910fb12ae86ef08fde87a9a9 but observed no change.

This may not be an issue with the flatpak distribution, but it doesn't seem like a silverblue version change should cause such an issue given its containerized.

Dominant language
Shell
Stars
217
Forks
81
Avg merge
4d 12h
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from flathub/com.visualstudio.code

All issues in flathub/com.visualstudio.code

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.