Difference between revisions of "Development Team/Jhbuild/Ubuntu"

From Sugar Labs
Jump to: navigation, search
(older and may be deprecated: remove obsolete item)
(clean up)
Line 1: Line 1:
 
== Supported versions ==
 
== Supported versions ==
===9.04===
 
====5SEP9====
 
  
./sugar-jhbuild buildone sugar-base sugar-toolkit sugar
+
Currently Intrepid (8.10) and Jaunty (9.04) are supported.
  
U904 stopped working. Black screen on Xephyr. Going to try
+
== Prerequisites ==
DISPLAY=:0 ./sugar-jhbuild run
 
Didn't work because I had gtk-recordmydesktop running at the same time. I started Sugar and then started GTK RMD with no problems.
 
  
====4SEP9====
 
All worked from a full update/ build to run.
 
 
====older and may be deprecated====
 
Jaunty (9.04) has [http://dev.sugarlabs.org/ticket/310 a broken D-Bus security configuration] that prevents sugar-emulator from working (because Xephyr cannot work).
 
On both versions [http://dev.sugarlabs.org/ticket/342 sugar-emulator doesn't work properly if the X server uses evdev as keyboard driver] (because of a Xephyr bug).
 
 
===8.10===
 
Currently intrepid (8.10) is supported.
 
 
== Prerequites ==
 
 
In order to install sugar-jhbuild, you need git-core and svn.
 
In order to install sugar-jhbuild, you need git-core and svn.
  
 
== Installing dependencies ==
 
== Installing dependencies ==
 +
 
After installing and updating sugar-jhbuild according to the [[../|common instructions]], you can use this invocation to install all dependencies automatically:
 
After installing and updating sugar-jhbuild according to the [[../|common instructions]], you can use this invocation to install all dependencies automatically:
  
Line 28: Line 14:
  
 
== Fixing RPATH ==
 
== Fixing RPATH ==
 +
 
To work around a bug in the Gnome Python bindings, you need to issue the following commands after installing all dependencies:
 
To work around a bug in the Gnome Python bindings, you need to issue the following commands after installing all dependencies:
  
Line 35: Line 22:
 
     -name "*.so" | sudo xargs chrpath -d
 
     -name "*.so" | sudo xargs chrpath -d
  
== PenguinTV ==
+
== Significant bugs ==
 +
 
 +
Jaunty (9.04) has [http://dev.sugarlabs.org/ticket/310 a broken D-Bus security configuration] that prevents sugar-emulator from working (because Xephyr cannot work).
 +
On both versions [http://dev.sugarlabs.org/ticket/342 sugar-emulator doesn't work properly if the X server uses evdev as keyboard driver] (because of a Xephyr bug).
 +
 
 +
== Potential pitfalls ==
  
You may have some issues with penguintv on Ubuntu, just interrupt the pull with a CTRL+C, open a shell, repeat the command manually, and accept the certificate permanently.
+
* gtk-recordmydesktop may prevent sugar-emulator from working properly
 +
* You may have some issues with penguintv, just interrupt the pull with a CTRL+C, open a shell, repeat the command manually, and accept the certificate permanently.

Revision as of 13:57, 21 September 2009

Supported versions

Currently Intrepid (8.10) and Jaunty (9.04) are supported.

Prerequisites

In order to install sugar-jhbuild, you need git-core and svn.

Installing dependencies

After installing and updating sugar-jhbuild according to the common instructions, you can use this invocation to install all dependencies automatically:

./sugar-jhbuild depscheck -s | sudo xargs aptitude -y install

Fixing RPATH

To work around a bug in the Gnome Python bindings, you need to issue the following commands after installing all dependencies:

sudo aptitude install chrpath
find /usr/lib/python-support/python-gnome2/python2.5/gtk-2.0 \
    /usr/lib/python-support/python-gconf/python2.5/gtk-2.0 \
    -name "*.so" | sudo xargs chrpath -d

Significant bugs

Jaunty (9.04) has a broken D-Bus security configuration that prevents sugar-emulator from working (because Xephyr cannot work). On both versions sugar-emulator doesn't work properly if the X server uses evdev as keyboard driver (because of a Xephyr bug).

Potential pitfalls

  • gtk-recordmydesktop may prevent sugar-emulator from working properly
  • You may have some issues with penguintv, just interrupt the pull with a CTRL+C, open a shell, repeat the command manually, and accept the certificate permanently.