Difference between revisions of "Submit Bugs/Problems"

From Sugar Labs
Jump to navigation Jump to search
m (moved Anal bleaching 12 to Submit Bugs/Problems over redirect: revert)
m (copyedit)
 
(21 intermediate revisions by 10 users not shown)
Line 1: Line 1:
<noinclude>{{GoogleTrans-en}}</noinclude>
+
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.  
{{TOCright}}
 
== Please Describe Bugs & Problems Here ==
 
* You may try our new, community-powered support site, '''http://www.getsatisfaction.com/sugarlabs''',
 
* or our '''[http://launchpad.net/soas Sugar on a Stick project support site]'''.
 
* Communicate directly with the [[Development Team]]'s work ticket system by using the [http://trac.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.
 
* Bugs or new features specific to the upcoming [[Sugar on a Stick]] v2 beta should be filed into this tracker, http://launchpad.net/soas; see this [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg08066.html announcement].
 
* 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 our reports, please include background information on your version of Sugar and any links that might be helpful for those investigating the problem.
 
  
* You may want to review [[Sugar Labs/FAQ]] for some common questions, and [[:Category:Testing]] for other testers' reports.
+
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.  
  
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.
+
Then visit the issues tab of the repo, and hit the big green button to report your issue.  
  
===Journal comes and goes===
+
If you haven't written issue reports before, here's a great guide: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
Sugar on Ubuntu doesn't always preserve the Journal between sessions.
 
:It seems that the index is occasionally broken and the datastore is thus copied to a timestamped entry in .sugar/default/ and empty datastore is opened.
 
::Is this still a problem with 0.84? If so, could you [http://trac.sugarlabs.org please file a ticket]?
 
 
 
===.84 sugar===
 
Apps won't load in Fedora 11 emulating sugar under root.
 
Video of behavior: http://www.youtube.com/watch?v=1Lvvjvi3yE0
 
===Colors on Ubuntu===
 
The Colors activity canvas is only half the width of the screen and the aspect ratio is compressed.
 
:This bug is being tracked in [http://trac.sugarlabs.org/ticket/592 Ticket 592]
 
 
 
===Turtle Art===
 
Turtle Art on a non-1200x900 screen doesn't scale display.
 
:Resolved since Version 17.
 
 
 
===Hover menus from the Frame on Ubuntu===
 
They appear in the upper-left corner.
 
:Resolved in 0.84
 
 
 
===Can't Shutdown Sugar Spin===
 
I am using the Sugar Spin on a CD and nothing happens when I click on shutdown.
 
:The Sugar LiveCD and LiveUSB releases are going through a lot of testing and newer versions are  more reliable. Please try again at [[Downloads]].
 
 
 
===WPA/WEP Connectivity Problems===
 
 
 
Hi I still have problems connecting to WPA, even with build 703 installed. I enter a password and nothing happens. Any advice?
 
:Hmmm. This one falls between the crack of Sugar and the OLPC network stack. Have you asked for help from the OLPC support team? --[[User:Walter|Walter]] 19:57, 22 May 2008 (UTC)
 
::Looks like a place where more feedback should be given in the UI. Any concrete ideas? [[User:Tomeu|Tomeu]] 09:31, 23 May 2008 (UTC)
 
 
 
No, I haven't. Maybe we should explain what questions should go to OLPC team and what goes here.
 
:Good point. --[[User:Walter|Walter]] 20:15, 22 May 2008 (UTC)
 
 
 
===UI Element sizes===
 
This is more of an issue than a bug. But I don't know where else to put it for now.
 
 
 
As Sugar is ported to other systems, they will have screens with dimensions significantly different than the XO laptop. On the XO the assumption is made of 1200 x 900 pix, with Sugar occupying a grid of 12 x 16 elements 75 pixels square.
 
 
 
How will we deal with issues like screens in other aspect ratios, or where the 75-pixel element is not a practical size?
 
[[User:Rmyers|Rmyers]] 20:51, 22 May 2008 (UTC)
 
 
 
:Much of this is ameliorated by the extensive use of SVG for the graphics. --[[User:Walter|Walter]] 21:10, 22 May 2008 (UTC)
 
:There is active development on this issue. See, for example, http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg02712.html. --[[User:FGrose|FGrose]] 04:56, 20 March 2009 (UTC)
 
 
 
===Sonata===
 
 
 
I cannot access MP3 files I transfer to my SD card through Sonata. It does not let me select source directories/devices. Any advice? Is there a better player for Sugar/XO?
 
:perhaps you'll have better luck with [http://activities.sugarlabs.org/en-US/sugar/addon/4045 Jukebox]? If not, please [http://dev.sugarlabs.org file a bug report]
 
 
 
[[Category:General public]]
 
 
 
===Login fail on Fedora 9===
 
 
 
I have sugar installed on Fedora 9.  The first session I start allows me to give my name and choose my colour.  After that the session aborts with no further communication.  Every subsequent session aborts with no error message.  The only useful looking message is in the .xsession-errors file and looks like this.
 
 
 
*** PULSEAUDIO: Unable to connect: Connection refused
 
*** Is your sound server running?
 
*** See: http://www.pulseaudio.org/wiki/Troubleshooting
 
 
** (sugar-shell:12977): CRITICAL **: _wrap_gst_mixer_list_tracks: assertion `GST_IS_MIXER (self->obj)' failed
 
 
 
I checked over the fedora bug tracker and found some missing dependencies mentioned, but those were all installed (e.g. gstreamer).  When doing this I was using a second X session to my main one, but previously I have had the same problem in the main X session.  Any suggestions?
 
 
 
:I'll see if someone from the Fedora team can offer some help. --[[User:Walter|Walter]] 22:49, 21 September 2008 (UTC)
 
::What I have learned so far (from Marco)
 
::The Fedora 9 packages are basically untested :( Rawhide is getting much better. Perhaps we should spend a bit of time one of these days and push the latest packages in Fedora 9.
 
::There is a sugar component on http://bugzilla.redhat.com which can be used for distribution specific issues. Upstream issues should be reported to dev.laptop.org. Yeah, it can be hard/impossible for the user to know if it's distribution or upstream. I suggest to always give priority to upstream when unsure. --[[User:Walter|Walter]] 12:57, 22 September 2008 (UTC)
 
::This resolved in the F11 release. --[[User:Walter|Walter]] 13:54, 20 March 2009 (UTC)
 
 
 
 
 
===XOlympics activity fails if python-elements package installed on Fedora 12===
 
 
 
XOlympics uses a custom local "elements" module, but if python-elements is installed, XOlympics can't find box2d because it looks it finds the site-wide elements module first.  The Physics activity seems to require that python-elements is installed, so the only workaround I found was to add:
 
 
 
import sys
 
sys.path.insert(0, ".")
 
 
 
to the top of "XOlympics.activity/tools.py"
 
 
 
--[[User:DeanBrettle|DeanBrettle]] 13:12, 6 February 2010
 

Latest revision as of 12:06, 8 October 2024

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.

Then visit the issues tab of the repo, and hit 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