Attaching Sugar logs to tickets: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
If you provide debugging logs to a ticket, you'll be making it much easier to developers to fix the issue.
Si usted proporciona los registros de depuracion a [http://dev.sugarlabs.org/ Tickets], estara haciendo mucho mas facil para los desarrolladores para solucionar estos problemas.


== Activacion de Depuracion ==
== Enabling debugging ==


These are general steps to follow when providing logs for some bug:
Estos son los pasos generales a seguir para proporcionar los registros de algunos errores.

* Iniciar la [[actividad de Terminal]]

* Escribir lo siguiente.:


* Start the [[Terminal activity]].
* Type the following:
echo 'export SUGAR_LOGGER_LEVEL=debug' >> /home/olpc/.xsession
echo 'export SUGAR_LOGGER_LEVEL=debug' >> /home/olpc/.xsession
: despues presione la tecla Enter.
: then press the Enter key

* Reiniciar, presionando Ctrl+alt+erase.
* Realizar los minimos pasos para producir un error.
* Desde la ventana de terminal, tipear:


* Reboot, or just restart [[X]] by holding down ctrl+alt+erase
* Perform the minimal steps to reproduce the bug.
* From a terminal window, type:
sudo olpc-log
sudo olpc-log


* It places all relevant logs into a file in the current directory. The name of the file includes the serial number of the laptop and the date and time the log was generated. Please send this log when reporting the problem.
* Coloca todos los registros pertinentes en un archivo en el directorio actual. El nombre del archivo incluye el número de serie de la XO, la fecha y hora de inicio del registro generado. Por favor, envíe este registro, cuando se reporte algun problema.
* [[Log]] is an activity for viewing log files
* [[Regitro]] es una actividad donde se puede ver los registros de los archivos.

=== Otros ajustes de Depuracion ===

El archivo <tt>/home/olpc/,xsession-example</tt> contiene otros valores utiles para las depuraciones.Si ustedes an creado un archivo /home/olpc/.xssesion entonces puedes copiar lineas individuales de este. O usted puede copiar todo el archivo a / home / olpc / .xsession, editar el archivo y eliminar la configuración del registro que tu quieres habilitar.

* En la actividad del terminal escribir:


=== Other debugging settings ===
The file <tt>/home/olpc/.xsession-example</tt> contains other settings useful for debugging. If you have created a <tt>/home/olpc/.xsession</tt> then you can copy individual lines from this. Or you can copy the entire file to <tt>/home/olpc/.xsession</tt>, edit the file, and uncomment the log settings you want to enable.
* In a Terminal Activity:
cp /home/olpc/.xsession-example /home/olpc/.xsession
cp /home/olpc/.xsession-example /home/olpc/.xsession
nano /home/olpc/.xsession
nano /home/olpc/.xsession
''remove the "#" symbol from the start of the DEBUG settings you want to enable.
''borrar el simbolo "#" del inicio de la configuración de depuración que desea habilitar.
* Guarda el archivo (presiona ctrl + X)
* save the file (press ctrl+X)
* restart the X Window System as above
* Reinicia el sistema como se hizo antes

=== Presencia / Colaboracion ===


=== Presence / Collaboration ===
Si tus errores envuelven presencias (alguien a quien puedas ver en la vista de Vecindario ) o de Colaboracion (compartir actividades) , por favor siga los siguientes pasos en [[Telepathy debugging]].


If your bug involves presence (who you can see in Neighborhood View) or collaboration (activity sharing), please also follow the steps for [[Telepathy debugging]].
=== Otros registros ===
Varios subsistemas de [[Linux]] crean archivos de registrso en el directorio <tt>/var/log/</tt>.La [[actividad Registro]]
lista algunos de estos errores. Necesitaras entrar como usuario [[root]] para poder ver algunos archivos del registro en la [[Actividad Terminal]].


== Other logs ==
Several [[Linux]] subsystems create log files in the directory <tt>/var/log/</tt>.
The [[Log]] activity lists some of these.
You may need to become the [[root]] user to view some log files in the [[Terminal activity]].


=== Si no puedes reproducir los errores ===
== If you can't reproduce the bug ==


[[Python]]-based activities automatically make logs in <tt>/home/olpc/.sugar/default/logs</tt>. These logs seem to be moved into subfolders on restart and deleted after a certain period of time. If the activity crashed, the Python stack trace will be in its log. This is also a good thing to attach to a bug. As above, you will have to use the [[Terminal activity]] to copy them to removable memory (SD card or USB flash drive) before using the XO or another computer to attach them to the bug.
Las actividades basadas en python automaticamente crean registros en <tt>/home/olpc/.sugar/default/logs</tt>.
Estos registros parecen ser trasladados a las subcarpetas en el reinicio y se borran despues de un cierto periodo de tiempo. Si la actividad se colgo o dejo de funcionar, el seguimiento de esto estara en el registro. Estos tambien seria bueno adjuntarlo a los errores. Como se vio en la parte de arriba , se tendra que usar la [[actividad Terminal]] para copiar en una memoria extraible (sea una tarjeta SD o un USB) antes de usar la XO u otra computadora para adjuntarlos errores.




Latest revision as of 05:26, 4 September 2009

If you provide debugging logs to a ticket, you'll be making it much easier to developers to fix the issue.

Enabling debugging

These are general steps to follow when providing logs for some bug: 

 echo 'export SUGAR_LOGGER_LEVEL=debug' >> /home/olpc/.xsession
then press the Enter key
  • Reboot, or just restart X by holding down ctrl+alt+erase
  • Perform the minimal steps to reproduce the bug.
  • From a terminal window, type:
 sudo olpc-log
  • It places all relevant logs into a file in the current directory. The name of the file includes the serial number of the laptop and the date and time the log was generated. Please send this log when reporting the problem.
  • Log is an activity for viewing log files

Other debugging settings

The file /home/olpc/.xsession-example contains other settings useful for debugging. If you have created a /home/olpc/.xsession then you can copy individual lines from this. Or you can copy the entire file to /home/olpc/.xsession, edit the file, and uncomment the log settings you want to enable.

  • In a Terminal Activity:
 cp /home/olpc/.xsession-example /home/olpc/.xsession
 nano /home/olpc/.xsession
 remove the "#" symbol from the start of the DEBUG settings you want to enable.
  • save the file (press ctrl+X)
  • restart the X Window System as above

Presence / Collaboration

If your bug involves presence (who you can see in Neighborhood View) or collaboration (activity sharing), please also follow the steps for Telepathy debugging.

Other logs

Several Linux subsystems create log files in the directory /var/log/. The Log activity lists some of these. You may need to become the root user to view some log files in the Terminal activity.

If you can't reproduce the bug

Python-based activities automatically make logs in /home/olpc/.sugar/default/logs. These logs seem to be moved into subfolders on restart and deleted after a certain period of time. If the activity crashed, the Python stack trace will be in its log. This is also a good thing to attach to a bug. As above, you will have to use the Terminal activity to copy them to removable memory (SD card or USB flash drive) before using the XO or another computer to attach them to the bug.

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Attaching_Sugar_logs_to_tickets&oldid=216379"