Tips For Giving Useful Feedback To Developers

* Steps to reproduce the issue

* Evidence of the issue

/tmp/dumps/<username>_stdout.txt

/usr/bin/steam 2>&1> mylogfile.log

* System information.

I'm certainly no expert, but I do enjoy games under Linux and I want there to be more of them.Something we can do to help things flow smoothly is to let them know what works and what doesn't work. (bug reporting)It is probably important to keep a positive attitude when doing this or it might make some of them grumpy and we don't want that :PThese are some things they appreciate knowing:Providing clear step by step instructions on how to reproduce the issue in the least amount of steps is essential.Any logs or screenshots you can provide regarding your issues would be very useful.Steam console logs are usually written here, and it is best to exit steam before reading them:Another way to get logs would be to launch the steam client from the command line. On many systems this can be achieved by opening a terminal and launching the following command:This will redirect console output from the steam binary to your log file. Again, it is best to exit Steam before accessing the log.In Steam you can use the F12 key to take a screenshot. If this isn't sufficient there are many other tools that can do this for you, for example Print Screen in Ubuntu.A handy tool for showing people what you are experiencing as well as how to reproduce the issues is recordMyDesktop. This application is probably available in your distribution. Here is a link to more information about it:Things like CPU, GPU, Linux distribution, kernel, video driver, RAM, resolution, Steam version, desktop environment (Gnome vs KDE), etc are handy.Here is a script that helps grab some of that system information:Anyway, if you have more tips to add to this list please post them here! I'll try editing this post to include them :)