{"componentChunkName":"component---src-templates-post-template-js","path":"/note-vscode-onlinux-aptissue-en","result":{"data":{"markdownRemark":{"id":"cc6d0a26-0194-55df-ab44-5e15b048c11d","html":"
\n

This page has been machine-translated from the original page.

\n
\n\n

Introduction

\n

I troubleshot the issue where VSCode can no longer be launched with the code command after running apt update in a Linux environment, so I’m recording the cause and the fix.

\n

I had installed VSCode using a deb file downloaded from the official site and the dpkg -i command.

\n\n

Table of Contents

\n\n

Check VSCode information

\n

First, I confirmed that the code package existed.

\n
$sudo dpkg -l | grep code\nii  code                                     1.57.0-1623259737                  amd64        Code editing. Redefined.
\n

Next, check what the code command is calling.

\n
$which code\n/usr/bin/code
\n

Apparently, /usr/bin/code is a symbolic link to /usr/share/code/bin/code.

\n
$file /usr/bin/code\n/usr/bin/code: symbolic link to /usr/share/code/bin/code
\n

When I looked into /usr/share/code/bin/code, it turned out to be an executable shell script, so I checked its contents.

\n
$cat /usr/share/code/bin/code \n#!/usr/bin/env sh\n#\n# Copyright (c) Microsoft Corporation. All rights reserved.\n# Licensed under the MIT License. See License.txt in the project root for license information.\n\n# test that VSCode wasn't installed inside WSL\nif grep -qi Microsoft /proc/version && [ -z \"$DONT_PROMPT_WSL_INSTALL\" ]; then\necho \"To use Visual Studio Code with the Windows Subsystem for Linux, please install Visual Studio Code in Windows and uninstall the Linux version in WSL. You can then use the \\`code\\` command in a WSL terminal just as you would in a normal command prompt.\" 1>&2\nprintf \"Do you want to continue anyway? [y/N] \" 1>&2\nread -r YN\nYN=$(printf '%s' \"$YN\" | tr '[:upper:]' '[:lower:]')\ncase \"$YN\" in\ny | yes )\n;;\n* )\nexit 1\n;;\nesac\necho \"To no longer see this prompt, start Visual Studio Code with the environment variable DONT_PROMPT_WSL_INSTALL defined.\" 1>&2\nfi\n\n# If root, ensure that --user-data-dir or --file-write is specified\nif [ \"$(id -u)\" = \"0\" ]; then\nfor i in \"$@\"\ndo\ncase \"$i\" in\n--user-data-dir | --user-data-dir=* | --file-write )\nCAN_LAUNCH_AS_ROOT=1\n;;\nesac\ndone\nif [ -z $CAN_LAUNCH_AS_ROOT ]; then\necho \"You are trying to start Visual Studio Code as a super user which isn't recommended. If this was intended, please specify an alternate user data directory using the \\`--user-data-dir\\` argument.\" 1>&2\nexit 1\nfi\nfi\n\nif [ ! -L \"$0\" ]; then\n# if path is not a symlink, find relatively\nVSCODE_PATH=\"$(dirname \"$0\")/..\"\nelse\nif command -v readlink >/dev/null; then\n# if readlink exists, follow the symlink and find relatively\nVSCODE_PATH=\"$(dirname \"$(readlink -f \"$0\")\")/..\"\nelse\n# else use the standard install location\nVSCODE_PATH=\"/usr/share/code\"\nfi\nfi\n\nELECTRON=\"$VSCODE_PATH/code\"\nCLI=\"$VSCODE_PATH/resources/app/out/cli.js\"\nELECTRON_RUN_AS_NODE=1 \"$ELECTRON\" \"$CLI\" \"$@\"\nexit $?
\n

By reading this script, I confirmed that the actual VSCode executable is /usr/share/code/code.

\n

If you run the file command on it, you can confirm that it is an ELF file.

\n
$file /usr/share/code/code \n/usr/share/code/code: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=09e8dc044d33f961bfddaa7b20750bdf7d1f3005, not stripped
\n

Upgrade VSCode

\n

Now that the preliminary investigation is done, let’s reproduce the issue.

\n
sudo apt update && sudo apt upgrade code
\n

After this, VSCode on Linux was upgraded, and I could no longer launch VSCode from the terminal with the code command.

\n
$code\nbash: code: command not found
\n

Identify the problematic part

\n

From the investigation above, we can see that starting VSCode with the code command goes through the following steps.

\n\n

Here, I will identify at which step the problem occurs.

\n

Check whether the VSCode binary exists

\n

Let’s work backward from the goal.

\n

Surprisingly, after running apt upgrade code, /usr/share/code/code had disappeared.

\n
$file /usr/share/code/code\n/usr/share/code/code: cannot open `/usr/share/code/code' (No such file or directory)
\n

I tried apt install, but apparently it had not been uninstalled.

\n
$sudo apt install code\nReading package lists... Done\nBuilding dependency tree... Done\nReading state information... Done\ncode is already the newest version (4.11.5).\n0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
\n

Then, after exploring a few directories, I found an executable called /usr/bin/codium.

\n

Apparently, codium is an application in which VSCode has been made fully open source, and except for appearance-related parts such as Microsoft’s logo, it is almost completely identical to VSCode.\n(It seems some extensions I always use do not work, though…)

\n

It seems that the VSCode I had originally installed using a deb file downloaded from Microsoft’s page also had the same contents as codium, with only the outer shell being different.

\n

And in the Description of apt show code, I found the following.

\n
Description: Free/Libre Open Source Software Binaries of VSCode (VSCodium)\nTransitional package. Moved to codium.
\n

Apparently, the code package has moved to codium.

\n

Because of that, when I upgraded code with apt, I could no longer launch the application with the code command.

\n

Solution

\n

I simply created an alias.

\n
alias code=codium
\n

This lets me launch VSCode (codium) with the same feel as before.

\n

Summary

\n

This time, I troubleshot the issue where the code command stops working after an upgrade in an environment where VSCode had been installed using a deb file downloaded from the official site and the dpkg -i command.

","fields":{"slug":"/note-vscode-onlinux-aptissue-en","tagSlugs":["/tag/notes/","/tag/vs-code/","/tag/memo/","/tag/english/"]},"frontmatter":{"date":"2021-07-02","description":"I troubleshot the issue where VSCode can no longer be launched with the `code` command after running `apt update` in a Linux environment, so I’m recording the cause and the fix.","tags":["Notes","VSCode","Memo","English"],"title":"Why the `code` Command Stops Working After `apt upgrade` on Linux and How to Fix It","socialImage":{"publicURL":"/static/dc4d8b7f8795f3c3d3489d9957d155f2/no-image.png"}}}},"pageContext":{"slug":"/note-vscode-onlinux-aptissue-en"}},"staticQueryHashes":["251939775","401334301","825871152"]}