Add ubuntu 18.04 binary distros to automated release builds #610
Comments
|
This is exactly why we have to have automated builds for smapp asap on a predictable system. |
|
@IlyaVi - maybe as short term solution do a smapp build on 18 like the previous one you did? |
|
@lrettig - can you please check on a fully patched u18.04 system. Meaning, with all core ubuntu updates installed? Does it resolve the problem if you are updating to the supported components? We will do another build on u18.04 but it will be interesting to know if this fixes this issue. |
|
The latest build is launching on ubuntu 18.04, but now I see the spacemesh icon spin forever and I'm getting a different error (see below). I installed it on top of the previous one. @avive this system is fully patched (unless you mean something other than installing all the latest package updates using I didn't mention above, but for future reference when I installed and tried to open the app from the UI, nothing happened, and the process hung. When I ran the command manually, I got the error above. I now see this error repeated forever in the app log: |
|
Perhaps we should package as a snap and/or flatpak to avoid this kind of
problem?
At the very least, the deb should have dependencies for the versions of
libraries that we need...
Also, if we're doing deb, it might help to build the app in a container
(my docker-xpra branch has a dockerfile that can be modified to do this--I
updated it to ubuntu 20.04 but its very easy to build in a 18.04 container
instead, even if the host is 20.04.)
…On Fri, Oct 23, 2020, 19:07 Lane Rettig ***@***.***> wrote:
The latest build is launching on ubuntu 18.04, but now I see the spacemesh
icon spin forever and I'm getting a different error (see below). I
installed it on top of the previous one. @avive <https://github.com/avive>
this system is fully patched (unless you mean something other than
installing all the latest package updates using apt). I think the issue
is lower level: ubuntu 18 supports glibc 2.27 (as you can see above),
whereas the app was previously compiled with glibc 2.29 on a newer version
of ubuntu.
I didn't mention above, but for future reference when I installed and
tried to open the app from the UI, nothing happened, and the process hung.
When I ran the command manually, I got the error above.
I now see this error repeated forever in the app log:
[2020-10-23 16:06:00.397] [error] In netService, in grpc isServiceReady, error is: Error: 14 UNAVAILABLE: failed to connect to all addresses
[2020-10-23 16:06:00.397] [info] In netService, in grpc isServiceReady, received: "true"
[2020-10-23 16:06:00.397] [error] In netService, in grpc isServiceReady, error is: Error: 14 UNAVAILABLE: failed to connect to all addresses
[2020-10-23 16:06:00.397] [info] In netService, in grpc isServiceReady, received: "true"
[2020-10-23 16:06:00.397] [error] In netService, in grpc isServiceReady, error is: Error: 14 UNAVAILABLE: failed to connect to all addresses
[2020-10-23 16:06:00.398] [info] In netService, in grpc isServiceReady, received: "true"
[2020-10-23 16:06:00.398] [error] In netService, in grpc isServiceReady, error is: Error: 14 UNAVAILABLE: failed to connect to all addresses
[2020-10-23 16:06:00.398] [info] In netService, in grpc isServiceReady, received: "true"
[2020-10-23 16:06:00.398] [error] In netService, in grpc isServiceReady, error is: Error: 14 UNAVAILABLE: failed to connect to all addresses
[2020-10-23 16:06:00.398] [info] In netService, in grpc isServiceReady, received: "true"
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#610 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB73IWAUBMMMTUGI33AF5K3SMGS2JANCNFSM4S3TOQ2Q>
.
|
|
Latest ubuntu 18 .deb release is working beautifully, thanks. I'll test the snap release tomorrow as well. |
|
We still need to add U 18 .deb and maybe even snap builds to automated build system. It is still quite popular. |
avive
changed the title
|
I'll add "snap" build option to packager script, @narayanprusty you should add a new step for packing smapp using Ubuntu 18 |
|
Cant run app om Ubuntu 18.04 with this problem/ Have fix? Download deb package from ofiicial site nkt@v914636444:/opt/Spacemesh$ ./spacemesh_app
(node:1668) DeprecationWarning: file property is deprecated and will be removed in v5.
A JavaScript error occurred in the main process
Uncaught Exception:
Error: Failed to load /opt/Spacemesh/resources/app.asar/node_modules/grpc/src/node/extension_binary/electron-v8.4-linux-x64-glibc/grpc_node.node. /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.org.chromium.Chromium.ODnuJT)
at process.func [as dlopen] (electron/js2c/asar.js:140:31)
at Object.Module._extensions..node (internal/modules/cjs/loader.js:1016:18)
at Object.func [as .node] (electron/js2c/asar.js:149:18)
at Module.load (internal/modules/cjs/loader.js:816:32)
at Module._load (internal/modules/cjs/loader.js:728:14)
at Function.Module._load (electron/js2c/asar.js:748:26)
at Module.require (internal/modules/cjs/loader.js:853:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object.<anonymous> (/opt/Spacemesh/resources/app.asar/node_modules/grpc/src/grpc_extension.js:32:13)
at Module._compile (internal/modules/cjs/loader.js:968:30)
|
|
failed in ubuntu20 also |
|
I think you can close this |
Describe the bug
After upgrading from 0.1.1 to 0.1.2, the app won't start. I get the following error:
To Reproduce
Steps to reproduce the behavior:
sudo dpkg -i spacemesh_app_0.1.2_amd64.debDesktop (please complete the following information):
Additional context
I've run every previous release of the app on the same system, always upgrading in the same manner, and it always worked before. Suddenly this one doesn't. I haven't changed anything, other than running
apt upgradeonce in a while. It looks like the code of the app hasn't changed since the last release, so maybe it's something about how it was compiled? CC @avive @IlyaViPossibly helpful:
GLIBC_2.29' not foundon linux electron/electron#18181The text was updated successfully, but these errors were encountered: