BugSquad/Get Logs - Revision history

FGrose at 12:26, 18 September 2014

2014-09-18T12:26:07Z

← Older revision		Revision as of 08:26, 18 September 2014
Line 1:		Line 1:
	<noinclude>~~{{TOCright}}~~		<noinclude>
	[[Category:Testing]]		[[Category:Testing]]
	[[Category:BugSquad]]		[[Category:BugSquad]]
Line 18:		Line 18:

	== Enabling Sugar debug logging ==		== Enabling Sugar debug logging ==
	A shell script file ~/.sugar/debug is run when Sugar starts up. All environment variables exported by the file will be inherited by the Sugar shell and activity processes.		A shell script file, {{Code\|~/.sugar/debug}}, is run when Sugar starts up. All environment variables exported by the file will be inherited by the Sugar shell and activity processes.

	From Sugar 0.83 to 0.98, the file is prepared with commented lines. From Sugar 0.102, the file must be created by you. Use your editor to add a line, or remove the '#' before the line, to ensure SUGAR_LOGGER_LEVEL is exported with the value ''debug'', like this:		From Sugar 0.83 to 0.98, the file is prepared with commented lines. From Sugar 0.102, the file must be created by you. Use your editor to add a line, or remove the '#' before the line, to ensure SUGAR_LOGGER_LEVEL is exported with the value ''debug'', like this:
Line 43:		Line 43:
	=== Where are the logs placed ===		=== Where are the logs placed ===
	* Perform the minimal steps to reproduce the bug.		* Perform the minimal steps to reproduce the bug.
	* The relevant logs are stored in '~/.sugar/default/logs', (e.g, org.laptop.WebActivity-1.log for the log of the first Browse instance).		* The relevant logs are stored in {{Code\|~/.sugar/default/logs}}, (e.g, org.laptop.WebActivity-1.log for the log of the first Browse instance).

	=== Using sugar-launch ===		=== Using sugar-launch ===
Line 66:		Line 66:
	* Reboot, or just restart X using ctrl+alt+erase		* Reboot, or just restart X using ctrl+alt+erase

	The file ~~<tt>~~~/.xsession-example~~</tt>~~ contains other settings useful for debugging. You can copy individual lines from this or copy the entire file to ~~<tt>~~~/.xsession~~</tt>~~.		The file {{Code\|~/.xsession-example}} contains other settings useful for debugging. You can copy individual lines from this or copy the entire file to {{Code\|~/.xsession}}.

	== On other machines (Sugar.84)==		== On other machines (Sugar.84)==

Quozl: /* Enabling Sugar debug logging */

2014-09-18T07:00:24Z

Enabling Sugar debug logging

← Older revision		Revision as of 03:00, 18 September 2014
Line 18:		Line 18:

	== Enabling Sugar debug logging ==		== Enabling Sugar debug logging ==
	~~Starting with the 0.83 development release, we created the text~~ file, ~/.sugar/debug ~~(shown in~~ the ~~gray box below)~~, ~~which gets read at sugar startup~~. ~~All~~ the ~~logging options are commented out~~ by ~~default~~. Use your editor ~~of choice and~~ remove the '#' before the line 'export SUGAR_LOGGER_LEVEL=debug' to ~~enable Sugar debug logging~~.		A shell script file ~/.sugar/debug is run when Sugar starts up. All environment variables exported by the file will be inherited by the Sugar shell and activity processes.

			From Sugar 0.83 to 0.98, the file is prepared with commented lines. From Sugar 0.102, the file must be created by you. Use your editor to add a line, or remove the '#' before the line, to ensure SUGAR_LOGGER_LEVEL is exported with the value ''debug'', like this:

			export SUGAR_LOGGER_LEVEL=debug

			From Sugar 0.83 to 0.98, the prepared file looks like this:
	<pre>		<pre>
	# Uncomment the following lines to turn on many sugar debugging		# Uncomment the following lines to turn on many sugar debugging

Quozl: /* Using the sugar-emulator */

2014-09-18T06:47:19Z

Using the sugar-emulator

← Older revision		Revision as of 02:47, 18 September 2014
Line 38:		Line 38:
	* Perform the minimal steps to reproduce the bug.		* Perform the minimal steps to reproduce the bug.
	* The relevant logs are stored in '~/.sugar/default/logs', (e.g, org.laptop.WebActivity-1.log for the log of the first Browse instance).		* The relevant logs are stored in '~/.sugar/default/logs', (e.g, org.laptop.WebActivity-1.log for the log of the first Browse instance).

			=== Using sugar-launch ===

			To enable debug logging for one run of one specific activity, use sugar-launch in Terminal, to set the SUGAR_LOGGER_LEVEL environment variable and start the activity by bundle id:
			SUGAR_LOGGER_LEVEL=debug sugar-launch org.laptop.Chat

	=== Using the sugar-emulator ===		=== Using the sugar-emulator ===

Sridhar: /* The Log Activity */

2012-04-26T01:08:49Z

The Log Activity

← Older revision		Revision as of 21:08, 25 April 2012
Line 12:		Line 12:

	The [[olpc:Log]] Activity, is a Sugar-based log viewer that is in most distributions to help you view software logs. You can copy text from the view pane into the Sugar clipboard, then from the clipboard keep it into the Journal, and then attach that Journal item into the [http://bugs.sugarlabs.org bugs.sugarlabs.org] or [http://dev.laptop.org dev.laptop.org] [Attach file] > [Browse...] dialogs, or paste relevant pieces directly into the bug description.		The [[olpc:Log]] Activity, is a Sugar-based log viewer that is in most distributions to help you view software logs. You can copy text from the view pane into the Sugar clipboard, then from the clipboard keep it into the Journal, and then attach that Journal item into the [http://bugs.sugarlabs.org bugs.sugarlabs.org] or [http://dev.laptop.org dev.laptop.org] [Attach file] > [Browse...] dialogs, or paste relevant pieces directly into the bug description.

			You can use the Log Collector to easily export all logs to the journal in a handy zip bundle:

			[[Image:Log Collector.png\|615px]]

	== Enabling Sugar debug logging ==		== Enabling Sugar debug logging ==

FGrose at 18:36, 1 April 2010

2010-04-01T18:36:37Z

← Older revision		Revision as of 14:36, 1 April 2010
Line 11:		Line 11:
	== The Log Activity ==		== The Log Activity ==

	The [[olpc:Log]] Activity, ~~[{{fullurle:olpc:File:Activity-log.svg}} http://wiki.laptop.org/images/b/b5/Activity-log.svg][[Image:olpc:File:Activity-log.svg\|link=olpc:Log]]~~ is a Sugar-based log viewer that is in most distributions to help you view software logs. You can copy text from the view pane into the Sugar clipboard, then from the clipboard keep it into the Journal, and then attach that Journal item into the [http://bugs.sugarlabs.org bugs.sugarlabs.org] or [http://dev.laptop.org dev.laptop.org] [Attach file] > [Browse...] dialogs, or paste relevant pieces directly into the bug description.		The [[olpc:Log]] Activity, is a Sugar-based log viewer that is in most distributions to help you view software logs. You can copy text from the view pane into the Sugar clipboard, then from the clipboard keep it into the Journal, and then attach that Journal item into the [http://bugs.sugarlabs.org bugs.sugarlabs.org] or [http://dev.laptop.org dev.laptop.org] [Attach file] > [Browse...] dialogs, or paste relevant pieces directly into the bug description.

	== Enabling Sugar debug logging ==		== Enabling Sugar debug logging ==

FGrose at 18:27, 1 April 2010

2010-04-01T18:27:02Z

← Older revision		Revision as of 14:27, 1 April 2010
Line 1:		Line 1:
	<noinclude>{{ GoogleTrans-en \| es =show \| bg =show \| zh-CN =show \| zh-TW =show \| hr =show \| cs =show \| da =show \| nl =show \| fi =show \| fr =show \| de =show \| el =show \| hi =show \| it =show \| ja =show \| ko =show \| no =show \| pl =show \| pt =show \| ro =show \| ru =show \| sv =show }}</noinclude>		<noinclude>{{TOCright}}
	~~{{TOCright}}~~		[[Category:Testing]]
			[[Category:BugSquad]]
			[[Category:HowTo]]
			</noinclude>


	== What are the logs useful for ==		== What are the logs useful for ==
	If you provide debugging logs to a ticket, you'll be making it much easier to developers to fix the issue. In most of the cases it will be easiest for you to reproduce the bug.		If you provide debugging logs to a ticket, you'll be making it much easier to developers to fix the issue. In most of the cases it will be easiest for you to reproduce the bug.

			== The Log Activity ==

			The [[olpc:Log]] Activity, [{{fullurle:olpc:File:Activity-log.svg}} http://wiki.laptop.org/images/b/b5/Activity-log.svg][[Image:olpc:File:Activity-log.svg\|link=olpc:Log]] is a Sugar-based log viewer that is in most distributions to help you view software logs. You can copy text from the view pane into the Sugar clipboard, then from the clipboard keep it into the Journal, and then attach that Journal item into the [http://bugs.sugarlabs.org bugs.sugarlabs.org] or [http://dev.laptop.org dev.laptop.org] [Attach file] > [Browse...] dialogs, or paste relevant pieces directly into the bug description.

	== Enabling Sugar debug logging ==		== Enabling Sugar debug logging ==
	In the ~~latest~~ 0.83 development ~~releases (that will lead to 0.84)~~ we created the ~~file~~ text file ~/.sugar/debug which gets read at sugar startup.		Starting with the 0.83 development release, we created the text file, ~/.sugar/debug (shown in the gray box below), which gets read at sugar startup. All the logging options are commented out by default. Use your editor of choice and remove the '#' before the line 'export SUGAR_LOGGER_LEVEL=debug' to enable Sugar debug logging.
	All the logging options are commented by default. Use your editor of choice and remove the '#' before the line 'export SUGAR_LOGGER_LEVEL=debug' to enable Sugar debug logging.		<pre>
			# Uncomment the following lines to turn on many sugar debugging
			# log files and features
			#export LM_DEBUG=net
			#export GABBLE_DEBUG=all
			#export GABBLE_LOGFILE=$HOME/.sugar/default/logs/telepathy-gabble.log
			#export SALUT_DEBUG=all
			#export SALUT_LOGFILE=$HOME/.sugar/default/logs/telepathy-salut.log
			#export GIBBER_DEBUG=all
			#export PRESENCESERVICE_DEBUG=1
			#export SUGAR_LOGGER_LEVEL=debug

			# Uncomment the following line to enable core dumps
			#ulimit -c unlimited
			</pre>

	=== Where are the logs placed ===		=== Where are the logs placed ===
	* Perform the minimal steps to reproduce the bug.		* Perform the minimal steps to reproduce the bug.
	* The relevant logs are in '~/.sugar/default/logs', (e.g org.laptop.WebActivity-1.log for the log of the first Browse instance).		* The relevant logs are stored in '~/.sugar/default/logs', (e.g, org.laptop.WebActivity-1.log for the log of the first Browse instance).

	=== Using the sugar-emulator ===		=== Using the sugar-emulator ===
	If you are using a version older than the ~~latest~~ development release (0.83) run the emulator with the following command:		If you are using a version older than the development release 0.83, run the emulator with the following command:
	SUGAR_LOGGER_LEVEL=debug sugar-emulator		SUGAR_LOGGER_LEVEL=debug sugar-emulator

Line 20:		Line 42:
	If your bug involves the presence service, you might also want to follow the steps for [[BugSquad/Telepathy Debugging]].		If your bug involves the presence service, you might also want to follow the steps for [[BugSquad/Telepathy Debugging]].

	== On the XO (using Sugar 0.82.x)==		== On the XO-1 (using Sugar 0.82.x)==
	These are general steps to follow when providing logs for ~~some~~ bug:		These are general steps to follow when providing logs for a bug:

	* Start the Terminal activity.		* Start the Terminal activity.
Line 44:		Line 66:
	Another useful command is:		Another useful command is:
	<code>dmesg</code>		<code>dmesg</code>
	It prints out all of the kernel's messages and warnings for this session, with any new stuff at the end.		It prints out all of the kernel's messages and warnings for this session, with any new stuff at the end.

	~~[[Category:BugSquad]]~~
	~~[[Category:HowTo]]~~

Cjl: moved Walter is a wanker 7/Get Logs to BugSquad/Get Logs over redirect: revert

2010-02-25T00:15:58Z

moved Walter is a wanker 7/Get Logs to BugSquad/Get Logs over redirect: revert

← Older revision	Revision as of 20:15, 24 February 2010
(No difference)

Faggot: moved BugSquad/Get Logs to Walter is a wanker 7/Get Logs: Walter is a wanker

2010-02-24T23:46:29Z

moved BugSquad/Get Logs to Walter is a wanker 7/Get Logs: Walter is a wanker

← Older revision	Revision as of 19:46, 24 February 2010
(No difference)

Patrol: moved Walter is a wanker 11/Get Logs to BugSquad/Get Logs over redirect: revert

2010-02-24T01:34:10Z

moved Walter is a wanker 11/Get Logs to BugSquad/Get Logs over redirect: revert

← Older revision	Revision as of 21:34, 23 February 2010
(No difference)

Page move vandal: moved BugSquad/Get Logs to Walter is a wanker 11/Get Logs: Walter is a wanker

2010-02-24T00:20:42Z

moved BugSquad/Get Logs to Walter is a wanker 11/Get Logs: Walter is a wanker

← Older revision	Revision as of 20:20, 23 February 2010
(No difference)