This bug is to track the issue previously discussed on the forum at https://forum.snapcraft.io/t/setpriority-bad-system-call/1157 dating back to June 27th 2017.
"I have an application (Game) I'm snapping which gets killed with "Bad system call". In dmesg I see:
[423709.990734] audit: type=1326 audit(1498550621.595:334656): auid=1000 uid=1000 gid=1000 ses=1 pid=21912 comm="nw" exe="/snap/c3game/x1/nw" sig=31 arch=c000003e syscall=141 compat=0 ip=0x7f2da8f55177 code=0x0
"syscall=141".
I did a search onlline and found an irc conversation (https://irclogs.ubuntu.com/2016/06/20/%23snappy.html#t10:19) about the setpriority call from about a year ago. I spoke to @zyga at the sprint who suggested I mention this to @tyhicks as work has been done to allow us to ignore this syscall and allow the app to proceed rather than kill it (as we currently do). So I'm bringing it up here so the conversation is easier to find than an IRC conversation from the past, and get comment from @tyhickson when we can expect this to work. @zyga suggested this might be is some months away?"
