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

Output Tab is blank for all extensions

Open
#281 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
linux, vscode
Domain
devtools

Research direction

Start with the DevTools Console error in workbench.js:1037 and inspect the @vscode/spdlog native module and its libstdc++.so.6 dependency. Reproduce the blank Output Tab after resetting and opening the environment; done means extension output is displayed instead of failing for every extension.

Written by the indexing model from the issue text.

Description

Describe the bug
The "Output Tab" does not display any output for any of the extensions.

To Reproduce
Steps to reproduce the behavior:

  1. Reset the environment.
  2. Open the environment.
  3. Open the Output Tab (Ctrl+Shift+U)
  4. Changing the extensions does not help.

Expected behavior
Extension output should be displayed.

Screenshots
Image

Desktop (please complete the following information):

  • OS: Windows 11 Enterprise
  • Browser: Chrome
  • Version 151.0

Additional context
The DevTools Console has the following error:
workbench.js:1037 [Extension Host] Error: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.31' not found (required by /usr/lib/code-server/lib/vscode/node_modules/@vscode/spdlog/build/Release/spdlog.nod

Dominant language
No language data
Stars
35
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. 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 forcedotcom/code-builder-feedback

All issues in forcedotcom/code-builder-feedback

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.