Hi there again,
- Tracking the "Leaking python objects bridged to UNO for reason pyuno runtime is not initialized, (the pyuno.bootstrap needs to be called before using any uno classes)" message I've arrived to this issue:
https://github.com/unoconv/unoconv/issues/87
We've just followed a recommendation there and added the UNO_PATH to /etc/enviroment and seems to work, but as these messages are random cannot be %100 sure of that.
This in fact didn't work, some time after this those messages showed up again, neither with the listener launched with the Apache user.
We've done several tests and didn't find the reason of that error or the pattern that triggers it. The only clue we have is that the error only shows up when unoconv is launched from the scheduled task (\assignfeedback_editpdf\task\convert_submissions); there may be a issue in the task itself or a collision between the scheduled task and the synchronous job triggered when a user navigates to the assign submission?