How to report a bug on Ubuntu

Ubuntu is increasingly being used. Those who are fed up of fixed and operating systems customized just use it.

Certainly, it is not intuitive to use, but is very light and does not use a lot of memory. Ubuntu is also open source and in continuous development, so its users can report bugs in order to harmonize, as far as possible, the OS to perfection.

1.) We specify first. What is a bug in simple words is a conflict between the Code and other add-ons. To login or report must be in possession of a launchpad account that you can create by clicking here. This can be done in two ways: either from the menu or by using ubuntu-bugs.

2.) We make a signal from the menu in two cases: when an application stops responding and when it does not respond. In the first case, simply click on Help and then click on Report a problem. Proceeding in this way will be automatically sent to all the files and info about the program, and the operation is preferred by developers. If the application does not open or you were using a beta version of the OS, then automatically open a window called ” apport ” to be completed, it will automatically send everything to Launchpad. Although this procedure is to please developers who find themselves in addition to signaling also all the corresponding codes, thus facilitating research and work.

3.) If for various reasons, you were not able to send messages in the former way, then it is possible to do this with ubuntu-bugs. Press Alt + F2 and open the command window. Going to write the terminal ubuntu-bugs program where the program can be put in place two things, we distinguish cases: you must enter the name of the application where problems have been identified, and finally give the go ahead in case the program is not running, otherwise it will insert the process ID (to find the latter the operation to be performed is simple, go to System, Administration, System Monitor and see the ID that corresponds to the application of interest to us).

4.) In any case, the messages must be clear and complete, must be present the steps to get to the bug and what is actually expected, and you can also include files to clarify even better by filling in the part called ” Include an attachment “. Last request made by the developers is not to send as many messages with each little information, but only one as complete as possible. For further information, you can click here, the official guide for the bug report.