Refs https://github.com/microsoft/vscode/issues/212494
When using the default ANGLE gl/gles backend, v1.90 attempts
to get display refresh rate for vsync from an internal implementation
instead of using the gl extension EGL_CHROMIUM_sync_control,
this eventually ends up loading display info from XRandr and chromium
attempts to set a label for the data from the shipped resource pak
file that is not accessible to the gpu process triggering a SIGTRAP
in ui::ResourceBundle::GetSharedInstance.
When lauching with `env POSIXLY_CORRECT=y code [...]`, VSCode creates two directories named `-m` and `700`. This is because the order of arguments, in a POSIX strict environment, matters.
Exporting XDG_CACHE_HOME affects applications launched from within
the context of code.
Rename it to GDK_CACHE_DIR and do not export it. Also test for
existence before creating to avoid shelling out to mkdir if not
needed.
Signed-off-by: Sergio Schvezov <sergio.schvezov@canonical.com>
* snap: add assets verbatim
Providing the desktop files in snap/gui will have snapcraft copy over
those assets into the snaps meta/gui verbatim.
Addtionally, add a leading ${SNAP} to the Icon entry which was also
moved to snap/gui for the "package" to have an icon by default
(which is important when sideloading).
Signed-off-by: Sergio Schvezov <sergio.schvezov@canonical.com>
* escape
* fix snapcraft.yml
* use @@EXEC@@ in desktop files
* fix bad path
* fix snap desktop file
This allows software store to recognise this snap matches Visual Studio Code in
other formats (.deb, .rpm, Flatpak etc). It also means reviews on ODRS are
grouped together.
Clean up the stage-packages: to drop any unnecessary libraries and ensure all required libraries to maintain ABI compatibility are bundled in the snap.
+Simplifies the build process.
+Avoids creating a new shell that simply spawns another shell environment.
+Simplifies the update mechanism by removing the need to track the existence of snapUpdate.sh.
+Keeps the logic for snapUpdate.sh close to updateService.snap.ts
