Microsoft/vscode

Snap: Register code as an editor in Debian with update-alternatives

Open

#93,046 opened on Mar 19, 2020

View on GitHub
 (4 comments) (0 reactions) (2 assignees)TypeScript (10,221 forks)batch import
feature-requesthelp wantedinstall-updatelinuxsnap

Repository metrics

Stars
 (74,848 stars)
PR merge metrics
 (Avg merge 11h 43m) (1,000 merged PRs in 30d)

Description

Issue Type: Bug

This is a bug report regarding a feature that was implemented here: https://github.com/microsoft/vscode/issues/3541

  1. Install Ubuntu 18.04 LTS
  2. Open Snap Store aka "Ubuntu Software"
  3. Search for VSCode
  4. Click on VSCode
  5. Click install
  6. Wait for install to complete
  7. Open terminal
  8. run "update-alternatives --config editor"

Expected: VSCode appears as an option. See https://github.com/microsoft/vscode/issues/3541 Actual: VSCode does not appear as an option

VS Code version: Code 1.43.1 (fe22a9645b44368865c0ba92e2fb881ff1afce94, 2020-03-18T07:17:38.324Z) OS version: Linux x64 5.3.0-42-generic snap

Item Value
CPUs Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (8 x 3829)
GPU Status 2d_canvas: unavailable_softwareflash_3d: disabled_softwareflash_stage3d: disabled_softwareflash_stage3d_baseline: disabled_softwaregpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: disabled_offrasterization: disabled_softwareskia_renderer: disabled_off_okvideo_decode: disabled_softwareviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: unavailable_softwarewebgl2: unavailable_software
Load (avg) 1, 0, 0
Memory (System) 31.27GB (24.04GB free)
Process Argv . --no-sandbox
Screen Reader no
VM 0%

Contributor guide

Research direction
Inspect the Snap packaging configuration (snapcraft.yaml) to check if update alternatives registration is implemented, and compare with the previous implementation in issue #3541 for non snap installations.
Tech stack
typescript
Domain
desktop
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitLinuxSnap
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30