Hi Matt, Actually I jumped the gun on saying it was always working from command- line. It seems that the first time I sync, it generates a segfault after eToDo. Once it gets through once, it seems to be able to successfully complete the process. Once it completes successfully from command-line, it also completes successfully from the applet. So, I don't think that I have 2 different copies; I just think that my testing had not revealed this behavior (it's hard to tell when the applet's version of gpilotd crashes as I don't know whether there is an output log). Would a backtrace help the maintenance team?
Between the gpilotd crashing and now my calendar items not synching between Evolution and Palm, I'm planning to go back to the good, old reliable JPilot. Hopefully these issues will be resolved in the future. -- [feisty] etodo conduit times out when syncing with a palm device https://bugs.launchpad.net/bugs/81170 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
