That is in the OM Issue Tracker. You will need a GitHub account to login, but this is free.
Reports should include:
What you are testing on: What version of OMLx, please include the Build ID number of the iso you used. Is this the iso ‘Live’ or an installed system, is this on hardware or in VirtualBox or other VM?
Detailed description. This does not have to be long but there needs to be enough for someone to work with. This is a work project.
Any and all relevant logs and screen-shots. It would be wise to include the entire journal log with any report or post.
If you do not know how to do any of this please ask here and we will walk you through this.
Any terminal output longer than about 20-30 lines can be put in a .txt file and attached to your report.
Developers can not fix “it’s broke” they need a cause or otherwise something to work on. That is what the screen-shots and especially the logs are for.