Basic Linux Tips and Tricks, Part 2 - page 5
Finding SolutionsP>If you ask for help, whoever you reach will probably want to know your:
- Software configuration
- Distribution (name and version, e.g., Debian Etch or Debian Stable, Fedora Core 8, etc.)
- Kernel version--get this by typing
- Program version (usually Help: About in the GUI)
- Hardware configuration
- Motherboard type--e.g., Biostar GeForce 6100 AM2
- CPU type and speed--e.g., Athlon 64 4200x2
- Video chipset, video if it's a video problem or audio chipset, or other hardware.
Describe your problem and include the above.
First, use the internal bug reporting site search engine to see if the bug has already been reported. This is to your advantage as well as the developers, if you report a duplicate bug, the e-mail announcing a fix or workaround may happen for the people who reported the original bug and not you.
The bugs.debian.org site is the one for the Debian distro as a whole. Good for bugs critical for the Debian distro as a whole and bugs specific to the Debian repository versions of specific application packages. Other distros have their own bug reporting sites (or for smaller projects with a small number of developers, a mailing list or even the developer's e-mail address.
Part 3 of this series provides real-world examples of the process of solving Linux problems.
- 1Linux Top 3: Fedora 24, Peppermint 7 and Solus 1.2
- 2Linux Top 3: Alpine Linux 3.4, deepin 15.2 and Linux Lite 3.0
- 3Linux 4.7 Set to Boost Live Patching, Security and Power Management
- 4Linux 4.6 Charred Weasel adds USB 3.1 Support
- 5Linux Top 3: OpenIndiana 2016.04, Ubuntu 16.04 and Debian's New Leader