Use the checklist and fill out the elements one can answer. Then rename the checklist with your nick or handle in place of my-nickname, and post it as a .txt file in the English/Support forum with a descriptive title. Regarding reporting it is mostly important to report things you find that you believe may be an issue or bug. For serious technical issues or bugs please file a proper bug report here.
If one wishes to post output of coredumpctl or journalctl -b that is easy by outputting the command to a .txt file:
coredumpctl > coredumpctl.txt
and:
journalctl -b > journalctl.txt
Note:
If coredumpctl is empty there is no need to post.
It is a good idea to post the journal.txt file.
In the case of the journal output users need to be aware that there are lines that contain the word “failed” or “error” that are normal output not a problem. Only the more technically knowledgeable know which are real errors and which are not.
There is a more “extended” checklist for those with more time for testing:
Suggestions to improve this process or the this document are welcome. Please make such suggestions in the English/Development Testing forum. Use a descriptive tile for your forum posts.
In the Resources forum we lock threads to prevent pollution, off topic comments, spam, ect.
This is meant constructively and proactively. I have changed my belief about using checklists over time.
Filing bug reports is QA 101. To me you start here. Checklists are great, I use them myself. But bug reports needs to be the first thing emphasized in QA. If you do not have time to file a bug report why do you believe anyone would have time to work on your problem?
What I do is: I use checklists to guide my testing. Then if there are problems I report that. Why? This always has seemed more efficient to me than expecting someone else to read my checklists. If someone steps up and has time to do this I think that would be awesome and I would support that. But to me it seems a more efficient use of time to focus on solving problems. Plus I simply do not have time to add something like that to my “To Do” list.
It is appropriate to report problems first on IRC or in forum. If the problem persists or is not resolved in a few days please file a bug report. Problems reported on IRC or forum can get lost in the flow plus OpenMandriva channel and forum threads often get polluted. It is to hard to follow problems in either for a long period of time. File bug reports. Learn how to do it properly. I am convinced this is a greater help to this project than filing checklists at this time.
Do I ever forget my own advice. Yes. When I see that I have done so I endeavor to correct my mistake ASAP.
I really believe with all the new users we must emphasize filing bug reports. We all got lax on this when OM was a smaller group of people, me included.