Donn Washburn wrote: > Hey Group; > > I recently complained about jpilot not working after the first opening > then move. It always just blows up. As an effort to track down the > problem I have called it up via a xterm. > > While starting > > donn at m1l-suse:~> jpilot > removing stale pidfile > Couldn't find empty DB file /usr/share/copilot/Memo32DB.pdb: > No such file or directory > copilot may not be installed. > > What is copilot? Is that the problem? This is a fresh SuSE 10.3 Alpha > 4 system that came without jpilot. > Copilot is a branded jpilot that I did for a company called prometheon. It would create a binary called copilot, and had some logos on it, etc. I don't support that anymore, so its possible to have bugs in this build that wouldn't exist with a non-prometheon build. You should be able to build it without this option and then do a make install afterwards. > It also complains after it fails about > /usr/share/fonts/truetype/arial This maybe just a error that happens > during exit. You may be starting copilot in the Memo App, and it does not find a valid Memo32DB and then has errors. This is just a guess. Judd
More information about the jpilot mailing list