1,009
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + + + Line 11:
Line 13: − + Line 24:
Line 26: − + + + − + − + Line 44:
Line 48: − + Line 52:
Line 56: − + Line 58:
Line 62: − + − + Line 69:
Line 73: − + Line 75:
Line 79: − + Line 81:
Line 85: − + Line 95:
Line 99: − * [[User:Mokurai|Mokurai]] Ubuntu 11.4 Natty Narwhal + − ** 731133 TurtleArt cannot start due to missing files.+ − ** 307206 sugar moon activity works and should be packaged—Done. Please close.+ − + − ** 307209 sugar speak activity works fine and should be packaged+ − ** 623726 read fails to start+ − ** 307225 sugar ruler works/should be packaged, screen resolution fix+ − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
/* Ubuntu 11.4 Natty Narwhal Broken packages
Sugar on XOs runs on Fedora Linux. There are also Sugar packages for a number of [[Supported systems|other Linux distributions]]. When Sugar is packaged for a new distribution, please add the bug tracker for that system to this page, along with a link to information on how to use it.
Sugar on XOs runs on Fedora Linux. There are also Sugar packages for a number of [[Supported systems|other Linux distributions]]. When Sugar is packaged for a new distribution, please add the bug tracker for that system to this page, along with a link to information on how to use it.
== Fedora specific bugs ==
==Reporting bugs==
=== Fedora specific bugs ===
To report a bug in Fedora, go to http://bugzilla.redhat.com.
To report a bug in Fedora, go to http://bugzilla.redhat.com.
Refer to the [https://fedoraproject.org/wiki/BugsAndFeatureRequests Bugs and Feature Requests] page for detailed instructions on filing Fedora bugs.
Refer to the [https://fedoraproject.org/wiki/BugsAndFeatureRequests Bugs and Feature Requests] page for detailed instructions on filing Fedora bugs.
==Debian==
===Debian===
About [http://www.debian.org/Bugs/Reporting.en.html Debian Bug Tracking System] (BTS)
About [http://www.debian.org/Bugs/Reporting.en.html Debian Bug Tracking System] (BTS)
If you have questions that the interactive prompts of reportbug do not resolve, you can refer to the rest of the documentation at the link above, or ask the [http://lists.debian.org/debian-user/ Debian user mailing list].
If you have questions that the interactive prompts of reportbug do not resolve, you can refer to the rest of the documentation at the link above, or ask the [http://lists.debian.org/debian-user/ Debian user mailing list].
==Ubuntu==
===Ubuntu===
* [https://bugs.launchpad.net/ubuntu Ubuntu Bug Tracking System] (BTS)
[https://bugs.launchpad.net/ubuntu Bugs in Ubuntu]
* [https://bugs.launchpad.net/ubuntu Bugs in Ubuntu]
[https://wiki.ubuntu.com/BugSquad Ubuntu Bug Squad]
* [https://wiki.ubuntu.com/BugSquad Ubuntu Bug Squad]
Ubuntu uses the apport/ubuntu-bug program to gather data on software problems and report bugs. Usage is
Ubuntu uses the apport/ubuntu-bug program to gather data on software problems and report bugs. Usage is
for other options.
for other options.
==ALT Linux==
===ALT Linux===
* [https://bugzilla.altlinux.org/ Bugzilla server at ALT Linux]
* [https://bugzilla.altlinux.org/ Bugzilla server at ALT Linux]
* [http://www.altlinux.org/ALT_Linux_Bugzilla ALT Linux Bugzilla] Documentation (in Russian)
* [http://www.altlinux.org/ALT_Linux_Bugzilla ALT Linux Bugzilla] Documentation (in Russian)
==Mandriva==
===Mandriva===
* [https://qa.mandriva.com/index.cgi Mandriva Bugzilla]
* [https://qa.mandriva.com/index.cgi Mandriva Bugzilla]
* [http://wiki.mandriva.com/en/Development/Howto/Bugzilla Mandriva Bugzilla Howto]
* [http://wiki.mandriva.com/en/Development/Howto/Bugzilla Mandriva Bugzilla Howto]
==Trisquel==
===Trisquel===
* [http://trisquel.info/en/project/issues Trisquel GNULinux Issues]
* [http://trisquel.info/en/project/issues Trisquel GNULinux Issues]
==OpenSUSE==
===OpenSUSE===
* [http://en.opensuse.org/openSUSE:Submitting_bug_reports Want to learn]: It is not the easiest thing that you ever did, but it is not rocket science either.
* [http://en.opensuse.org/openSUSE:Submitting_bug_reports Want to learn]: It is not the easiest thing that you ever did, but it is not rocket science either.
==Caixa Magica==
===Caixa Magica===
* [https://bugs.launchpad.net/caixamagica Bugs in The Caixa Magica Project]
* [https://bugs.launchpad.net/caixamagica Bugs in The Caixa Magica Project]
* [https://help.launchpad.net/Bugs Getting started with bug tracking in Launchpad. ]
* [https://help.launchpad.net/Bugs Getting started with bug tracking in Launchpad. ]
==Gentoo==
===Gentoo===
* [http://bugs.gentoo.org/ Gentoo's Bugzilla]
* [http://bugs.gentoo.org/ Gentoo's Bugzilla]
* [http://www.gentoo.org/doc/en/bugzilla-howto.xml Gentoo Bug Reporting Guide]
* [http://www.gentoo.org/doc/en/bugzilla-howto.xml Gentoo Bug Reporting Guide]
==Slackware==
===Slackware===
From [http://www.tuxradar.com/content/slackware-made-easy Slackware made easy]:
From [http://www.tuxradar.com/content/slackware-made-easy Slackware made easy]:
If you are willing to do systematic testing of packages in a particular distribution at each package release or upgrade and each distro upgrade, please add your name and data here, and e-mail [mailto:mokurai@sugarlabs.org Mokurai]. This does not entail a commitment to test every version of every package in the [http://activities.sugarlabs.org/ Sugar Labs Activity repository], just the packages included with your chosen distribution.
If you are willing to do systematic testing of packages in a particular distribution at each package release or upgrade and each distro upgrade, please add your name and data here, and e-mail [mailto:mokurai@sugarlabs.org Mokurai]. This does not entail a commitment to test every version of every package in the [http://activities.sugarlabs.org/ Sugar Labs Activity repository], just the packages included with your chosen distribution.
===Ubuntu 11.4 Natty Narwhal===
[[User:Mokurai|Mokurai]]
** 284968 Jigsaw fails to launch--Actually, cannot install because python-abiword is still missing.
Activity packages that cannot run should be removed or fixed: jigsaw, sliderpuzzle, browse, read, flipsticks.
Old
** 460111 sugar browse fails -- libxul.so: No such file or directory
* 307206 sugar '''moon''' activity works and should be packaged—Done. Please close.
* 601219 Sugar package files installed in wrong directory--Mostly fixed, except '''sliderpuzzle''' and '''jigsaw''', which have other issues.
Current
* 284968 '''Jigsaw''' fails to launch--Actually, cannot install because python-abiword is still missing.
* 307209 sugar '''speak''' activity works fine and should be packaged.
* 307225 sugar '''ruler''' works/should be packaged, screen resolution fix
* 459532 sugar-web-activity uninstallable due to python-xpcom dependency, should depend on xulrunner-1.9 instead
* 460111 sugar '''browse''' fails -- libxul.so: No such file or directory. Browse-122 ImportError: No module named hulahop
Browse downloads .xo bundles to the Journal, but Firefox does not. In that case, copy the bundle file to a USB drive. You can copy it to the Journal from there. Click to install and start the activity.
* 623726 '''read''' fails to start--Starts now, but does not open file.
* 731133 '''TurtleArt''' cannot start due to missing files.--Version 108 installs and runs. Please package.
* 788815 Sugar '''Flipsticks''' activity crashes on start.
* 788822 Sugar '''SliderPuzzle''' activity dependent on missing Abiword.
* 788832 '''Firefox''' in Sugar hangs on exit
[[User:Sascha silbe|Sascha Silbe]]
I am sad to announce that we are dropping Ubuntu support for
sugar-jhbuild. Karmic Koala (9.10), the last version of Ubuntu that
shipped all packages required to use Sugar (including all Fructose
activities), has went end-of-life on 2011-05-01.
Apart from a bug in the Ubuntu version of Xephyr that prevents
sugar-emulator from working out of the box [1], all recent Ubuntu
versions lack python-xpcom [2], a crucial package for Browse. The latter
issue can only be worked around by building all browser engine packages
(xulrunner, python-xpcom, hulahop) in sugar-jhbuild. We (that is, I)
lack the time to go this route again. At least in the past, Mozilla had
a bad record for security updates: most of the time, the required
patches needed to be hand-picked by downstream (in this case us) from
their VCS repository. This is not only error-prone, but also rather
time-consuming. AFAICT this hasn't changed a bit.
I can only hope that Surf grows to be a full replacement for Browse.
Once that happens and all required packages for Surf (probably going to
include some bleeding edge ones) enter the most recent Ubuntu version,
we can start supporting Ubuntu again.
I will keep the Ubuntu configuration files in the sugar-jhbuild
repository. Use them at your own risk. Feel free to send patches, but
please don't file bug reports about anything Ubuntu-specific.