Hi Phil, It looks as though gnome-pilot hasn't actually been built correctly. I don't know what steps you took (I didn't give detailed instructions, because usually people asking for patches and building packages are old hands at this stuff).
You say you built "gnome-pilot 1.161", but 1.161 refers to one single file from the gnome-pilot source tree. So I don't know whether you checked out the whole gnome-pilot source from CVS (I doubt it) or just dropped the updated gpilotd.c file into some other source distribution of gnome-pilot. Anyway, here are some more detailed instructions that might help you along: 1. download gnome-pilot 2.0.15 from gnome.org: http://ftp.gnome.org/pub/GNOME/sources/gnome-pilot/2.0/gnome-pilot-2.0.15.tar.gz 2. unpack the file using 'tar xzf gnome-pilot-2.0.15.tar.gz' 3. change into the gnome-pilot-2.0.15 directory. 4. build it, configuring it to put the installation somewhere that won't conflict with your system installation (so that if an updated Edgy version is released you can easily upgrade). Here's how to build it: 4a. "./configure --prefix=/tmp/gp" <-- or use some other location instead of /tmp/gp 4b. "make && make install" 5. Now, start the background daemon: "killall gpilotd; /tmp/gp/libexec/gpilotd" 6. In another window, start the corresponding config applet: "/tmp/gp/bin/gpilotd-control-applet" With any luck, you'll be in business, i.e. able to configure and enable the backup conduit. You won't have Evolution conduits at this stage. If you want those, copy the ".conduit" files from your system installation (I'm not 100% where they go on Ubuntu, so do 'locate e-address | grep conduit') and put them into /tmp/gp/share/gnome-pilot/conduits/. These instructions are off the top of my head, so apologies if I've made some mistakes. -- gpilotd locks up my Palm Z22 https://launchpad.net/bugs/66355 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
