Can you please tell me more about your environment? Which architecture (x86 or arm?) and distribution is this happening on. Can you also look at dmesg and attach the part of the log when the application dies please?
Thanks for your bugreport! If the 32bit application you are using available in the store? If so, could you please tell us the name so that we can try to reproduce it?
Sorry for not including platform information: This is running on Ubuntu 16.04 (x86, 64 bit). The package was built with snapcraft 2.29.
you should not manually tinker with the link but use “snap revert core” so that all meta-data, configs etc are properly rolled back too
Thanks, that answers part of my second question. Is there also a way to specify this as part of the build process (snapcraft)?
The application is pharo, although I don’t think you actually need it. You should be able to run the shell for any application with the broken core and see the problem, e.g.:
snap run --shell pharo
/snap/core/2381/lib/ld-linux.so.2
Note that if a different version of core is current, the error won’t occur.
If you still want to try pharo: to force the 32 bit version to run (it also contains a 64 bit version, which is the default):
Thanks a lot for your report @akgrant! We debugged the issue and found that for snaps that use @unrestricted and multi-arch there is a bug. The fix is in https://github.com/snapcore/snapd/pull/3602 and we plan to merge it tonight.
As for building question I’ll defer to @sergiusens as I don’t know
The regression test for this issue is coming up, we just didn’t commit it with the fix last night because we wanted to release as soon as possible. The test will be added so this kind of bi-arch issue doesn’t strike us again.