Pathio Users

Pathio crashes on startup

When I try to start the latest version I get the following message:

Pathio has crashed
Uncaught Error: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27’ not found (required by /tmp/.org.chromium.Chromium.drPnM4)

Pathio Version: v0.5.3-beta0-linux
Linux Mint 18.1

1 Like

I get this same error, using Mint 18.3
5.2 Alpha worked ok
checking my glibc… ldd (Ubuntu GLIBC 2.23-0ubuntu11) 2.23
it is obvious that the latest pathio is build with a later build environment… that will not run on older versions

Hi folks, please see my response here: GLIB 2.27 not available for Debian. Sorry for the trouble, we should have this fixed soon!

1 Like

I also get this error, again with Linux Mint 18.3. Looking forward to the fix. Thanks!

Got a crash with different error…

installed: X-AppImage-BuildId=83472790-763a-11a9-2087-3df91664d241 image: X-AppImage-BuildId=83472790-763a-11a9-2087-3df91664d241
session_guid: 49c1b97b-e634-4dc0-becf-ceec486c3f19
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
{"level":"error","message":"Fatal crash occurred!","code_origin":"nodeMain_main","version":"v0.5.4-beta","user_role":"unknown","session_guid":"49c1b97b-e634-4dc0-becf-ceec486c3f19","msg_no":7,"timestamp":"2019-05-17T10:50:03.388Z"}

How to fix that?
Pathio 0.5.4 Beta
Ubuntu 19.04 on a laptop with i7 and 13gb free ram

Thanks for letting us know. We think we have a fix for this coming in shortly. I’ll let you know when it’s in the next release so you can test it.

2 Likes

Thanks for letting us know. We think we have a fix for this coming in shortly. I’ll let you know when it’s in the next release so you can test it.

Thank you. I’ll keep trying on windows the next releases.

1 Like

This still seems to be an issue, at least on Archlinux x64 using v0.6.3-alpha

session_guid: 903f85b2-06d1-4ca9-b883-aeed727aa132
terminate called after throwing an instance of ‘std::bad_alloc’
what(): std::bad_alloc
{“level”:“error”,“message”:“Fatal crash occurred!”,“code_origin”:“nodeMain_main”,“version”:“v0.6.3-alpha”,“user_role”:“unknown”,“slice_guid”:null,“session_guid”:"",“msg_no”:7,“timestamp”:“2019-06-28T20:19:49.674Z”}

Still crashing on V0.6.3-beta2 in Archlinux x64 but there is more output now.

session_guid: 477c2dd8-9b9c-490b-bc23-4df1de916d0a
Starting session... (nodeMain_main)
FishSlice starting...
Starting crashReporter (main.js)
Initialising Backtrace (main.js)
Creating Windows
Loading App
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Fatal crash occurred!
Closing Window

Given that this thread was originally started 3 months ago, I am not really getting the impression that this kind of error is high on their priority list. At this point I am starting to doubt it will be fixed. I had high hopes for Pathio, but I think I will stick with SS3D and Slic3r.

Hi @brandon,
You are correct that this crash hasn’t been top-most priority, but we’ve been working on it behind scenes. It’s been more difficult than we initially anticipated because it has involved upgrading lots of our components and we’re being careful about unforeseen repercussions of the changes. Rest assured that we have been working on this (as recently as yesterday afternoon). We really do apologize for the delay, though.

1 Like

So how about the GLIBC_2.27 problem? Still fails on 6.3-beta4 on my debian stretch systems.

Based on what I have been able to track down and confirm, Pathio will only run on Debian based distros based on Buster or higher. So anything from the last year only, which would be, Buster, Ubuntu 18.04 and Mint 19 or higher.

Hi

any chance for download the soruce code and build myself?

greetings