Reporting bugs is one of the things which helps developers improve their software. To get through this as quickly as possible here are some things to consider when experiencing bugs:
So how to actually write a good bug report?
How to identify and report software bugs:
For assistance with any program that is crashing or exhibiting buggy behavior you need to post all errors the program is generating. Accurate textual output containing the exact content of any error message(s) is required to properly diagnose issues. Providing a summation of an error message in your own words (or a picture) is not the correct procedure for reporting bugs. The exact complete error message content must be provided, so that it may be searched online. Better yet, skip the middleman, and research your own errors online prior opening a help request on the forum. This is referred to as performing your due diligence. Meaning you are expected to make a reasonable effort to search for a solution before opening any help request on the forum. We attempt to help users with issues with third party software, however this is not Garuda's responsibility. Any software experiencing bugs that can not be resolved should be reported to its upstream project.
A program that will not start, or is experiencing bugs should be launched in the terminal to display a textual output of any errors produced by the program. You can find the correct command to start the program in the terminal by right clicking on the programs icon in the application start menu. If for example you were trying to start the program "Pamac" for installing and uninstalling software you would do as follows. Right click on the icon named "Add/Remove software" in the applications menu (KDE). Depending upon your DE there should be a menu popup with a choice similar to "Edit application" or "Properties". Left click on this option and then select the "Application" tab (or similar). In the "Application" tab there will be a section with a listing for the "Command:" to start the program. You should find “Command: pamac-manager %U “ listed there. Copy and paste "pamac-manager %U” into the terminal (without quotes) and press enter. Copy and paste any resultant errors from starting the program via the terminal into a properly formatted code block in your "Opening Post" (OP) on the forum.
Help requests that have zero possibility of ever being solved because of a total lack of information are simply considered cruft and clutter on the forum. Any help request with woefully inadequate information may be moved from the main forum until sufficient information is provided. Your help request's OP can be edited to provide the required information in the following manner. Click on the three dots (...) at the bottom margin of your opening post. A new section will expand that contains a pencil icon. Clicking on the pencil icon will allow you to edit your post to add the information your post is lacking. Generally most technical help requests require at least your system specifications and any relevant errors and background information related to your issue. Be sure to properly format all errors and other code in easily human readable code blocks as already explained above. Once your OP has been edited to include the required information it will be returned to the main forum (if it has been moved).