I haven't tried the latest version. However, I do know that less recent jpilot builds will discretely omit building the Keyring plugin if the openssl-development environment is not installed (on redhat-esque systems, that would be a package called something like 'openssl-devel', probably something similar in the debian universe). If this is the source of the problem, it would manifest itself in the output of the 'make config' stage, which would tell you that it didn't bother to build the plugin. Carlo Donn Washburn wrote: > I will say that I preserved the ~/.jpilot in a special directory. > Since then I gave loaded a new version of SuSE 11 Beta2. I am also > using the same /etc/udev/rules.d file that worked before. I also > confirmed that /dev/ttyUSB0 is there along with /dev/jpilot. > > Assuming it is a ~/.jpilot problem, how would you go about fixing it > short of removal of ~/.jpilot? > > Ralph Alvy wrote: >> On Sunday 04 May 2008 04:35:39 pm Donn Washburn wrote: >>> A check of the Palms error message shows a lack of Keys-Gtkr. >>> Both this Palm and Jpilot worked together previously >>> >> If you deleted ~/.jilot before the sync, you'll get that message. You should >> still see the Keyring plugin fully installed, though. >> _______________________________________________ >> Public archival of this list without permission is prohibited. >> http://lists.jpilot.org/mailman/listinfo/jpilot >> > -- Carlo Graziani (773) 702-7973 (Voice) Department of Astronomy and Astrophysics (773) 702-6645 (FAX) University of Chicago 5640 South Ellis Avenue | If the free market really allocates resources Chicago, IL 60637 | efficiently, why does LA have four times as carlo at oddjob.uchicago.edu | many plastic surgeons as brain surgeons?
More information about the jpilot mailing list