Problems with Installation on Ubuntu/Linux

dzen

Hello there!

For Linux, there are three options available on Download - Legend page.

Appimage
.deb
snap

For me, both Appimage and .deb install resulted in the following line in my syslog:

May 19 22:45:08 pop-os kernel: [...] traps: legend[77601] trap int3 ip:[...] sp:[...] error:0 in legend[...]

I would love to give you more detail, but this is literally the only line that gets put into syslog.

—
Snap doesn’t work right away either - but that’s only because it can’t verify certs while installing so one has to put --dangerous with snap install command, like so:

sudo snap install Legend-2.0.8-linux-amd64.snap --dangerous

After which it starts up fine. I feel this should be indicated somewhere, ideally on the download page itself.

dzen

From my limited knowledge, the trap int3 error is probably benign. It is most likely a debug breakpoint set during development, that somehow got into the release package.

universes13

So this has been a continual frustration for me, too. Yes, the snap with the –dangerous flag works and I’m not sure why I didn’t notice this forum post before. The .deb has failed with both the current and the previous Ubuntu.

When starting legend from the command line I get:

Checking for update Error: Error: ENOENT: no such file or directory, open '/opt/Legend/resources/app-update.yml' (node:10700) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/opt/Legend/resources/app-update.yml' (Uselegend –trace-warnings …to show where the warning was created) (node:10700) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag–unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:10700) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. Trace/breakpoint trap (core dumped)
If you need @Jay , I can also provide the crash log.

Hope this helps so that the next version will install properly in Linux.

Jay

Unfortunately I have no Linux experience so I’m not fully sure how to to fix these errors. Electron has options to build for Linux that seemed to work for some of our beta testers using Linux, but I don’t know how to debug it myself. I expect will be releasing a beta app update this month, and that will include updating Electron to the latest version, which may fix these issues by itself? If not, I’ll try installing Linux in a VM and see if I can reproduce the errors.

Or does using --dangerous seem like a reasonable solution? If so, we can just add that to the download page as you suggested.

universes13

Jay Its not a good look to be required to hobble the checking features in whichever package manager is being used…

While I have used Linux for probably two decades now, I am no expert. I do wonder why Electron wasn’t having a app-update.yml file created at installation or had not included a simple check on startup to look for it and create it if not present.

Hopefully an up to date Electron will do the right thing…

Love the app and try to use it all the time. Glad i’ve got it going again in Linux. Makes life easier.