Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't get code-oss to launch raspberry pi 3b #67

Open
Aailea opened this issue Feb 19, 2019 · 22 comments

Comments

Projects
None yet
@Aailea
Copy link

commented Feb 19, 2019

launch from the console:

code-oss --verbose

get this output after some seconds:

[main 2019-02-19T15:28:35.507Z] [storage state.vscdb] open(/home/pi/.config/Code - OSS (headmelted)/User/globalStorage/state.vscdb, retryOnBusy: true)
[main 2019-02-19T15:28:35.524Z] [storage state.vscdb] open(): Unable to open DB due to [object Object]
[main 2019-02-19T15:28:35.527Z] [storage state.vscdb] open(): Unable to use backup due to Error: ENOENT: no such file or directory, unlink '/home/pi/.config/Code - OSS (headmelted)/User/globalStorage/state.vscdb'
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[1140:0219/152836.977430:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-process.

if I try to launch again:

[main 2019-02-19T15:29:30.423Z] Sending env to running instance...
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[1209:0219/152931.765136:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-process.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

& get a window:
"Another instance of code-oss (headmelted) is running but not responding. please close all other instances and try again.

Anything I can do? almost given up...

@Aailea

This comment has been minimized.

Copy link
Author

commented Feb 19, 2019

Sorry. almost forgot

code-oss --version
1.32.0
ce88f65a8818317410b6f0a697ddcec0174f36ca
arm

@TotalBro

This comment has been minimized.

Copy link

commented Feb 19, 2019

Getting this message as well as of yesterday around noon; I'm configuring a Pi for work and was repeatedly reformatting and freshly installing various styles of Raspbian through NOOBS for other reasons when I encountered this issue. Output contains roughly the same errors as yours, and trying to get around the electron issues with --disable-gpu doesn't seem to help as it has on other platforms in the past. Installing the gpg keys manually also doesn't appear to help; it's worth noting that, during the install, I'm getting a gpg: no valid openPGP data found, though I'm not sure if this is normal since I unfortunately didn't think to save logs from the working builds.

@Aailea

This comment has been minimized.

Copy link
Author

commented Feb 19, 2019

Also had tried with --disable-gpu, No result.

Also got the "gpg: no valid OpenPGP data found" message during the various installations I tried, but did not consider it to be a problem... researching I had found someone stating the solution to this was to download the gpgkey in advance with
sudo wget -qO - https://packagecloud.io/headmelted/codebuilds/gpgkey | sudo apt-key add -;

@TotalBro

This comment has been minimized.

Copy link

commented Feb 20, 2019

I've tried installing both ways, but even manually installing the key and verifying that it's there with
apt-key list
but that doesn't seem to actually fix this issue unfortunately.

@TotalBro

This comment has been minimized.

Copy link

commented Feb 20, 2019

This does appear to be an issue with a more recent version. I grabbed an old release (specifically, code-oss_1.29.0-1539683192_armhf.deb, commit 590c416, from 16 October,) and installed it manually with
sudo dpkg -i /home/pi/Download/code-oss_1.29.0-1539683192_armhf.deb
or wherever you happen to put the package.
This worked for me, after about 30 seconds of grey screen while it spun up, it launched with no errors and haven't encountered any problems yet. Hope this works for you while someone smarter than me figures out a better way.

@aliclubb

This comment has been minimized.

Copy link

commented Feb 20, 2019

I HAD the same issue, but upgraded all software on my Pi today, including code-oss, and now get this output when launching from console.

pi@raspberrypi:~ $ code-oss --verbose
[main 2019-02-20T17:04:45.389Z] Starting VS Code
[main 2019-02-20T17:04:45.398Z] from: /usr/share/code-oss/resources/app
[main 2019-02-20T17:04:45.399Z] args: { _: [],
  diff: false,
  add: false,
  goto: false,
  'new-window': false,
  'reuse-window': false,
  wait: false,
  version: false,
  help: false,
  'list-extensions': false,
  'show-versions': false,
  verbose: true,
  status: false,
  'prof-modules': false,
  'prof-startup': false,
  'disable-extensions': false,
  'disable-gpu': false,
  logExtensionHostCommunication: false,
  'skip-getting-started': false,
  'skip-release-notes': false,
  'sticky-quickopen': false,
  'disable-restore-windows': false,
  'disable-telemetry': false,
  'disable-updates': false,
  'disable-crash-reporter': false,
  'skip-add-to-recently-opened': false,
  'unity-launch': false,
  'open-url': false,
  nolazy: false,
  issue: false,
  'file-write': false,
  'file-chmod': false,
  'driver-verbose': false,
  force: false,
  'prof-code-loading': false }
[main 2019-02-20T17:04:45.413Z] Resolving machine identifier...
[main 2019-02-20T17:04:45.415Z] Resolved machine identifier: 787e6c0bb0a8a6447a23cc8dfa943e1c474a72d910fff6eb81a33794479a3c3f
[main 2019-02-20T17:04:45.499Z] update#ctor - updates are disabled as there is no update URL
[main 2019-02-20T17:04:45.525Z] windowsManager#open
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[24684:0220/170445.677589:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-process.
[24648:0220/170446.196921:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
[main 2019-02-20T17:04:46.211Z] [storage state.vscdb] open(/home/pi/.config/Code - OSS (headmelted)/User/globalStorage/state.vscdb, retryOnBusy: true)
[main 2019-02-20T17:04:46.269Z] [storage state.vscdb] open(): Unable to open DB due to [object Object]
[main 2019-02-20T17:04:46.284Z] [storage state.vscdb] open(): Unable to use backup due to Error: ENOENT: no such file or directory, unlink '/home/pi/.config/Code - OSS (headmelted)/User/globalStorage/state.vscdb'
[24701:0220/170446.453302:ERROR:command_buffer_proxy_impl.cc(114)] ContextResult::kFatalFailure: Shared memory handle is not valid
[24684:0220/170446.488034:WARNING:ipc_message_attachment_set.cc(49)] MessageAttachmentSet destroyed with unconsumed attachments: 0/1
[24648:0220/170450.500442:INFO:CONSOLE(1400)] "%cTRACE", source: file:///usr/share/code-oss/resources/app/out/vs/workbench/workbench.main.js (1400)
[24648:0220/170450.527243:INFO:CONSOLE(1400)] "%c  ERR", source: file:///usr/share/code-oss/resources/app/out/vs/workbench/workbench.main.js (1400)
[24648:0220/170450.551844:INFO:CONSOLE(1400)] "%c  ERR", source: file:///usr/share/code-oss/resources/app/out/vs/workbench/workbench.main.js (1400)

I get a window appear, but nothing else happens beyond this. When closing the window, the console shows:

[main 2019-02-20T17:08:17.180Z] Lifecycle#window.on('close') - window ID 1
[main 2019-02-20T17:08:17.182Z] Lifecycle#onBeforeWindowClose.fire() - window ID 1
[main 2019-02-20T17:08:17.194Z] Lifecycle#window.on('closed') - window ID 1
[main 2019-02-20T17:08:17.196Z] Lifecycle#onWillShutdown.fire()
[main 2019-02-20T17:08:17.217Z] Lifecycle#app.on(window-all-closed)
[main 2019-02-20T17:08:17.219Z] Lifecycle#app.on(before-quit)
[main 2019-02-20T17:08:17.220Z] Lifecycle#onBeforeShutdown.fire()
[main 2019-02-20T17:08:17.239Z] Lifecycle#app.on(will-quit)
[main 2019-02-20T17:08:17.244Z] [storage state.vscdb] close()

But I have to Control-C it to actually quit, it never terminates on its own.

pi@raspberrypi:~ $ code-oss --version
1.32.0
aeaef41d51201e555735f5e8d2f38a9d0ddb9026
arm
pi@raspberrypi:~ $ 
@Aailea

This comment has been minimized.

Copy link
Author

commented Feb 21, 2019

TotalBro, thanks :D, I´ll wait to see if this issue is fixed for now. It´s good to know I can go back to a working version if time presses.

I have installed the latest version released yesterday (1.32.0-1550644722) & get the exact same behaviour as reported by aliclubb.

note the last line reported in the console is
[main 2019-02-21T11:02:31.792Z] [storage state.vscdb] close()

(same file reported as missing during launch)

@mvklingeren

This comment has been minimized.

Copy link

commented Feb 21, 2019

Same here; the current release clearly isn't working on RPi.

@HansH2807

This comment has been minimized.

Copy link

commented Feb 21, 2019

Same here! I went back to any 1.29 version and it worked fie, including all extensions. After nightly upgrading to the latest 1.32 version code-oss hung up again as described above. Can anyone tell me how to exclude code-oss from upgrading?

@corbinbs

This comment has been minimized.

Copy link

commented Feb 22, 2019

Hi,

If you've installed 1.29 like:

apt-get install code-oss=1.29.0-1539702286

you can then mark it on hold by running:

apt-mark hold code-oss

then runs of apt-get upgrade won't try to bump it up until you've run

apt-mark unhold code-oss

to allow it to upgrade once again.

Thanks for the work on the code-oss builds for Raspberry Pi.
I've been using it for a while now on a pi in a pi-top laptop. 👍

Brian
🚜 💻

@HansH2807

This comment has been minimized.

Copy link

commented Feb 22, 2019

@aliclubb

This comment has been minimized.

Copy link

commented Feb 22, 2019

As a point of interest, a grep for state.vscdb in the two workspace.main.js files, shows no references to state.vscdb in 1.29, but does in 1.32.

@aliclubb

This comment has been minimized.

Copy link

commented Feb 22, 2019

If you manually place a file called state.vscdb into the correct place, code-oss deletes it upon startup, whilst complaining it can't open the file...

@hitman-codehq

This comment has been minimized.

Copy link

commented Apr 20, 2019

Thanks for the tips everyone - falling back to 1.29 does indeed work! :-)

@ertoorule

This comment has been minimized.

Copy link

commented Apr 30, 2019

it worked!

@ghost

This comment has been minimized.

Copy link

commented May 11, 2019

Same - 1.29 working fine, all versions after are black screened. Looking forward to a fixed version as this is definitely my favourite editor for the pi.

@HansH2807

This comment has been minimized.

Copy link

commented May 14, 2019

FYI: I am running raspian stretch (desktop version) in a VirtualBox 5.26.x VM under Win10 Pro. In this configuration code-oss version 1.32.0 runs as expected (see screenshot)
grafik

@ghost

This comment has been minimized.

Copy link

commented May 14, 2019

Hmmm - hardware specific? I've checked again and upgraded to 1.32.0 and still get the black screen problem on a Raspberry Pi 3b. Downgrading to 1.29 is fine.

2019-05-14-171813_1920x1080_scrot

@Silerra

This comment has been minimized.

Copy link

commented May 18, 2019

I think the arch type from cpu makes the difference. In your VirtualBox runs the virtualized Intel Core. But the Raspbian on Raspberry 3b (or 3b+ in my case) runs with the arch type ARM 32bit (ARMv7). ARMv7 is no longer supported from Microsoft for years. For a few month, the builds for the ARMv7 from the community (here from headmelted) also seem to stop working

In some post, I see that some users have also got under ARM 64 bit (with aarch64) also more recent versions from Code-OSS to run. (I hope my sentence structure is correct.)
The Raspberry PI 3 series have a CPU architecture ARMv8. But the unmodified version of Raspbian runs with ARMv7 (you can see it with command 'uname -m' or 'file $(which ls)'). We can try to run code-oss on 64 bit OS on Raspberry PI or normal 32 bit Raspbian with 64 bit debian guest OS (via nspawn).
In any case, I'm still exploring for more alternatives.

@yuchdev

This comment has been minimized.

Copy link

commented May 30, 2019

Same issue, after downgrade to 1.29 works fine
apt-get install code-oss=1.29.0-1539702286

@fifn2

This comment has been minimized.

Copy link

commented May 31, 2019

What's the status on fixing this? I really want the newest version of code.

@SuperJMN

This comment has been minimized.

Copy link

commented Jul 12, 2019

Still unresolved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.