Difference between revisions of "Submit Bugs/Problems"

From Sugar Labs
Jump to navigation Jump to search
(Login fail on Fedora 9 - no useful error message.)
(remove nowiki, fix typos)
 
(58 intermediate revisions by 17 users not shown)
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>
+
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.  
== Please Describe Bugs & Problems Here ==
 
(Developers: please continue to use the [http://dev.laptop.org Trac system] to report and monitor bugs.)
 
----
 
  
 +
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.
  
===WPA/WEP Connectivity Problems===
+
Then visit the issues tab of the repo, and hit the big green button to report your issue.
  
Hi I still have problems connecting to WPA, even with build 703 installed. I enter a password and nothing happens. Any advice?
+
If you haven't written issue reports before, here's a great guide: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
: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)
 
 
 
===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?
 
 
 
 
 
[[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?
 

Latest revision as of 13:50, 14 May 2016

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 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