Program hanging/oscap errors after remediation and subsequent scans with workbench on new profile

[j-ode]

When implementing a new Fedora profile in #10506, I encountered issues when remediating the profile using workbench.
When running workbench without sudo, either from terminal or from GNOME, scap workbench hangs before remediation finishes, and you are given a choice to kill the program or wait, but an even an hour later nothing happens. When running workbench with sudo, the remediation finished, however oscap errors are raised, even when subsequently scanning the system using the profile. Strangely, if you remediate the system using the oscap cli tool and then scan the system using workbench, no oscap errors in workbench appear. See the attached screenshots.

SCAP Security Guide Version:

latest master, OpenSCAP 1.3.7

Operating System Version:

Fedora 37 fresh install VM with 4GB RAM, Fedora 38 fresh install on laptop with 16GB RAM

Steps to Reproduce:

1. Use branch in PR #10506
2. Build the fedora product
3. Try to scan and remediate a fresh fedora system using workbench with the cusp_fedora profile

Actual Results:

When using workbench without sudo, it hangs during remediation. When using with sudo, it produces oscap errors.

Expected Results:

Workbench remediates the system without hanging or errors just as oscap does

[jan-cerny]

The error about "Can't statvfs" is proabably fine, it's related to permissions of the file being read and shouldn't have impact on results. So the real problem here is the hanging and freezing.