Location of gpilotd (was: Re: evolution 1.4.5, red hat linux 9, and treo600?)



> I found a patch to gpilotd.c that included support
> for the Treo600.  I got the src to gnome-pilot-2.0.10, edited the patch
> (just one line for the treo model number), configured to not install in 
> local,
> built gpilotd and did a 'make install'.  Oddly, gpilotd was not installed in
> /usr/bin.  I could only find the built exe in .libs/gpilotd so I copied that 
> down
> to /usr/bin.  I suspect this is the wrong thing to do but I'm not sure why 
> it
> is not installing  it by itself.

Ximian's RPMs (and I think the plain gnome-pilot sources) install gpilotd in
/usr/libexec/. Mandrake installs it in /usr/lib, so you should find it in
one of those places.

> Now when I try 'tools->pilot settings'
> I get a popup error saying "cannot connect to gnomepilot demon'.  If I
> run gpilotd by hand I get a kernel hang and I have to power cycle.

Close down gnome-pilot and try a 'kill bonobo-activation-server'. The file
that says where gpilotd is located is
/usr/lib/bonobo/servers/GNOME_Pilot_Daemon.server. It might be in a different
path, but this is the standard path I've seen for all bonobo servers (which
gpilotd and gpilotd-control-applet use).

Hope this helps a little. Since you're already rebuilding the source,
you may want a patch for the memo conduit. gnome-pilot 2.0.10 crashes
on the memo conduit. Take a look back at the september and october archives
for a few threads on it. There'll be a patch in one of the threads.

Nathan Owens


__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]