wjhunter3

The attached patch will resolve the problem. [fapolicyd-1.3.1-issue-254.patch.txt](https://github.com/linux-application-whitelisting/fapolicyd/files/12175474/fapolicyd-1.3.1-issue-254.patch.txt)

The attached patch will resolve the problem. [fapolicyd-1.3.1-issue-253.patch.txt](https://github.com/linux-application-whitelisting/fapolicyd/files/12175435/fapolicyd-1.3.1-issue-253.patch.txt)

If it makes a difference I'm running fapolicyd 1.3.1 on RHEL 8, but I haven't seen any changes between 1.3.1 and 1.3.2 that would resolve the problems I'm seeing. The...

Output from the terminals I used to recreate: [issue-253-term1.txt](https://github.com/linux-application-whitelisting/fapolicyd/files/12184194/issue-253-term1.txt) [issue-253-term2.txt](https://github.com/linux-application-whitelisting/fapolicyd/files/12184195/issue-253-term2.txt)

Also . . . the problem only manifests when there are no mount points to watch when fapolicyd starts.

Our application is in a closed system, so having a "mirror" system to modify the trust DB and copy to the target system is not possible/practical. The "loophole" would be...

> "--add-opens=javafx.graphics/javafx.scene.skin=ALL-UNNAMED", > "--add-opens=javafx.graphics/javafx.scene=ALL-UNNAMED", This didn't resolve the problem.

I believe the CssStyleHelper messages are a side effect of the problem: ``` Exception in thread "JavaFX Application Thread" java.lang.reflect.InaccessibleObjectException: Unable to make protected javafx.collections.ObservableList javafx.scene.Parent.getChildren() accessible: module javafx.graphics does...