Difference between revisions of "Development Team/Jhbuild/Ubuntu"
< Development Team | Jhbuild
Jump to navigation
Jump to search
m (moved Development Team/Jhbuild/Ubuntu to Anal bleaching 15/Jhbuild/Ubuntu: Anal bleaching) |
m (moved Anal bleaching 15/Jhbuild/Ubuntu to Development Team/Jhbuild/Ubuntu over redirect: revert) |
(No difference)
|
Revision as of 17:42, 21 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 (8.10 / 9.04)
To work around a bug in the Gnome Python bindings shipped by Intrepid (8.10) and Jaunty (9.04), 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.