Hardened systemd service cause polkit fail to start with mozjs-102
Current behaviour, description of the problem
Install polkit-123 built with mozjs-102, then
# systemctl daemon-reload
# systemctl restart polkit
Job for polkit.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status polkit.service" and "journalctl -xeu polkit.service" for details.
Desired behaviour
polkit daemon should start fine.
Reproducer
See current behavior.
Detailed description
Bisect pinpoints to 25eef55d as the first bad commit. I'll try to figure out which specific hardening option caused this.