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

Failed to launch workspace on raspberry pi 3 b+ raspbian stretch #68

Open
tan20290 opened this issue Feb 21, 2019 · 7 comments

Comments

@tan20290
Copy link

commented Feb 21, 2019

This new update makes it stuck at the beginning of launching. Then it stop working and have no response
15507632902471232384014
.

@Askmewho

This comment has been minimized.

Copy link

commented Feb 25, 2019

meee too...

@tomstrawn

This comment has been minimized.

Copy link

commented Mar 4, 2019

same here, if i go back to earlier version, issue goes away.

@DotComCTO

This comment has been minimized.

Copy link

commented Mar 8, 2019

Same here. I just ran through the installer on a fresh Raspbian build on a 3b+ (armhf). No issues on the installer, but I'm seeing the same blank page as the OP. Hoping this is something that can be resolved.

Much appreciated!

@Silerra

This comment has been minimized.

Copy link

commented Mar 9, 2019

Same issue. The only way for me is downgrade the version:

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

Duplicate of #67

@tomstrawn

This comment has been minimized.

Copy link

commented Mar 9, 2019

@kevin-chau

This comment has been minimized.

Copy link

commented Mar 13, 2019

Should we close this one since it's a duplicate of #67? There seems to be more progress in that issue.

@DotComCTO

This comment has been minimized.

Copy link

commented Mar 13, 2019

Should we close this one since it's a duplicate of #67? There seems to be more progress in that issue.

Feel free to either close or merge the two. The screenshot from the OP was certainly helpful is verifying that I was seeing the same issue.

Unfortunately, the issue doesn't seemed to be resolved, but at least there's a workaround for now. It'd be nice to get a better understanding of the nature of the issue.

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