[Bug] chrome-sandbox permissions prevent startup on Fedora 43

Environment

• Fedora 43
• SELinux: default enforcing configuration
• No custom SELinux policies
• No AppArmor modifications
• windows95 version:
• Installation method: <RPM/AppImage/manual/etc.>

Problem

After fixing issue #322, I can start the application, but it now immediately aborts with:

[1071999:0615/045650.040696:FATAL:sandbox/linux/suid/client/setuid_sandbox_host.cc:166]
The SUID sandbox helper binary was found, but is not configured correctly.
Rather than run without sandboxing I'm aborting now.
You need to make sure that
/usr/lib/windows95/chrome-sandbox
is owned by root and has mode 4755.

trace trap (core dumped)

Some Additional Infos

ls -l /usr/lib/windows95/chrome-sandbox
rpm -qf /usr/lib/windows95/chrome-sandbox -rwxr-xr-x 1 root root 15000 Apr 13 19:20 /usr/lib/windows95/chrome-sandbox windows95-5.0.1-1.x86_64

Expected behavior

The application should start normally without requiring manual post-installation permission fixes.

Observations

The bundled chrome-sandbox binary appears to be detected, but Chromium refuses to start because ownership and/or SUID permissions are not set correctly.

Workaround

Required permissions according to the error:

chown root:root /usr/lib/windows95/chrome-sandbox
chmod 4755 /usr/lib/windows95/chrome-sandbox

This happens on a clean Fedora 43 installation with default security settings and no SELinux/AppArmor customization.

Question

Should these permissions be applied during packaging/install time, or is the application expected to run with --no-sandbox on modern Linux distributions?