manjaro.org needs JavaScript to function properly

if is something else then use a search engine to find it and do your own research to make sure you have the correct place, every upstream project has different protocols on how to test and report a bugs so make sure you read them before reporting, and also provide as much information as possible as that will improve the chance of your bug not being closed.

First thing you should do is find out how to reproduce the bug, after that is resolved then you should download a ISO image and reproduce it in a virtual machine, if you cannot reproduce it there then it might be a local isolated issue on your machine or possibly a package that you installed from the AUR.

You can reproduce the bug in a virtual machine! now you have to decide what might be causing the bug.

If the bug can be resolved at packaging level by introducing a patch or any other means to fix it. Head to packages search it and find out if the package belongs to Arch upstream or manjaro, if is a Arch package you can report it at bugs.archlinux.org if is a manjaro package you can report it at gitlab.manjaro.org under the correct package or software name.

Most bugs cannot be fixed at packaging level, in this case you have to find the correct place to report the bug in the correct project bug tracker.

Most common issues are packages that provide custom modifications installed from the official repositories or the AUR, such as themes custom extensions or anything the modifies or extends the vanilla functionality. Those pieces of software also have their own bug trackers.

if is something else then use a search engine to find it and do your own research to make sure you have the correct place, every upstream project has different protocols on how to test and report a bugs so make sure you read them before reporting, and also provide as much information as possible as that will improve the chance of your bug not being closed.

Do not report bugs in the forum, the forum is not a issue tracker, if you do two things will happen the bug will be lost and actually never be reported and fixed, or someone will see it and inform the developers, developers might even see it but they don't have time to open a issue at that moment and it ends up being forgotten.

Issue trackers exist to resolve this kind of problems, a central place to discuss bugs and implementations in a backlog so they can be addressed as quickly as possible, this is the only way a project can evolve in quality control.