Originally reported here, but it does not seem to be a Flatpak specific issue.
It looks like that there is a regression in the new xnec2c version 4.4.17 causing very frequent crashes:
[crit] [crit] [crit] segmentation fault, exiting
segmentation fault, exiting
segmentation fault, exiting
[crit] segmentation fault, exiting
[crit] segmentation fault, exiting
[err] early EOF?, child 0 length 39321 return 0
[err] Failed to read data from forked child
[err] fstep=-1 is out of bounds. calc_data.steps_total=11[err] fstep=-1 is out of bounds. calc_data.steps_total=11[err] fstep=-1 is out of bounds. calc_data.steps_total=11write(): Broken pipe
write(): Broken pipe
read(): No such file or directory
[err] child 4 length 7 return 0
read(): No such file or directory
[err] child 3 length 7 return 0
read(): No such file or directory
[err] child 1 length 7 return 0
I will try to narrow down the problem, but unfortunately my limited free time does not allow me to work on this properly.
However, it is important to fix this since the version 4.4.17 is already in Debian Testing and will be in the upcoming Ubuntu 26.04 LTS.
Originally reported here, but it does not seem to be a Flatpak specific issue.
It looks like that there is a regression in the new xnec2c version 4.4.17 causing very frequent crashes:
I will try to narrow down the problem, but unfortunately my limited free time does not allow me to work on this properly.
However, it is important to fix this since the version 4.4.17 is already in Debian Testing and will be in the upcoming Ubuntu 26.04 LTS.