Difference between revisions of "Development Team/Jhbuild/Ubuntu"
< Development Team | Jhbuild
Jump to navigation
Jump to search
Sascha silbe (talk | contribs) (→Supported versions: add Karmic) |
Sascha silbe (talk | contribs) (→Significant bugs: mention karmic) |
||
| Line 24: | Line 24: | ||
== Significant bugs == | == Significant bugs == | ||
| − | Jaunty (9.04) | + | Jaunty (9.04) and Karmic (9.10) have [http://dev.sugarlabs.org/ticket/310 a broken D-Bus security configuration] that prevents sugar-emulator from working (because Xephyr cannot work). |
| − | On | + | On all 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 == | == Potential pitfalls == | ||
Revision as of 10:15, 1 February 2010
Supported versions
Currently Intrepid (8.10), Jaunty (9.04) and Karmic (9.10) 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) and Karmic (9.10) have a broken D-Bus security configuration that prevents sugar-emulator from working (because Xephyr cannot work). On all 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.