Well here's another piece of the puzzle. My comment on 3/26 that all was well was due to me running gpilotd from the command-line. My follow-up reply on 4/1 occurred when I used the gpilot-applet to manage gpilotd. That method is always resulting in a crash. Synching by running gpilotd at a command-prompt as a regular user is always successfully synching. I have loads of ToDo's that have no dates and am not wanting to change my system to get around a bug, esp since there's another workaround. Leaves me wondering what the difference is between running gpilotd manually versus having gpilot-applet manage it.
-- [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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
