Submit Bugs/Problems - Revision history

Pikurasa: copyedit

2024-10-08T17:06:28Z

copyedit

← Older revision		Revision as of 13:06, 8 October 2024
Line 1:		Line 1:
	If you find a bug or would like to report an issue with Sugar, visit https://github.com/sugarlabs and look for the activity or a sugar component repository ~~hat~~ you think is relevant.		If you find a bug or would like to report an issue with Sugar, visit https://github.com/sugarlabs and look for the activity or a sugar component repository that you think is relevant.

	If you don't know which one to use, use https://github.com/sugarlabs/sugar, and be sure to sign up and sign in to Github.		If you don't know which one to use, use https://github.com/sugarlabs/sugar, and be sure to sign up and sign in to Github.

Davelab6: remove nowiki, fix typos

2016-05-14T17:50:25Z

remove nowiki, fix typos

← Older revision		Revision as of 13:50, 14 May 2016
Line 1:		Line 1:
	~~__TOC__~~		If you find a bug or would like to report an issue with Sugar, visit https://github.com/sugarlabs and look for the activity or a sugar component repository hat you think is relevant.

	If you ~~find a bug or would like~~ to ~~report an issue with Sugar~~, ~~visit <nowiki>~~https://github.com/sugarlabs</~~nowiki>~~ and ~~look for the activity or a sugar component tepository hat you think is relevant~~.		If you don't know which one to use, use https://github.com/sugarlabs/sugar, and be sure to sign up and sign in to Github.

	~~If you don't know which one to use, use <nowiki>https://github.com/sugarlabs/sugar</nowiki>~~, and ~~be sure to sign up and sign in~~ to ~~Github~~.		Then visit the issues tab of the repo, and hit the big green button to report your issue.

	~~Then visit the issues tab of the repo, and rit the big green button to report your issue.~~		If you haven't written issue reports before, here's a great guide: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

	If you haven't written issue reports before, here's a great guide: ~~<nowiki>~~http://www.chiark.greenend.org.uk/~sgtatham/bugs.html~~</nowiki>~~
	:

Davelab6: Refresh page with 2016 content

2016-05-14T17:49:34Z

Refresh page with 2016 content

← Older revision		Revision as of 13:49, 14 May 2016
Line 1:		Line 1:
	__TOC__		__TOC__

	~~<big>'''Where to Describe Bugs & Problems'''</big>~~		If you find a bug or would like to report an issue with Sugar, visit <nowiki>https://github.com/sugarlabs</nowiki> and look for the activity or a sugar component tepository hat you think is relevant.
	* Communicate directly with the [[Development Team]]'s work ticket system by using the [http://bugs.sugarlabs.org Sugar Labs '''trac''' instance] to report bugs you find ~~with Sugar on the various distributions.~~
	* Problems registered in the '''trac''' database become work tickets to which you may subscribe, have comments appended, titles changed, log files or screenshots attached, links included, and more.
	* The tickets are reviewed periodically by the [[BugSquad]] and so get more [[Development Team]] attention than a ~~report in the wiki~~ or ~~on a mailing list, but are not as broadly announced as with a mailing list post.~~
	* To get broad community attention to ~~a problem, prepare a '''trac''' ticket AND announce it~~ with ~~a link to the '''trac''' ticket page in a posting to sugar-devel AT lists.sugarlab.org (or~~, ~~if OLPC XO-1 hardware-specific, to devel AT lists.laptop.org). Register your email address at http~~://~~lists~~.sugarlabs~~.org~~/~~listinfo/sugar-devel or http://lists.laptop.org/listinfo/devel to avoid delays in acceptance of your posts.~~
	* In your report, please include background information on your version of Sugar and ~~any links that might be helpful~~ for ~~those investigating~~ the ~~problem.~~
	~~: See [[BugSquad/Bug Report]] for reporting guidance.~~
	~~: You may also [[Sugar_on_a_Stick/Getting_Involved/Testing#Report_your_hardware_profile\| report your hardware profile]] and upload log files as described in [[BugSquad/Get Logs]].~~
	* You may want to review [[Sugar Labs/FAQ]] for some common questions, and [[:Category:Testing]] for other testers' reports.

	~~Email sent~~ to ~~feedback AT~~ sugarlabs~~.org will~~ be ~~forwarded~~ to the ~~IAEP mailing list~~, ~~which is used for general discussion of~~ the ~~Sugar Labs education project~~.		If you don't know which one to use, use <nowiki>https://github.com/sugarlabs/sugar</nowiki>, and be sure to sign up and sign in to Github.
	~~== bugs.sugarlabs.org/timeline ==~~
	~~{{Iframe\|collapsed=\|~~http://~~bugs~~.~~sugarlabs~~.org/~~timeline~~		Then visit the issues tab of the repo, and rit the big green button to report your issue.
	~~\|http:/~~/bugs.~~sugarlabs.org~~/~~timeline\|900\|800\|1}}~~
			If you haven't written issue reports before, here's a great guide: <nowiki>http://www.chiark.greenend.org.uk/~sgtatham/bugs.html</nowiki>
			:

FGrose: archive old reports

2014-02-05T16:10:06Z

archive old reports

@@ Line 1: / Line 1: @@
 __TOC__
-<big>'''Please Describe Bugs & Problems Here'''</big>
+<big>'''Where to Describe Bugs & Problems'''</big>
 * Communicate directly with the [[Development Team]]'s work ticket system by using the [http://bugs.sugarlabs.org Sugar Labs '''trac''' instance] to report bugs you find with Sugar on the various distributions.
 * Problems registered in the '''trac''' database become work tickets to which you may subscribe, have comments appended, titles changed, log files or screenshots attached, links included, and more.
 * The tickets are reviewed periodically by the [[BugSquad]] and so get more [[Development Team]] attention than a report in the wiki or on a mailing list, but are not as broadly announced as with a mailing list post.
 * To get broad community attention to a problem, prepare a '''trac''' ticket AND announce it with a link to the '''trac''' ticket page in a posting to sugar-devel AT lists.sugarlab.org (or, if OLPC XO-1 hardware-specific, to devel AT lists.laptop.org).  Register your email address at http://lists.sugarlabs.org/listinfo/sugar-devel or http://lists.laptop.org/listinfo/devel to avoid delays in acceptance of your posts.
 * In your report, please include background information on your version of Sugar and any links that might be helpful for those investigating the problem.
@@ Line 14: / Line 12: @@
 Email sent to feedback AT sugarlabs.org will be forwarded to the IAEP mailing list, which is used for general discussion of the Sugar Labs education project.
+== bugs.sugarlabs.org/timeline ==
-===Journal comes and goes===
+{{Iframe|collapsed=|http://bugs.sugarlabs.org/timeline
-Sugar on Ubuntu doesn't always preserve the Journal between sessions.
+|http://bugs.sugarlabs.org/timeline|900|800|1}}

Patrol: Reverted edits by Alice-thomas222 (talk) to last revision by FGrose

2011-03-09T07:12:35Z

Reverted edits by Alice-thomas222 (talk) to last revision by FGrose

← Older revision		Revision as of 03:12, 9 March 2011
Line 95:		Line 95:

	--[[User:DeanBrettle\|DeanBrettle]] 13:12, 6 February 2010		--[[User:DeanBrettle\|DeanBrettle]] 13:12, 6 February 2010

	~~[http://www.designerevaluation.com/logo-design/ logo design]~~
	~~[http://www.designerevaluation.com/ website design]~~

Alice-thomas222: /* XOlympics activity fails if python-elements package installed on Fedora 12 */

2011-03-09T07:00:33Z

XOlympics activity fails if python-elements package installed on Fedora 12

← Older revision		Revision as of 03:00, 9 March 2011
Line 95:		Line 95:

	--[[User:DeanBrettle\|DeanBrettle]] 13:12, 6 February 2010		--[[User:DeanBrettle\|DeanBrettle]] 13:12, 6 February 2010

			[http://www.designerevaluation.com/logo-design/ logo design]
			[http://www.designerevaluation.com/ website design]

FGrose at 03:40, 28 July 2010

2010-07-28T03:40:02Z

← Older revision		Revision as of 23:40, 27 July 2010
Line 1:		Line 1:
	~~<noinclude>{{TOCright}}</noinclude>~~		__TOC__

	<big>'''Please Describe Bugs & Problems Here'''</big>		<big>'''Please Describe Bugs & Problems Here'''</big>
Line 5:		Line 5:
	* Problems registered in the '''trac''' database become work tickets to which you may subscribe, have comments appended, titles changed, log files or screenshots attached, links included, and more.		* Problems registered in the '''trac''' database become work tickets to which you may subscribe, have comments appended, titles changed, log files or screenshots attached, links included, and more.
	* The tickets are reviewed periodically by the [[BugSquad]] and so get more [[Development Team]] attention than a report in the wiki or on a mailing list, but are not as broadly announced as with a mailing list post.		* The tickets are reviewed periodically by the [[BugSquad]] and so get more [[Development Team]] attention than a report in the wiki or on a mailing list, but are not as broadly announced as with a mailing list post.
	{{Iframe\|     → Click the [show] link to see recent ticket activity:		{{Iframe\|     → Click the [show ▼] link to see recent ticket activity:
	\|http://bugs.sugarlabs.org/timeline\|900\|500\|1}}		\|http://bugs.sugarlabs.org/timeline\|900\|500\|1}}
	* To get broad community attention to a problem, prepare a '''trac''' ticket AND announce it with a link to the '''trac''' ticket page in a posting to sugar-devel AT lists.sugarlab.org (or, if OLPC XO-1 hardware-specific, to devel AT lists.laptop.org). Register your email address at http://lists.sugarlabs.org/listinfo/sugar-devel or http://lists.laptop.org/listinfo/devel to avoid delays in acceptance of your posts.		* To get broad community attention to a problem, prepare a '''trac''' ticket AND announce it with a link to the '''trac''' ticket page in a posting to sugar-devel AT lists.sugarlab.org (or, if OLPC XO-1 hardware-specific, to devel AT lists.laptop.org). Register your email address at http://lists.sugarlabs.org/listinfo/sugar-devel or http://lists.laptop.org/listinfo/devel to avoid delays in acceptance of your posts.

FGrose at 13:54, 11 May 2010

2010-05-11T13:54:33Z

← Older revision		Revision as of 09:54, 11 May 2010
Line 5:		Line 5:
	* Problems registered in the '''trac''' database become work tickets to which you may subscribe, have comments appended, titles changed, log files or screenshots attached, links included, and more.		* Problems registered in the '''trac''' database become work tickets to which you may subscribe, have comments appended, titles changed, log files or screenshots attached, links included, and more.
	* The tickets are reviewed periodically by the [[BugSquad]] and so get more [[Development Team]] attention than a report in the wiki or on a mailing list, but are not as broadly announced as with a mailing list post.		* The tickets are reviewed periodically by the [[BugSquad]] and so get more [[Development Team]] attention than a report in the wiki or on a mailing list, but are not as broadly announced as with a mailing list post.
	: {{Iframe\|Click the [show] link to see recent ticket activity:		{{Iframe\|     → Click the [show] link to see recent ticket activity:
	\|http://bugs.sugarlabs.org/timeline\|900\|500\|1}}		\|http://bugs.sugarlabs.org/timeline\|900\|500\|1}}
	* To get broad community attention to a problem, prepare a '''trac''' ticket AND announce it with a link to the '''trac''' ticket page in a posting to sugar-devel AT lists.sugarlab.org (or, if OLPC XO-1 hardware-specific, to devel AT lists.laptop.org). Register your email address at http://lists.sugarlabs.org/listinfo/sugar-devel or http://lists.laptop.org/listinfo/devel to avoid delays in acceptance of your posts.		* To get broad community attention to a problem, prepare a '''trac''' ticket AND announce it with a link to the '''trac''' ticket page in a posting to sugar-devel AT lists.sugarlab.org (or, if OLPC XO-1 hardware-specific, to devel AT lists.laptop.org). Register your email address at http://lists.sugarlabs.org/listinfo/sugar-devel or http://lists.laptop.org/listinfo/devel to avoid delays in acceptance of your posts.
	* In your report, please include background information on your version of Sugar and any links that might be helpful for those investigating the problem.		* In your report, please include background information on your version of Sugar and any links that might be helpful for those investigating the problem.
	: See [[BugSquad/Bug Report]] for reporting guidance.		: See [[BugSquad/Bug Report]] for reporting guidance.
	: You may also [[Sugar_on_a_Stick/Getting_Involved/Testing#Report_your_hardware_profile report your hardware profile]] and upload log files as described in [[BugSquad/Get Logs]].		: You may also [[Sugar_on_a_Stick/Getting_Involved/Testing#Report_your_hardware_profile\| report your hardware profile]] and upload log files as described in [[BugSquad/Get Logs]].
	* You may want to review [[Sugar Labs/FAQ]] for some common questions, and [[:Category:Testing]] for other testers' reports.		* You may want to review [[Sugar Labs/FAQ]] for some common questions, and [[:Category:Testing]] for other testers' reports.

FGrose at 13:49, 11 May 2010

2010-05-11T13:49:32Z

← Older revision		Revision as of 09:49, 11 May 2010
Line 1:		Line 1:
	<noinclude>{{TOCright}}</noinclude>		<noinclude>{{TOCright}}</noinclude>

	== Please Describe Bugs & Problems Here ==		<big>'''Please Describe Bugs & Problems Here'''</big>
	* Communicate directly with the [[Development Team]]'s work ticket system by using the [http://bugs.sugarlabs.org Sugar Labs '''trac''' instance] to report bugs you find with Sugar on the various distributions.		* Communicate directly with the [[Development Team]]'s work ticket system by using the [http://bugs.sugarlabs.org Sugar Labs '''trac''' instance] to report bugs you find with Sugar on the various distributions.
	* Problems registered in the '''trac''' database become work tickets to which you may subscribe, have comments appended, titles changed, log files or screenshots attached, links included, and more.		* Problems registered in the '''trac''' database become work tickets to which you may subscribe, have comments appended, titles changed, log files or screenshots attached, links included, and more.
	* The tickets are reviewed periodically by the [[BugSquad]] and so get more [[Development Team]] attention than a report in the wiki or on a mailing list, but are not as broadly announced as with a mailing list post.		* The tickets are reviewed periodically by the [[BugSquad]] and so get more [[Development Team]] attention than a report in the wiki or on a mailing list, but are not as broadly announced as with a mailing list post.
			: {{Iframe\|Click the [show] link to see recent ticket activity:
			\|http://bugs.sugarlabs.org/timeline\|900\|500\|1}}
	* To get broad community attention to a problem, prepare a '''trac''' ticket AND announce it with a link to the '''trac''' ticket page in a posting to sugar-devel AT lists.sugarlab.org (or, if OLPC XO-1 hardware-specific, to devel AT lists.laptop.org). Register your email address at http://lists.sugarlabs.org/listinfo/sugar-devel or http://lists.laptop.org/listinfo/devel to avoid delays in acceptance of your posts.		* To get broad community attention to a problem, prepare a '''trac''' ticket AND announce it with a link to the '''trac''' ticket page in a posting to sugar-devel AT lists.sugarlab.org (or, if OLPC XO-1 hardware-specific, to devel AT lists.laptop.org). Register your email address at http://lists.sugarlabs.org/listinfo/sugar-devel or http://lists.laptop.org/listinfo/devel to avoid delays in acceptance of your posts.
	* In your report, please include background information on your version of Sugar and any links that might be helpful for those investigating the problem. You may also [~~http://wiki.sugarlabs.org/go/~~Sugar_on_a_Stick/Getting_Involved/Testing#Report_your_hardware_profile report your hardware profile] and upload log files as described in [[~~OLPC:Reporting bugs~~]].		* In your report, please include background information on your version of Sugar and any links that might be helpful for those investigating the problem.
			: See [[BugSquad/Bug Report]] for reporting guidance.
			: You may also [[Sugar_on_a_Stick/Getting_Involved/Testing#Report_your_hardware_profile report your hardware profile]] and upload log files as described in [[BugSquad/Get Logs]].
	* You may want to review [[Sugar Labs/FAQ]] for some common questions, and [[:Category:Testing]] for other testers' reports.		* You may want to review [[Sugar Labs/FAQ]] for some common questions, and [[:Category:Testing]] for other testers' reports.

Walter: Reverted edits by Goo (Talk) to last revision by David Kergyl

2010-04-02T23:18:20Z

Reverted edits by Goo (Talk) to last revision by David Kergyl

Show changes