Segmentation fault in python snap

[LyzardKing]

Hi!
I noticed an issue with a python snap (in this case ubuntu-make).
On a fresh ubuntu budgie install I tried installing the ubuntu-make snap and run it normally,
but there seems to be an issue, because it fails with a Segmentation fault.
It was running properly in previous revisions on 17.04.
The upstream master for ubuntu-make doesn’t have any issue running properly

I’m running:
snapd version 2.27.6+17.10
ubuntu-budgie 17.10 beta

[LyzardKing]

@mvo, @ogra
I’m one of the maintainers for umake itself and the snap.
I tested older versions but they’re failing as well.
The issue seems to me to be related to any updates in snapd for 17.10,
since on older releases of ubuntu the program works without any problem.
Is there a way to debug this properly and see what’s going on?
Running directly from the git branch I can’t see any issue.
Thanks.

[ogra]

there ist a known issue with running classic snaps on non-xenial systems… it ist being worked on:

Classic snaps failing on Ubuntu 17.10

I’ve been attempting to install some classic snaps on a fully updated 17.10 system today. I got this error with atom: relocation error: /snap/atom/x1/lib/x86_64-linux-gnu/libpthread.so.0: symbol __libc_dl_error_tsd, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Teleconsole fails with the following: terminated by signal SIGSEGV (Address boundary error) Can anyone else confirm this issue with classic snaps?

[LyzardKing]

Thanks.
I did read that thread a few days ago, but I thought the issue was different in this case,
since the snap worked in other non xenial (mainly zesty) systems.
I’ll follow that now, and see if the case in question is related.
Thanks for the reply!

[LyzardKing]

@mvo Can I ask if you ended up looking at the ubuntu-make snap?
I tried changing it like the snapcraft snap, adding python and apt as parts.
That didn’t change much…
The only change that makes it work in 17.10 is to remove the LD_LIBRARY_PATH export.