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

[tan20290]

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

.

[ghost]

meee too...

[tomstrawn]

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

[DotComCTO]

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]

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]

Thank you for the suggestion, saved me time researching how to block an update. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Silerra <notifications@github.com> Sent: Saturday, March 9, 2019 6:51 AM To: headmelted/codebuilds Cc: tomstrawn; Comment Subject: Re: [headmelted/codebuilds] Failed to launch workspace on raspberry pi 3 b+ raspbian stretch (#68) 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<#67> — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#68 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/At-6_FH7f-IPhCr2jZJW_UElDEdEgmZaks5vU6AzgaJpZM4bHt3I>.

[kevin-chau]

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

[DotComCTO]

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.