Observed in #1351 with SELinux as the likely culprit. Without the message, the user saw a segfault with no apparent reason