OK, I’m trying to install GTG again. This time, I’m using Ubuntu 13.10 Desktop (64-bit). To get things started, I ran the same pre-steps as before: added myself to the sudo list, installed some basic tools, and set up bzr, and grabbed the code from launchpad. I tried running:

sudo apt-get install python-liblarch python-liblarch-gtk

But it turns out that this installs v1.0 and GTG is expecting v2.1. No worries. Just follow the instructions to do a git clone. The trick after that is to run ./gtg -l (instead of just ./gtg). To eliminate the other warning messages that GTG throws, just do:

sudo apt-get install python-dateutil python-suds python-evolution

Now to get the geolocation stuff to work, installing geoclue is easy:

sudo apt-get install python-geoclue

To get python-clutter, I had to update my sources.list to reference squeeze, since it seems it’s not listed in the wheezy dist. So that definitely fixes it so that apt-get can find the package, but it still gave me problems, just like before:

The following packages have unmet dependencies:
Depends: libclutter-1.0-0 (>= 1.0.8) but it is not going to be installed
Depends: python (E: Unable to correct problems, you have held broken packages

So this is saying that, to use python-clutter, I need to downgrade my python to something < 2.7. OK, so I found that one of the easiest way to install older versions of python is to add PPAs like this to your sources.list:

sudo add-apt-repository ppa:fkrull/deadsnakes
sudo apt-get update
sudo apt-get install python2.6 python2.6-dev
ls -lsa /usr/bin/python* # you should see python2.6 listed here now

Now that I have a version that might work with python-clutter, I can set up a virtual environment that only has python2.6 and see if it works:

sudo apt-get install python-virtualenv
mkdir ~/<gtg_virtualenv>
cd <gtg_virtualenv>
virtualenv -p /usr/bin/python2.6 --no-site-packages .
source bin/activate

The --no-site-packages is important, as it says that we won’t look at any of the packages that are in our host environment (like python2.7). Of course, that also means that you’ll have to reinstall any packages that you need. And that explains why, if you go run GTG right off the bat, you’ll get error messages like:

File "./gtg", line 26, in 
from gtk.gdk import Screen
ImportError: No module named gtk.gdk

And that’s where my patient with this experiment ends. I couldn’t seem to figure out an easy way to install the right set of packages. I tried the usual suspects (pygobject, etc), but none of them worked or they were already installed, so it didn’t help. Oh well, back to the drawing board!

Leave a Comment

Your email address will not be published. Required fields are marked *