Reporting bugs is one of the things which helps developers improving their software. To get through this as quickly as possible here are some things to consider when experiencing bugs:
What kind of bug do you want to report?
Do you have some kind of log or screenshot of the occurrence? Things like “screen goes dark” are hardly resolvable without giving proper information about the circumstances (such as specs, error message, etc.)
Is the problem related to Garuda or is the problem caused by a bug in the software used? If there are issues with a specific version of software that is used in Garuda the only solution will most likely be to report the bug at the software's bug tracker (e.g. Gitlab). If the issue is related to the Garuda specific settings they can be reported to our Forum with proper background information (see below)
Make sure to do at least a quick search concerning the issue prior to posting a bug report or opening a new thread. Sometimes there are already information available on how to solve the issue, saving you and us time.
So how to actually write a good bug report?
Have system logs ready. Longer terminal outputs can be pasted to our PrivateBin and linked to the thread to avoid making the post too long and messy. Screenshots are not as useful as actual text outputs and should be avoided unless it's a graphical bug or something similar.
Include the output of “inxi -Fxxxza” in your post. This gives the people trying to resolve the issue proper information on the hardware used.
If you include terminal outputs in your post please use the proper output format in your post. Using "~" 3 times above and "~" 3 times below the text block will provide a readable, raw look.
Be specific - Try to summarize the problem in minimum words yet effectively.
Do not combine multiple problems even if they seem to be similar. Write different reports for each problem.