I have the same problem.
If I start jpilot with the -p argument, however, jpilot runs and syncs with my
Tungsten C. However, jpilot doesn't retrieve the categories from the device and
prints "todo.c:357 Error reading category info ToDoDB" stdout. Otherwise, jpilot
seems to work fine.

rpm -qa glibc*
glibc-2.3.4-21.i686
glibc-common-2.3.4-21.i386
glibc-profile-2.3.4-21.i386
glibc-headers-2.3.4-21.i386
glibc-kernheaders-2.4-9.1.90.i386
glibc-utils-2.3.4-21.i386
glibc-devel-2.3.4-21.i386
Works with that. So, was there some kind of weird regression between what came
up with FC4test1 (where I saw the bug), to the rawhide of a while ago where i
got glibc-2.3.4-21 to now, where its out again in glibc-2.3.5-1 ?

Hello,
Jpilot works right, there is a problem in attached ToDoDB.pdb file. There is
problem in file header.
Can you specify which command produced this misstake in ToDoDB.pdb file? (This
ToDoDB.pdb file produce the same error in the previous jpilot version.)
Ivana Varekova

FC3 Jpilot produce the same error as new FC4 Jpilot so if your FC3 Jpilot worked
fine, so in ToDoDB.pdb was not this misstake. The misstake must appeared before
your FC4 jpilot first wrote this error output.
It probably happend when you used Treo (if this error appear when you run FC4
jpilot first).
Ivana Varekova