I'm sorry, but it is simply nonsense. Eterm is a compiled application which should run on any system - if properly built. It looks like it is not that case. But stating that the system itself is broken is nonsense. But you know. Probably your build environment is not really consistent (=compatible with the running system).

sigsegv usually means a few shared objects are not compatible with each other and/or with the app.

I did not write the program, nor tell it to say that, I am simply reporting what Eterm said, so don't kill the messenger.
to say it is not the system, in my option is wrong, I have more than one other system that without any issues whatsoever install Eterm and it runs without any issues whatsoever, yet Arch for some strange reason does not follow this rule. Therefore, logic states, they did something particularly odd to their system to cause it to no loger compile and make and run without issue as all of the other Linux/GNU distros I have tired this on do not have this particular issue with Eterm, Only Arch and its knock offs, particularly Manjaro being the one put to question here.

therefore, in order for Eterm source code to actually work in Manjaro, (or any Arch or Arch knock off) what then needs to be done. something, one or the other needs to make a fix in the source code so it can co-exist together and Eterm will run without issue, as it stands it is Arch that is now being brought into Question as to what did they do to there system to cause this issue, and not Eterm, for reasons stated.

furthermore, the one that put it into the "repo" should have already taken the necessary steps to make Eterm compatible with Arch and its knock offs. not me a user. makes me wonder about there Quality Control. That and the persons integrity that submitted it, whereas Slackware, slackbuilds.org ohh yeah they got Quality Control for submissions.