
Lorsqu'une application plante dans Kubuntu, le message d'erreur approprié sera affiché. Il est généralement facile de remplir un rapport de bogue depuis ce message. Avec une application KDE, le rapport de plantage de KDE apparaîtra ainsi qu'une aide pour le signalement du bogue. Sinon, le rapport de plantage Ubuntu apparaîtra ainsi qu'une aide pour le signalement du bogue sur Launchpad.
Lorsqu'une application plante dans un KDE, un rapport de plantage sera présenté qui sera similaire aux images suivantes : la première image montre l'onglet Général qui résume le plantage, la seconde image montre l'onglet Informations pour le développeur qui fournit des informations de traçage de l'erreur qui sont utiles aux développeurs.
Si les informations de traçage sont jugées intéressantes, remplir un rapport de bogue est facile avec l'assistant de rapport de plantage. Si les informations de traçage ne sont pas pertinentes, il n'est alors pas possible de remplir un rapport de bogue avec l'assistant. Le rapport de bogue peut toujours être rempli manuellement sur http://bugs.kde.org/.
Pour accomplir le processus de rapport de bogue, suivez la procédure indiquée ci-dessous.
Procedure 1. Remplir le rapport rapport de bogue après un plantage
button. The following dialog will appear.
thebutton. The following dialog will appear.
theSelect the applicable options. The drop-down box under the question, "Does the application crash again if you repeat the same situation?" has several options.
After selecting the applicable items from the dialog in the previous step, button.
theDepending on the information available in the crash report, either of two dialogs will appear. One is a dialog that indicates that there is not enough information to file a good report. The other is a dialog indicating that the information is useful, and that it would be helpful to continue with filing the report.
If there was not enough information...
It may be necessary to install the proper debug packages in order to get a good trace. Such packages include
kdebase-dbg
,kdebase-workspace-dbg
,kdebase-runtime-dbg
.If enough information was provided to continue filing a bug report using the assistant, a dialog will appear to allow logging in to KDE's Bugzilla.
Use e-mail address as username
Use the e-mail address that was used to register with KDE's Bugzilla.
After logging in with username (e-mail address) and password, button. The assistant will check for duplicates and display the following dialog.
theIf there is a possible duplicate report, button. Either of the following dialogs will be presented.
the report in the list and then theIf the bug appears to be a duplicate, button. This will file the bug report and inform the developers that it may be a duplicate. This is recommended, except in cases with experienced users where it is clearly not a duplicate. the will attach the crash information to the report.
theIf the bug is not a duplicate, simply in the dialog showing the possible duplicates. A dialog will appear with . To prevent checking for more reports and continue to file the report, the button. A dialog will appear to enter additional information concerning the report.
theOnce the details of the bug report are complete, button. The following dialog will be presented.
theIf the information looks correct, button. The following dialog will be presented.
the
Congratulations on a successful bug report! Identifying and reporting bugs are essential to improving Kubuntu and KDE. Some emails may be sent to the registered address to update progress or to allow developers to get additional information about the bug.
When an application that is not KDE crashes in Kubuntu, a pop-up notification will appear from Apport that is similar to the following image.
Crash information may be different
The following screen shots were created by crashing the application VLC deliberately. Crash dialogs associated with other applications will be different. In an actual bug situation, the application name, VLC, will be replaced by the name of the application that actually crashed.
Pour accomplir le processus de rapport de bogue, suivez la procédure indiquée ci-dessous.
Procedure 2. Remplir le rapport rapport de bogue après un plantage
buttons on the System Notification Helper. The following dialog will be presented.
thebutton. The Collecting Problem Information progress dialog will be presented.
theAfter all of the information concerning the crash is collected, a dialog will be presented that displays the details of the report, and the report is sent to the developers. button to view details of the report. The following dialog will be presented.
thebutton to send the report to the developers. In this case, it will send the report to Launchpad. The following progress dialog will be presented.
theAfter the progress dialog completes, the default web browser will open to Launchpad presenting either the login page or the beginning of the online version of the bug reporting process. After logging in (if necessary) the following page will be presented.
When Launchpad is finished processing the bug data, the following page will be presented.
button. The following page will be presented.
theAny extra information can be filled in about the bug report such as what was being done when it crashed or the online file locations that may have caused the crash. The following is a brief description filed with the report in this procedure.
button on the bottom of the page. The following page will be presented.
the
Congratulations on making a successful crash report!Identifying and reporting bugs are essential to improving Kubuntu. Some emails may be sent to the registered address to update progress or to allow developers to get additional information about the bug.